competition-stego-media
Lets your agent investigate steganography in media. It helps find hidden information in images, audio, or video by analyzing metadata and other hidden details.
What it does
This tool helps find hidden information within media files like images, audio, or video. It looks for secret data disguised in the technical details of the file.
When to use it
- ✓When you suspect a media file contains a secret message.
- ✓If you need to analyze a media file's technical details to find something hidden.
- ✓When participating in security challenges requiring data extraction from media files.
Example of what to ask your AI
“Look for hidden information in the image file 'secret_photo.jpg'.”
Want more? Open the sections below.
How to use
The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.
Skill link
Ready-to-paste message
How it works
The tool first understands the media file's structure. Then, it examines different 'channels' within the file, such as metadata or color layers, to find the hidden data.
Installation
Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.
In the terminal (Claude Code, Codex, Cursor), in your project folder:
npx skills add zhaoxuya520/reverse-skill --skill competition-stego-mediaOr download just the file:
curl -L https://raw.githubusercontent.com/zhaoxuya520/reverse-skill/main/CTF-Sandbox-Orchestrator/competition-stego-media/SKILL.md -o SKILL.mdTechnical content (original SKILL.md)
Original text by the author, straight from GitHub.
Competition Stego Media
Use this skill only as a downstream specialization after $ctf-sandbox-orchestrator is already active and has established sandbox assumptions, node ownership, and evidence priorities. If that has not happened yet, return to $ctf-sandbox-orchestrator first.
Use this skill when the challenge lives inside a media container, hidden channel, or appended payload rather than a conventional crypto blob.
Reply in Simplified Chinese unless the user explicitly requests English.
Quick Start
- Confirm the real container type, dimensions, duration, codec, and chunk layout before guessing a hidden layer.
- Check metadata, thumbnails, sidecar files, and appended trailers before deeper signal-domain work.
- Rank candidate channels by evidence: alpha, palette, LSB, transform-domain residue, frame order, or container slack.
- Preserve each extracted layer separately so the transform chain stays reproducible.
- Stop when the hidden payload is reproduced, not merely suspected.
Workflow
1. Establish Container Truth
- Inspect headers, chunk tables, EXIF or document metadata, container indexes, thumbnails, and file size anomalies.
- Compare declared format against observed structure to catch polyglots, appended archives, or malformed trailers.
- Record exact offsets, frame numbers, or channel boundaries that look promising.
2. Inspect Candidate Channels
- Check alpha, palette order, RGB or YUV planes, LSBs, spectrogram features, document object streams, or video frame deltas.
- Prefer evidence-driven attempts over brute forcing every transform.
- Note whether the payload is plain bytes, another media layer, compressed data, or an encrypted blob.
3. Reconstruct The Hidden Payload Path
- Keep the chain in order: container -> channel or carrier -> extraction -> decompression or decode -> final parse.
- Separate extraction success from final interpretation; a channel hit is not the same as artifact recovery.
- If the problem becomes primarily about cryptography after extraction, hand off to the broader crypto skill.
Read This Reference
- Load
references/stego-media.mdfor the media checklist, channel ranking guide, and evidence packaging.
What To Preserve
- File structure facts: offsets, chunks, frame numbers, stream names, metadata keys, and trailer size
- Intermediate extractions and the exact command or transform used to produce them
- The final recovered payload and the channel that produced it
FAQ
What are 'channels' in a media file?
Channels are like the different parts that make up a media file, such as colors (red, green, blue), transparency (alpha), or extra information (metadata).
What is 'LSB'?
LSB stands for 'Least Significant Bit'. It's a technique where small changes in the data bits of an image or audio can hide information without the difference being noticeable to the eye or ear.
Do I need to know how to code to use this?
No, this tool is designed for non-programmers. You just need to describe what you are looking for.
Details
Original description by the author
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for image, audio, video, document, and container steganography. Use when the user asks to inspect metadata, alpha or palette channels, LSBs, thumbnails, appended trailers, QR fragments, transcoding artifacts, or recover a hidden payload from media without blind brute force. Use only after `$ctf-sandbox-orchestrator` has a
Popularity
- GitHub stars
- 42k
- Ranking position
- #4738
- License
- MIT
- Updated
- 9/22/2026
Comments
- …
More skills from this repository
competition-ad-certificate-abuse
Helps your agent analyze attacks on digital certificate systems. It investigates how certificates can be misused to gain access.
zhaoxuya520/reverse-skill
competition-agent-cloud
Helps your agent analyze security challenges in AI and cloud systems. It investigates how prompts, tools, and the cloud can be exploited.
zhaoxuya520/reverse-skill
competition-android-hooking
Helps your agent investigate Android applications. It analyzes how apps work internally and how they might be modified or exploited.
zhaoxuya520/reverse-skill
competition-browser-persistence
Helps your agent analyze how websites store information in your browser. It investigates cookies and other data to understand how sessions work.
zhaoxuya520/reverse-skill
Similar skills
dashboard-builder
Helps your agent create useful monitoring dashboards. It turns data into charts that answer important system questions.
affaan-m/ECC
dev-team
Simulates a collaborative development team where different roles respond to a problem together. It's useful for getting multiple perspectives without manually switching agents.
affaan-m/ECC
ecc-council
Has your agent convene a four-voice council for difficult decisions. It's useful when there are multiple good options and debate is needed before choosing.
affaan-m/ECC