Agent Skills › zhaoxuya520/reverse-skill › competition-crypto-mobile

competition-crypto-mobile

GitHub

CTF竞赛中用于密码学、编码、隐写术及移动端（APK/IPA）安全分析的下游技能。支持解密、恢复密钥链、检查隐藏媒体载荷、挂钩签名逻辑及重放请求，需在前置沙箱建立后调用。

CTF-Sandbox-Orchestrator/competition-crypto-mobile/SKILL.md zhaoxuya520/reverse-skill

Trigger Scenarios

用户要求解码二进制数据或恢复变换链需要检查隐藏媒体载荷或元数据需要挂钩APK或IPA签名逻辑需要检查应用本地存储或重放移动请求签名

Install

npx skills add zhaoxuya520/reverse-skill --skill competition-crypto-mobile -g -y

More Options

Non-standard path

npx skills add https://github.com/zhaoxuya520/reverse-skill/tree/main/CTF-Sandbox-Orchestrator/competition-crypto-mobile -g -y

Use without installing

npx skills use zhaoxuya520/reverse-skill@competition-crypto-mobile

指定 Agent (Claude Code)

npx skills add zhaoxuya520/reverse-skill --skill competition-crypto-mobile -a claude-code -g -y

安装 repo 全部 skill

npx skills add zhaoxuya520/reverse-skill --all -g -y

预览 repo 内 skill

npx skills add zhaoxuya520/reverse-skill --list

SKILL.md

Frontmatter

{
    "name": "competition-crypto-mobile",
    "description": "Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for crypto, encoding, steganography, APK, IPA, and mobile trust-boundary challenges. Use when the user asks to decode a blob, recover a transform chain or key, inspect hidden media payloads, hook an APK or IPA signer, inspect app storage, or replay mobile request-signing logic. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here."
}

Competition Crypto Mobile

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 active challenge depends on recovering a transform chain, hidden media payload, mobile signing path, or local trust boundary.

Reply in Simplified Chinese unless the user explicitly requests English.

Quick Start

Decide whether the dominant path is crypto, stego, or mobile.
Recover transforms in order; do not jump straight to the fanciest algorithm.
Record exact parameters and boundaries that affect the result.
Hook the narrowest mobile boundary that proves the behavior.
Reproduce the plaintext, payload, signed request, or accepted branch.

Workflow

1. Crypto And Encoding

Reconstruct the chain step by step: container, compression, encoding, xor or substitution, crypto, integrity, final parse.
Keep exact keys, IVs, nonces, salts, tags, offsets, and byte order.

2. Stego

Inspect metadata, chunk layout, palettes, alpha planes, LSBs, thumbnails, trailers, and transcoding artifacts.
Rank decode attempts by evidence, not by brute-force curiosity.

3. Mobile

Start with manifest or plist, exported components, deeplinks, native libs, shared prefs, local DBs, and configs.
Trace signer logic, token storage, SSL pinning, protobuf or RPC boundaries, and native bridge calls.

Read This Reference

Load references/crypto-mobile.md for the transform checklist, hook targets, and evidence packaging.
If the task is specifically about Android dynamic tracing, signer hooks, JNI boundaries, or pinning checks, prefer $competition-android-hooking.
If the task is specifically about iOS runtime tracing, Keychain access, Objective-C or Swift hooks, or pinning checks inside an IPA, prefer $competition-ios-runtime.
If the task is specifically about media carriers, hidden channels, thumbnails, or appended trailers, prefer $competition-stego-media.