root@thehacksparrow:~/writeups$ SYSTEM ONLINE
root@sparrow:~/writeups$ cat burp-suite-other-modules.md
// Offensive

Burp Suite: Other Modules

15 Nov 2026 · 7 min read
Overview — A hands-on Offensive room covering the four Burp Suite modules that get less attention than Repeater and Intruder: Decoder (encode, decode and hash data), Comparer (diff two items by words or bytes), Sequencer (measure the entropy of session or anti-CSRF tokens) and Organizer (bookmark and annotate requests). A small target web app provides a login form to compare responses and a token to analyse.
PlatformTryHackMe
CategoryOffensive
DifficultyEasy
RoomBurp Suite: Other Modules

Task 1 — Introduction

Each of these modules does something you could do with a script or a web tool, but having it one right-click away from the traffic you are already inspecting saves a lot of context switching. Start the target machine (and the AttackBox if you are not using your own Burp), then work through the tools in order. The target is reachable at MACHINE_IP.

Task 2 — Decoder: Overview

Decoder transforms data in both directions: it decodes things you intercept, encodes payloads you want to send, computes hashes, and offers Smart Decode, which repeatedly tries to peel encodings off until it reaches plain text (similar in spirit to CyberChef's Magic). The layout has four parts:

  1. The input box. Data gets here by pasting or by right-click then Send to Decoder from any other module.
  2. A switch between treating the input as text or as hex bytes.
  3. Drop-downs to Decode as, Encode as and Hash.
  4. The Smart Decode button.

Every operation creates a new output box below, which itself can be transformed again, so you can chain steps.

Q: Which feature attempts auto-decode of the input?
A: Smart Decode

Task 3 — Decoder: Encoding/Decoding

The available formats, and why you would reach for each:

  • Plain: the untransformed text.
  • URL: replaces unsafe characters with % followed by their hex code. A forward slash (ASCII 47, hex 2F) becomes %2F. Essential when payloads travel inside query strings.
  • HTML: character entities such as " or B. Useful for recognising how an application escapes output, which is central to XSS testing.
  • Base64: maps arbitrary bytes onto a printable alphabet. Common in tokens, headers and basic-auth.
  • ASCII Hex: each character becomes its two-digit hex code, so ASCII becomes 4153434949.
  • Hex, Octal, Binary: treat the input as a number and convert it between bases.
  • Gzip: compress or decompress; the result is binary, so it is easiest to view in the hex editor.

Operations can be stacked (for example text to ASCII Hex to octal), and each applied transformation is colour coded so you can tell at a glance what has been done. Hex view lets you edit data byte by byte, which matters for binary content. Smart Decode, for instance, recognises Burp as HTML entities and returns the text Burp. It is not perfect, but it is a quick first attempt at unknown blobs.

Q: Base64 encode the phrase Let's Start Simple.
A: TGV0J3MgU3RhcnQgU2ltcGxl

Q: URL decode %4e%65%78%74%3a%20%44%65%63%6f%64%69%6e%67.
A: Next: Decoding

Q: Use Smart Decode on the HTML-entity string that spells out two percent-encoded characters; what is the decoded text?
A: 47

Smart Decode works in two rounds here: the HTML entities decode to a URL-encoded string (%34%37), and that decodes to 47. This is a good demonstration of nested encoding.

Q: Encode Encoding Challenge as Base64, then convert that result to ASCII Hex, then encode the hex string as octal. What is the final string?
A: Follow the chain in Decoder and submit what it displays. Step 1 gives RW5jb2RpbmcgQ2hhbGxlbmdl and step 2 gives 5257356a62325270626d6367513268686247786c626d646c; the octal step depends on how Decoder treats the hex input, so copy its output directly.

Task 4 — Decoder: Hashing

A hash function is a one-way transformation: the same input always yields the same fixed-size digest, a tiny change in the input changes the digest completely, and you cannot run it backwards. For example, MD5 of MD5sum is 4ae1a02de5bd02a5515f583f4fca5e8c while MD5SUM gives 13b436b09172400c9eb2f69fbd20adad. That makes hashes ideal for integrity checks and for storing passwords: the application stores only the hash and, at login, hashes what you submit and compares. MD5 (and MD4) are broken and should not be used for anything security-sensitive; they are still handy for quickly identifying files.

In Decoder, pick an algorithm from the Hash menu. The output is raw bytes, so Burp shows it in hex view; apply Encode as, ASCII Hex to get the familiar hex digest string.

Q: What is the SHA-256 hashsum of Let's get Hashing!, as an ASCII Hex string?
A: 6B72350E719A8EF5AF560830164B13596CB582757437E21D1879502072238ABE

Q: Generate an MD4 hashsum of Insecure Algorithms and encode it as Base64.
A: TcV4QGZZN7y7lwYFRMMoeA==

Q: Four SSH keys were tampered with and only one has the MD5 3166226048d6ad776370dc105d40d9f8. Which one is the original?

Decoder could do it one file at a time, but a shell does it in one line: hash every file and look for the known digest.

md5sum *

Only one line carries the digest from the task description, the file key3.

A: key3

Task 5 — Comparer: Overview

Comparer shows the differences between two pieces of data, either by words (good for text such as HTML responses) or by bytes (good for binary or when whitespace matters). The main window has the item list on the left, load buttons on the upper right (Paste, Load from file, Remove, Clear) and the Words / Bytes buttons on the lower right. Items usually arrive via right-click then Send to Comparer.

Selecting two items and choosing a mode opens a diff window. Text or hex view can be switched, the legend at the bottom shows the colours for modified, deleted and added data, and Sync views keeps both panes in the same format. The window title reports the total number of differences.

Task 6 — Comparer: Example

Comparer earns its place when two responses look almost identical. A classic case is a credential attack: two login responses can have slightly different lengths, and a diff shows exactly which part changed and whether it signals success.

  1. Browse to the support login page (http://MACHINE_IP/support/login) and submit an invalid username and password with Proxy intercepting.
  2. Send the request to Repeater (Ctrl+R), send it, then right-click the response and choose Send to Comparer.
  3. In Repeater change the credentials to the pair the room provides (support_admin / w58ySK4W), send again and send this second response to Comparer.
  4. Open both in Comparer and compare by words. The differences highlight the redirect or content that appears only on a successful login.

The room asks no questions in this task; the value is the technique.

Task 7 — Sequencer: Overview

Sequencer estimates the entropy (randomness) of tokens such as session cookies, CSRF tokens and password-reset tokens. Tokens that are predictable can be guessed, and a guessable reset token is effectively an account takeover. There are two ways to feed it:

  • Live capture (default): you give Sequencer a request whose response contains a token, and it replays that request thousands of times, harvesting a fresh token each time. Noisy, but needs no prior data.
  • Manual load: you paste or load a list of tokens you already collected. Quiet, but you need plenty of samples.

Q: What does Sequencer allow us to evaluate?
A: Entropy

Task 8 — Sequencer: Live Capture

The exercise analyses the anti-brute-force token in the admin login form.

  1. Capture a GET request to /admin/login/ in Proxy and choose Send to Sequencer.
  2. Under Token Location Within Response choose Form field and select loginToken from the list (the other choices are Cookie and Custom location).
  3. Leave other settings at default and click Start live capture.
  4. When about 10,000 tokens have been collected, click Pause, then Analyze now.

Pausing rather than stopping lets you resume if the report says you do not have enough samples. Auto analyze re-runs the analysis every 2,000 requests so you can watch the estimate stabilise. You can also copy or save the captured tokens for later offline analysis.

Q: What is the overall quality of randomness estimated to be?
A: Excellent

Task 9 — Sequencer: Analysis

The report has four sections, and the Summary usually tells you enough:

  • Overall result: Burp's verdict on how safely the tokens are generated.
  • Effective entropy: an estimate in bits. In the room's example it is about 117 bits, high enough that guessing or brute force is impractical.
  • Reliability: the significance level (1% here), meaning roughly 99% confidence in the estimate.
  • Sample: how many tokens were analysed and their characteristics.

The character-level and bit-level tabs are worth a look when the summary raises doubts, because they show where the weakness lies, for example a bit position that never changes. Keep in mind that a good score is evidence, not proof: statistical tests cannot show that a generator is cryptographically secure.

Task 10 — Organizer: Overview

Organizer is a notebook for requests you want to come back to: ones to investigate later, ones already found interesting, or ones destined for the report. Send items from Proxy, Repeater or other tools via right-click then Send to Organizer, or with Ctrl+O. Each stored item is a read-only snapshot of the request and response at the moment you sent it, so later edits in Repeater do not change it.

The table includes index, time, workflow status, source tool, method, host, path, query, parameter count, response status, response length and your own notes. Selecting a row shows the request and response (both read-only) with a search bar underneath.

Q: Are saved requests read-only? (yea/nay)
A: Yea

Quick reference

ModuleWhat it doesWhere it appears
DecoderEncode, decode and hash data; operations can be chainedTasks 2 to 4
Smart DecodeRepeatedly peels nested encodings automaticallyTasks 2 and 3
Decoder hashingOutput is raw bytes; use Encode as ASCII Hex for the digest stringTask 4
ComparerDiffs two items by words or by bytesTasks 5 and 6
SequencerEstimates the entropy of tokens (live capture or manual load)Tasks 7 to 9
Sequencer reportOverall result, effective entropy, reliability and sample sizeTask 9
OrganizerStores read-only snapshots of requests with notes and statusTask 10

Key takeaways

  • Decoder chains encoders, decoders and hashes; Smart Decode handles nested encodings but is not infallible.
  • Hash outputs are bytes: convert them with ASCII Hex to get the usual digest string. MD4 and MD5 are only fine for identification, never for security.
  • Comparer turns "these two responses look the same" into an exact diff, which is how you notice a successful login hidden in a similar page.
  • Sequencer needs thousands of samples; pause instead of stopping so you can collect more, and read effective entropy and reliability together.
  • Organizer keeps immutable copies of interesting traffic with notes and status, useful for reporting.