competition-crypto-mobile

Recovers transform chains, stego payloads, and mobile signing paths in CTF challenges.

Updated Aug 14, 2026
One-click install
npx skills add https://github.com/MDSIXONE/opencode-config --skill competition-crypto-mobile-mdsixone
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: competition-crypto-mobile
Source: https://github.com/MDSIXONE/opencode-config/tree/main/skills/reverse-skill/CTF-Sandbox-Orchestrator/competition-crypto-mobile
Command: npx skills add https://github.com/MDSIXONE/opencode-config --skill competition-crypto-mobile-mdsixone

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? CTF challenges involving crypto, encoding, steganography, and mobile apps require methodical multi-stage analysis; this Skill provides a structured downstream workflow for decoding blobs, recovering transform chains, inspecting hidden media payloads, and hooking APK/IPA trust boundaries after sandbox assumptions are established. ## 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 layout, palettes, alpha planes, LSBs, thumbnails, and appended trailers with evidence-driven decode attempts. - Mobile Trust-Boundary Analysis: Traces APK/IPA signer logic, token storage, SSL pinning, protobuf boundaries, and native bridge calls, hooking the narrowest boundary that proves behavior. - Use Case: Given an encoded blob from a CTF challenge, decode each stage in order, record decisive bytes per stage, and reproduce the final plaintext or signed request as verifiable evidence. ## Quick Start After $ctf-sandbox-orchestrator is active, use $competition-crypto-mobile to decode this blob, recover the transform chain, inspect stego payloads, or hook the mobile signing path.

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-stage encoded blob in a CTF challenge?▼

Reconstruct the chain step by step: 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 is reproducible.

How to find hidden payloads in steganography challenges?▼

Inspect metadata, chunk layout, palettes, alpha planes, LSBs, thumbnails, and appended trailers. Rank decode attempts by evidence rather than brute-forcing, and preserve the decisive bytes proving each decode stage.

When should I use Android or iOS hooking instead of this skill?▼

Use $competition-android-hooking for Android dynamic tracing, signer hooks, JNI boundaries, or pinning checks, and $competition-ios-runtime for iOS runtime tracing, Keychain access, or Objective-C/Swift hooks. This skill covers the broader crypto, stego, and mobile workflow.

Can this skill be used without the sandbox orchestrator?▼

No. It is an internal downstream skill that requires $ctf-sandbox-orchestrator to be active first, since the orchestrator establishes sandbox assumptions, node ownership, and evidence priorities before routing here.

What evidence should be preserved during mobile app analysis?▼

Preserve hook points, signed strings, headers, local storage paths, component names, protobuf fields, and channel-specific outputs. Correlate static evidence from manifests and configs with dynamic hooking evidence before concluding.