Skip to content

zhaoxuya520/reverse-skill / CTF-Sandbox-Orchestrator/competition-crypto-mobile

competition-crypto-mobile

Verified

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.

FileKindSize
SKILL.mdskill md2.8 KB
agents/openai.yamlconfig376 B
references/crypto-mobile.mdmarkdown932 B

references/crypto-mobile.md

View on GitHub
# Crypto, Stego, And Mobile Checklist

## Crypto

- Work in order: container -> compression -> encoding -> xor/substitution -> crypto -> integrity -> parse
- Recognition is not recovery; reproduce the actual plaintext or downstream artifact
- Keep exact parameters in one compact evidence block

## Stego

- Check metadata, chunk layout, palettes, alpha, LSBs, thumbnails, appended trailers
- Prefer evidence-driven decode attempts over blind brute force

## Mobile

- Check manifest/plist, exported components, deeplinks, native libs, shared prefs, local DBs, configs
- Hook the narrowest boundary: signer, crypto helper, protobuf edge, keystore access, WebView bridge
- Correlate static evidence and dynamic evidence before concluding

## Common Pitfalls

- Reporting only algorithm names with no reproduced artifact
- Scattering transform stages across many bullets
- Hooking too late and missing the trust boundary that matters
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall