A rover's account. A QR code scattered across posts. A barcode in another community. The puzzle is connecting the clues—and keeping encoded text separate from encrypted bytes.
OSINTImage reconstructionQR codeBase64BarcodeAES
1. Instagram trailg3kko.gFind the QR fragments; distinguish them from rickroll decoys.
2. Reconstructed QRBase64 → invite + key + IVThe decoded bundle provides a destination and two crypto inputs.
3. Discord clueSearch “flag” → barcodeThe barcode carries the ciphertext as hexadecimal text.
4. AES decryptionKey + IV + ciphertextCorrect parameters produce the flag, according to the write-up.
The two branches converge at decryption: Instagram supplies the key and IV; Discord supplies the ciphertext. The actual values and AES mode are absent from the supplied document.
The scenario
The challenge description says a rover named g3kko.g left a cryptic message online. The author points the solver to Instagram, where several posts contain pieces of a QR code. Rebuilding that image reveals an encoded message that leads to a Discord server.
The decoded QR payload reportedly contains an invite link, an AES key, and an initialization vector (IV), in that order. Searching the Discord server for flag reveals a barcode. Its decoded string is the hexadecimal ciphertext needed for the final AES operation.
This is a clue-following and data-transformation exercise, not a password brute-force attack or an exploit against Instagram or Discord. The intended secret is recovered by collecting the material deliberately placed along the trail.
What was available—and what was not run
This guide uses the supplied one-page write-up's previously extracted text, plus read-only technical documentation. Direct PDF preview was unavailable. The original post images, QR payload, Discord barcode, crypto values, and final flag were not supplied. No files, decoders, AES recipes, build scripts, or HTML previews were run. No social account or Discord server was accessed.
What a complete solve would establish
Which challenge posts supplied the fragments, and how they formed one readable QR code.
The exact QR scan text and decoded invite/key/IV bundle.
The Discord message and barcode that supplied the ciphertext.
The key, IV, ciphertext, AES mode, and any padding or authentication settings used.
The actual decrypted flag—not merely a string that resembles the flag format.
The important distinction
Scanning a code, decoding Base64, parsing hex, and decrypting AES are four different operations.
The important limitation
The PDF explains the route, but does not include enough artifacts or parameters to reproduce the final answer.
Show the documented flag format—not a recovered flag
The only flag-shaped text supplied is the format below. the discovery is a placeholder in the original description, not an answer recovered in this review.
Exact format from the PDF · not the solution
LUH{the discovery}
The write-up says AES decryption reveals the flag, but does not print its value. No final flag is invented here.
How the trail works
Author-described sequence
Each clue changes the kind of evidence you are looking for. The final step combines information collected in two different places.
1. A handle narrows the search
The starting identity is g3kko.g. The solution explicitly names Instagram; that platform attribution comes from the write-up, not from a live account lookup performed here.
The PDF describes odd posts and a few rickroll links intended as distractions. A link being present is not evidence that it advances the solve. The relevant clue is the recurring visual material that can form a QR symbol.
General research practice: record the source of each clue and why it belongs to the challenge. A matching handle alone does not establish that a present-day account is the historical challenge account.
2. The image pieces form a single QR code
The author says several posts contain pieces of a QR code. Their images must be collected individually and stitched together in an image editor, or placed together in the correct arrangement. The number of fragments, their dimensions, and the layout are not given.
A QR code's small squares are called modules. Their spacing and the continuity of the overall grid matter. Simply making a collage of screenshots with gaps or inconsistent scaling is not the same as reconstructing the encoded symbol.
Practical reconstruction principles
Keep originals separate from working copies; use the highest-quality available images.
Match module scale and align fragment edges. Do not assume posting order is tile order.
Use the large corner finder patterns and continuing grid as alignment evidence.
Avoid stretching, smoothing, or repeatedly saving with lossy compression.
Keep a clear outer margin. DENSO WAVE specifies a four-module quiet zone on every side of a QR symbol.
Those are general QR-handling principles, not a reconstruction of the absent Quizzle images. The symbol in this guide's sidebar is only an illustrative icon; it is not a challenge QR code.
3. The QR carries an encoded bundle, not the flag
Scanning the rebuilt symbol reportedly returns a long “base64-looking string.” Decoding it gives three items in a specified order:
Documented order · actual contents not provided
1. Discord invite link
2. AES key, represented in hex
3. IV, represented in hex
The PDF does not show the encoded text or its separators. Do not assume the decoded payload is JSON, three lines, or a space-delimited string. Preserve the actual scan output before interpreting its fields.
4. Wordplay identifies the tool and cipher
The author quotes a post comment, cheff likes it with key and IV, as a hint toward CyberChef. The letter clues A+, E+, and S are interpreted as AES.
This points to a family of operations, not a complete recipe. Knowing “AES” does not specify the mode, padding, or all the additional settings a mode might require.
5. Discord supplies the missing ciphertext
The invite leads to a Discord server. The PDF says searching for flag turns up a barcode. Scanning that barcode yields a string identified as hexadecimal ciphertext.
The QR and barcode serve different roles. The QR connects the trail and supplies key material. The Discord barcode supplies the data to decrypt. Treating the QR payload itself as the AES ciphertext skips an essential clue.
The barcode type is not specified
The document calls it a barcode, without naming a symbology such as Code 128. This guide does not guess the barcode type or recreate a plausible-looking substitute. A future decoder must support the actual artifact.
The intended solve recovers a deliberately disclosed key; it does not defeat AES cryptographically. Correct bytes and matching settings are still necessary to obtain the original plaintext.
Encoding & AES
Technical background + caveats
A visible string is a representation of data. Decryption succeeds only when those representations become the intended bytes, with the intended settings.
The challenge-specific facts here come from the PDF. Byte sizes, encoding rules, and tool behavior below are general technical background checked against RFC 4648, NIST, DENSO WAVE, and CyberChef documentation/source.
Four operations that should not be confused
Operation
What it does
Role in Quizzle
Scan QR / barcode
Reads a visual symbol and returns its encoded payload.
Extracts the QR text and the barcode's ciphertext text.
Decode Base64
Maps printable characters back into bytes; requires no secret key.
Unpacks the invite, key, and IV bundle.
Parse hexadecimal
Converts every two hex digits into one byte.
Interprets the key, IV, and ciphertext correctly.
Decrypt AES
Uses a symmetric key and a matching mode/configuration to recover plaintext.
Reveals the final flag, according to the author.
Base64 is not encryption
Standard Base64 uses A–Z, a–z, 0–9, +, and /, with = used for padding when needed. Base64url uses - and _ instead of + and /. The PDF does not reproduce the payload, so its exact alphabet cannot be inspected here.
Preserve case and the original characters. If decoding fails, check the scan transcription and the alphabet rather than blindly deleting punctuation or repeatedly decoding unrelated layers.
This example is a published encoding illustration, not an output generated in this review. Encoding changes presentation; it adds no confidentiality.
Hex text and text bytes are different inputs
For a hex field, 41 represents one byte with value 0x41. If that same string is entered as UTF-8 text, it becomes two bytes: 0x34 0x31, the characters 4 and 1.
Representation example · not challenge key material
Keep leading zeros. Hex letter case does not change byte values, but missing digits do. A complete hex byte string has an even number of digits after any documented separators are removed.
AES key sizes are measured in bytes, not displayed digits
NIST FIPS 197 defines AES-128, AES-192, and AES-256. All use a 128-bit (16-byte) block; the suffix identifies the key size, not the block size.
AES variant
Key bytes
Hex digits
Block size
AES-128
16
32
16 bytes
AES-192
24
48
16 bytes
AES-256
32
64
16 bytes
These lengths are sanity checks, not recovered Quizzle values. The PDF provides no key string, so it does not establish which AES variant was used.
An IV does not select the mode
An initialization vector is a mode-related input distinct from the key. Its role and required length depend on the mode and implementation. AES-CBC uses a 16-byte IV; other modes have their own requirements and conventions.
The presence of a key and IV does not prove the challenge used CBC. NIST SP 800-38A describes ECB, CBC, CFB, OFB, and CTR as different constructions around a block cipher. An authenticated mode such as GCM also introduces authentication-tag handling.
Do not turn a tool default into a challenge fact
The CyberChef AES Decrypt source reviewed lists CBC first and documents PKCS#7 as the default padding for CBC/ECB. That is current tool behavior, not evidence of Quizzle's historical recipe. The PDF specifies neither the mode nor padding. No complete decrypt recipe can be justified from it alone.
The supported portion of a CyberChef setup
The author specifies hexadecimal key, IV, and input, with raw output. The remaining fields must come from the real challenge artifacts or an authoritative recipe.
Setting
Documented / justified choice
Evidence limit
Operation
AES Decrypt
Named by the author's solve.
Key
Actual decoded key; interpret as Hex.
No value or length supplied.
IV
Actual decoded IV; interpret as Hex.
No value or length supplied.
IV from input
Off for the described separate-IV route.
The author supplies the IV separately; no embedded-IV layout is documented.
Input
Barcode string; AES input interpretation Hex.
Ciphertext string absent.
Output
Raw, as described.
Actual plaintext absent; preserve its exact characters.
Mode
Unspecified. Recover from artifacts or author settings.
Do not assert CBC merely because it is a default.
Padding / authentication
Match the actual encryption configuration.
No padding choice, tag, or additional authenticated data is documented.
Decode hexadecimal exactly once
One coherent route is to paste the barcode's hex text into AES Decrypt and choose Input: Hex. Another is to use From Hex first and then choose Input: Raw in the AES operation.
Do not add From Hex while leaving AES set to interpret the already-decoded bytes as hex again. The key and IV's format toggles are separate from the main input setting.
What the error messages can and cannot tell you
Invalid key length: inspect the key's byte length, its format toggle, and whether you pasted labels or separators.
IV error: confirm the IV belongs in its separate field and meets the actual mode's requirements.
Unable to decrypt / padding failure: check ciphertext integrity, key, IV, mode, and padding; it is not proof that AES must be replaced by another cipher.
Output without a coherent flag: verify the whole configuration and the origin of the ciphertext, rather than editing the output to look correct.
For CBC, wrong-IV effects are concentrated in the first plaintext block. Wrong-key, corrupted-input, and other mode/configuration errors can behave differently. Diagnostic symptoms are leads, not proofs of one cause.
Solve walkthrough
Read-only study plan
Collect the evidence, preserve each intermediate result, then configure the final operation. A useful write-up records more than “put it in CyberChef.”
This adapts the author's route for future authorized practice. It is reference text only: no browsing of the challenge trail, image scanning, decoding, or decryption was performed. The original artifacts are prerequisites for reproduction.
Establish the challenge identity and scope
Record g3kko.g, the platform named by the solution (Instagram), and the challenge dates. Use only intended challenge content or organizer-provided archives. Do not extend the handle search into unrelated people or private communities.
Checkpoint: a sourced challenge account or archive, not just a present-day username match.
Separate QR fragments from distractions
The author identifies rickroll links as decoys and several images as QR pieces. Preserve the relevant images and any clue-bearing captions/comments. Note each image's source and intended position in the reconstructed code.
The comment cheff likes it with key and IV and letter clues A+, E+, S point to CyberChef and AES. They should be recorded with their context, not treated as encryption parameters.
Checkpoint: an image set with provenance and an evidence-based layout. Fragment count and tile order are not given in the PDF.
Rebuild and scan the QR
Align the original modules at consistent scale, avoid introducing seams or distortion, and preserve the quiet zone. Inspect a scanner's returned payload as text before allowing it to open any destination.
The expected output is a Base64-looking string, not a direct flag. Keep that scan output exactly; if it is truncated, every downstream stage may become misleading.
Checkpoint: the reconstructed image and its exact scan text. Neither is supplied in this collection.
Decode the bundle and label the three fields
Apply Base64 decoding to the scan text using the matching alphabet. The author's order is invite link, key, IV. Separate the fields according to the actual decoded structure, not an invented delimiter scheme.
Preserve the original bundle as well as your parsed fields. Treat the key and IV as hex byte representations; do not remove leading zeros.
Checkpoint: three exact values and their source. A key should decode to 16, 24, or 32 bytes for standard AES; IV requirements depend on the selected mode.
Find the Discord barcode and extract its text
In authorized future practice, the recovered invite is the platform pivot. The PDF says to search the server for flag and scan the resulting barcode. Record the message context and image, not just the search keyword.
Keep the decoded ciphertext text and confirm that it is complete hex. A lone search hit is not enough if it lacks a connection to the challenge trail.
Checkpoint: the original barcode and exact ciphertext string. The PDF contains no server/channel/message identifiers or barcode image.
Resolve the complete AES configuration
Gather the real key, IV, and ciphertext, then establish the mode and any padding/tag settings from the original clues or author recipe. The one-page PDF leaves those settings unspecified.
The described CyberChef route uses Key: Hex, IV: Hex, Input: Hex, and Output: Raw, with the IV supplied separately. Check that each field is being decoded once. Do not substitute an empty IV or a tool default for missing evidence.
This is the unresolved checkpoint
Without the original artifacts and correct settings, stop short of claiming a reproduced solve. “AES + key + IV” is a clue summary, not a uniquely determined operation.
Preserve the exact plaintext and proof
The author says the raw output is the flag. A future reproduction should retain the exact output, recipe/settings, and intermediate artifacts. Check the documented LUH{...} structure, but do not use that shape alone as proof.
An accepted submission or organizer confirmation, where available, is stronger evidence than a manually constructed flag-looking string. No submission or decryption result is claimed here.
Checkpoint: exact plaintext and reproducible inputs/settings. The final flag is not printed in the supplied write-up.
A compact evidence notebook
This blank record is for later practice, not a populated solve. Copying it only copies text.
Suggested record · all artifact values intentionally blank
Challenge: Quizzle
Starting handle (PDF): g3kko.g
Account/archive source:
Collection date:
QR fragment sources and arrangement:
Reconstructed image reference:
Exact QR scan text:
Base64 alphabet and decoded bundle:
Invite:
Key hex:
IV hex:
Discord message/archive reference:
Barcode image and symbology:
Exact ciphertext hex:
AES mode and evidence:
Key bytes / IV bytes / ciphertext bytes:
Padding or authentication settings:
Tool version and complete recipe:
Exact decrypted plaintext:
Acceptance evidence, if available:
If future practice gets stuck
Symptom
First things to check
QR will not scan
Missing fragments, tile orientation, module scale, seams, contrast, and quiet zone. Preserve originals before edits.
QR scans, Base64 does not decode cleanly
Truncated scan text, changed case, wrong alphabet, or copied scanner UI rather than the payload.
Decoded bundle seems to contain too many fields
Actual delimiters and labels; a URL can itself contain punctuation. The PDF does not specify the payload grammar.
Invite no longer works
Historical challenge availability. Ask for an organizer-provided archive; do not assume another server is equivalent.
Barcode yields no useful string
Image completeness, supported symbology, surrounding margin, and whether the selected image is the intended clue.
Key length is invalid
Hex vs UTF-8 interpretation, missing zeros/digits, or labels included in the key field.
A string looks like a flag but has no evidence trail
Preserve the actual output and settings; flag format is a consistency check, not independent proof.
Things to learn
Takeaways & safe practice
The useful skill is not guessing a cipher. It is following dependencies, preserving representations, and knowing when the available evidence is insufficient.
Follow clues with provenance
A handle, image, caption, invite, and message are separate artifacts. Record how each leads to the next. The author identifies decoys, but a reproducible solve still needs to show why the chosen evidence belongs together.
Separate finding from processing
OSINT finds the material. Image reconstruction restores a visual carrier. Scanning extracts its text. Base64 and hex decoding interpret that text. AES decryption uses the gathered bytes and settings. Naming each stage makes failures much easier to isolate.
Keep originals and intermediate results
Do not retain only the final screenshot. A missing character in a ciphertext or an incorrectly scaled QR fragment can invalidate the result. Preserve the source images, reconstructed code, exact scan text, decoded bundle, barcode payload, and recipe.
Byte interpretation is part of the algorithm
A string that looks like a key is not necessarily the bytes the cipher expects. Lengths must be counted after decoding the declared format. Leading zeros, format toggles, input decoding, and output encoding are technical decisions—not cosmetic UI choices.
A key and IV do not fully describe AES decryption
The mode and any applicable padding/authentication settings must match encryption. A current UI default is not historical evidence. A strong technical write-up records the full recipe and the tool version.
Distinguish a missing artifact from a failed method
If the QR, invite, or barcode is absent, you cannot reproduce the trail by studying the summary harder. If the AES mode is unspecified, “no clean output” is not evidence that the documented cipher was wrong. Identify what is missing before trying new hypotheses.
Challenge mechanisms versus security guarantees
Mechanism
What it achieves here
What it does not establish
Split QR code
Requires collecting and aligning visual clues.
Cryptographic secrecy or access control.
Base64 bundle
Packages a destination and crypto inputs as printable text.
Confidentiality; decoding requires no secret.
Cross-platform invite
Moves the solver to the next clue location.
Permission to inspect unrelated or private content.
Barcode ciphertext
Uses a visual carrier for encoded encrypted data.
A different encryption algorithm or a hidden key by itself.
AES with disclosed key material
Provides a decryption exercise after collecting the clues.
A break of AES or protection from a solver who has the key and all settings.
Rickroll decoys
Distracts from relevant clues.
Evidence that every unrelated link should be followed or executed.
Scope and privacy
Keep future work within the intended challenge and authorized archives. Preview decoded links before navigation. Do not run downloads or commands embedded in clue text, expose personal account information, or join unrelated communities to fill gaps in the write-up.
For a challenge author
Archive the trail. Preserve original fragment images, comments, barcode, and message context; social links and invites can expire.
Publish enough to reproduce the solution. A post-event write-up should include the QR layout, decoded payload, exact hex values, complete AES mode/settings, and final answer.
State the payload format. Field order alone does not define how to parse a string safely.
Identify the barcode type. “Scan it” is less useful when a reader does not know which symbology their tool must support.
Keep keys out of real security boundaries. Intentional disclosure is suitable for a puzzle, not for protecting production secrets.
Self-check
Can I explain which artifact supplies the key, IV, and ciphertext?
Can I distinguish QR scanning from Base64 decoding?
Can I explain why 4142 as hex differs from 4142 as UTF-8 text?
Can I convert AES key byte lengths into hex digit lengths?
Can I explain why an IV does not prove CBC was used?
Can I avoid decoding hex twice in a CyberChef recipe?
Can I identify the missing artifacts and settings without inventing them?
Can I distinguish the documented flag format from the actual flag?
Useful follow-up topics
QR finder patterns and quiet zones; lossless image handling; barcode symbologies; Base64 versus Base64url; byte strings and text encodings; AES modes, padding, and authenticated encryption; and reproducible OSINT evidence collection.
Files & source notes
Provenance & evidence limits
The original write-up is a concise route description, not a complete artifact package. Keep those limits beside the technical explanation.
Key size, IV length, mode, padding, and any applicable authentication parameters.
Final flag
Says decryption reveals it; provides the format.
Actual plaintext and acceptance evidence. Neither is printed.
Supplemental technical references
The following public pages were fetched and read as text on 17 November 2026. They explain general principles; they do not supply missing Quizzle artifacts. These optional links require internet only if you choose to open them.
CyberChef AES Decrypt source — reviewed as text only; key/IV format toggles, input/output formats, mode choices, IV extraction, and documented padding defaults.
The CyberChef source link follows its current branch, not a pinned historical release. Its settings explain the interface reviewed today and must not be mistaken for Quizzle's missing author recipe.
Read the supplied write-up text · substantive snapshot
Transcribed from the existing extraction. Blank layout lines and the page footer are omitted; the description, format, and solution wording are preserved. This is text, not a runnable recipe.
Quizzle Challenge Write-up.pdf · extracted text
Quizzle
Category: Misc · Difficulty: Easy Release Date: 05-09-2026 · Close Date: 16-09-2026 · Author: letushackofficial
Description
A rover named g3kko.g left a cryptic message buried somewhere online. Your job: find the account, follow the
trail, and dig out the message.
Flag Format
LUH{the discovery}
Solution
Start by tracking down g3kko.g on Instagram. The account has a bunch of odd posts, and a couple of them are
just rickroll links thrown in to waste your time — ignore those.
Look closer and you'll notice several posts contain pieces of a QR code, split across them. Download each of
those images individually, then stitch them together in an image editor (or just place them side by side) to
rebuild the full QR code. Scan the reconstructed code and you get a long base64-looking string.
Decode it and you get three things, in this order: an invite link, a key, and an IV. One of the posts has a
comment that says "cheff likes it with key and IV" — a nod to CyberChef, and "A+", "E+", "S" spells out AES if you
squint. If you don't already know what AES is, this is the point where a quick search tells you enough to keep
going.
Follow the invite into the Discord server. Search the server for the word "flag" and you'll turn up a barcode. Scan
it and pull the string out of it — that's your ciphertext, and it's in hex.
At this point you've got everything CyberChef needs: the key (hex), the IV (hex), and the input (the barcode
string, also hex). Set up an AES decrypt recipe with those three values and let it run — the raw output is the flag,
revealed.
Review boundaries
Documented, not independently reproduced: the Instagram/Discord trail, QR/barcode contents' roles, clue interpretation, and reported final decryption.
General technical background: QR margin guidance, Base64/hex rules, AES key/block sizes, and the reviewed CyberChef interface. Illustrative byte examples are not challenge outputs.
Not supplied or recovered: source images, payload strings, invite, key, IV, ciphertext, full AES settings, and actual flag.
Not performed: any file execution, build, script/CLI run, HTML preview, QR/barcode scan, Base64/AES operation, social-account visit, Discord access, or challenge submission.
Not embedded: original PDFs, external sites, CyberChef, scanners, or missing challenge artifacts.
One HTML file with embedded styling and navigation. No external assets or automatic network requests. Copy buttons copy text; print, theme, and page switching are local browser features. There is no decoder, decryptor, or lab launcher.