binary-re-dynamic-analysis
Analyze Binaries with Dynamic Runtime Tracing
Security researchers need to observe actual binary behavior at runtime, not just static code. This skill provides safe, sandboxed execution with QEMU emulation, GDB debugging, and Frida hooking to trace syscalls, inspect memory, and validate reverse engineering hypotheses.
์คํฌ ZIP ๋ค์ด๋ก๋
Claude์์ ์ ๋ก๋
์ค์ โ ๊ธฐ๋ฅ โ ์คํฌ โ ์คํฌ ์ ๋ก๋๋ก ์ด๋
ํ ๊ธ์ ์ผ๊ณ ์ฌ์ฉ ์์
ํ ์คํธํด ๋ณด๊ธฐ
"binary-re-dynamic-analysis" ์ฌ์ฉ ์ค์ ๋๋ค. Run this binary with QEMU strace and tell me what files it accesses
์์ ๊ฒฐ๊ณผ:
Executed binary using QEMU user-mode emulation with syscall tracing. Observed file access patterns:
- Read: /etc/config.json (configuration data)
- Write: /var/log/app.log (logging output)
- Read: /usr/lib/libssl.so (SSL library dependency)
No network syscalls detected. Binary appears to be a local configuration processor.
"binary-re-dynamic-analysis" ์ฌ์ฉ ์ค์ ๋๋ค. Use Frida to hook the authenticate() function and show me what password it checks
์์ ๊ฒฐ๊ณผ:
Attached Frida to running binary and intercepted authenticate() function at offset 0x2a40. Captured argument at call time: password buffer contains "admin123". Function returns 1 (success) when this value matches, 0 otherwise. This appears to be a hardcoded authentication check.
"binary-re-dynamic-analysis" ์ฌ์ฉ ์ค์ ๋๋ค. Debug this binary with GDB and examine memory at the stack pointer when main() starts
์์ ๊ฒฐ๊ณผ:
Started binary under QEMU with GDB server on port 1234. Set breakpoint at main() symbol. Execution paused at 0x000084c0. Stack pointer (sp) is at 0xbefff7a0. Memory dump shows:
0xbefff7a0: argc=2
0xbefff7a4: argv pointer
0xbefff7a8: environment variables
Stack is properly aligned for ARM ABI.
๋ณด์ ๊ฐ์ฌ
๋ฎ์ ์ํThis is a legitimate security research and reverse engineering skill for authorized binary analysis. All static findings are false positives related to documentation examples showing proper use of analysis tools. The skill requires explicit human approval before executing any binaries and emphasizes sandbox isolation. No malicious patterns detected.
๋ฎ์ ์ํ ๋ฌธ์ (1)
์ํ ์์ธ
โ๏ธ ์ธ๋ถ ๋ช ๋ น์ด (3)
๐ ํ์ผ ์์คํ ์ก์ธ์ค (2)
ํ์ง ์ ์
๋ง๋ค ์ ์๋ ๊ฒ
Malware Analysis in Sandbox
Security analysts can safely execute suspicious binaries in isolated QEMU environments to observe network behavior, file modifications, and syscall patterns without risking the host system.
Cross-Architecture Firmware Debugging
Embedded systems developers can debug ARM or MIPS binaries on x86 development machines using QEMU emulation with GDB, eliminating the need for physical hardware during analysis.
Reverse Engineering Protected Binaries
Penetration testers can use Frida hooks to intercept cryptographic functions, authentication checks, and network protocols in compiled applications to understand their behavior and find vulnerabilities.
์ด ํ๋กฌํํธ๋ฅผ ์ฌ์ฉํด ๋ณด์ธ์
Use QEMU to run this ARM binary and trace all syscalls to identify what network connections it makes
Start this binary under QEMU with GDB attached, set a breakpoint at address 0x8400, and show me the register state when it hits
Create a Frida script to intercept all connect() calls in this binary and log the IP addresses and ports it tries to reach
Run this ARM32 binary in a Docker container on macOS with platform emulation and capture all library loading events using LD_DEBUG
๋ชจ๋ฒ ์ฌ๋ก
- Always get explicit human approval before executing any binary and document the sandbox configuration being used
- Start with QEMU syscall tracing before deeper analysis to understand high-level behavior safely
- Use network isolation in sandbox environments when analyzing binaries with unknown network behavior
ํผํ๊ธฐ
- Running unknown binaries without sandbox isolation or on production systems
- Attempting to use Frida with QEMU user-mode emulation (architecture mismatch will fail)
- Using /tmp directory paths for Docker volume mounts on Colima (fails silently, use home directory instead)
์์ฃผ ๋ฌป๋ ์ง๋ฌธ
Can this skill execute Windows PE binaries?
Is it safe to run malware with this skill?
Why does Frida not work with QEMU emulated binaries?
What sandbox configuration should I use for unknown binaries?
Can I debug ARM binaries on an x86 machine?
How do I handle anti-debugging techniques in binaries?
๊ฐ๋ฐ์ ์ธ๋ถ ์ ๋ณด
์์ฑ์
2389-research๋ผ์ด์ ์ค
MIT
๋ฆฌํฌ์งํ ๋ฆฌ
https://github.com/2389-research/claude-plugins/tree/main/binary-re/skills/dynamic-analysis์ฐธ์กฐ
main
ํ์ผ ๊ตฌ์กฐ
๐ SKILL.md