competition-crypto-mobile

Recovers transform chains, hidden media payloads, and mobile signing logic in CTF challenges.

7|4|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/dbx0/skills --skill competition-crypto-mobile-dbx0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: competition-crypto-mobile
Source: https://github.com/dbx0/skills/tree/main/skills/crypto-stego/crypto/competition-crypto-mobile
Command: npx skills add https://github.com/dbx0/skills --skill competition-crypto-mobile-dbx0

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? CTF challenges involving crypto, steganography, and mobile apps often hide flags behind layered encodings, concealed media payloads, or app-level trust boundaries, and this Skill provides a structured workflow to decode, extract, and reproduce the required artifacts without wasting time on blind brute force. ## Core Features & Use Cases - Crypto and Encoding Recovery: Reconstructs transform chains step by step (container, compression, encoding, xor/substitution, crypto, integrity, parse) while preserving exact keys, IVs, nonces, and byte order. - Steganography Inspection: Examines metadata, chunk layouts, palettes, alpha planes, LSBs, thumbnails, and appended trailers, ranking decode attempts by evidence. - Mobile Trust-Boundary Analysis: Traces APK/IPA signer logic, token storage, SSL pinning, protobuf edges, and native bridge calls, hooking the narrowest boundary that proves the behavior. - Use Case: During a CTF, you receive an APK that signs requests with a hidden key. Use this Skill to trace the signer logic, hook the signing function, and replay a valid signed request to recover the flag. ## Quick Start Ask the agent to decode the attached challenge blob or hook the APK signer to reproduce the accepted signed request, after the CTF sandbox orchestrator has established assumptions.

Frequently Asked Questions about competition-crypto-mobile

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decode a multi-layer encoded blob in a CTF challenge?

Reconstruct the transform chain in order: container, compression, encoding, xor or substitution, crypto, integrity check, then final parse. Record exact keys, IVs, nonces, salts, offsets, and byte order at each stage so the plaintext can be reproduced.

How to find hidden data in images during steganography challenges?

Inspect metadata, chunk layout, palettes, alpha planes, LSBs, thumbnails, and appended trailers. Rank decode attempts by evidence found in the file rather than brute-forcing every possible extraction method.

How do I bypass or replay mobile request signing in an APK?

Trace the signer logic, token storage, and native bridge calls from the manifest and native libraries, then hook the narrowest boundary such as the signer or crypto helper. Reproduce the signed request with the exact headers and signed strings the app produces.

When should I use a specialized Android or iOS hooking skill instead?

Use a dedicated Android hooking skill when the task centers on dynamic tracing, JNI boundaries, or signer hooks, and an iOS runtime skill for Keychain access or Objective-C/Swift hooks. This skill covers the broader crypto, stego, and mobile workflow.

Why does my crypto challenge solution fail even with the right algorithm?

Recognition is not recovery; wrong keys, IVs, nonces, byte order, or offsets silently break decryption. Keep every parameter in one evidence block and reproduce the actual plaintext or downstream artifact to confirm the solution.