์Šคํ‚ฌ binary-re-dynamic-analysis
๐Ÿ”ฌ

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.

์ง€์›: Claude Codex Code(CC)
โš ๏ธ 66 ๋‚˜์จ
1

์Šคํ‚ฌ ZIP ๋‹ค์šด๋กœ๋“œ

2

Claude์—์„œ ์—…๋กœ๋“œ

์„ค์ • โ†’ ๊ธฐ๋Šฅ โ†’ ์Šคํ‚ฌ โ†’ ์Šคํ‚ฌ ์—…๋กœ๋“œ๋กœ ์ด๋™

3

ํ† ๊ธ€์„ ์ผœ๊ณ  ์‚ฌ์šฉ ์‹œ์ž‘

ํ…Œ์ŠคํŠธํ•ด ๋ณด๊ธฐ

"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.

๋ณด์•ˆ ๊ฐ์‚ฌ

๋‚ฎ์€ ์œ„ํ—˜
v4 โ€ข 1/21/2026

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.

2
์Šค์บ”๋œ ํŒŒ์ผ
1,912
๋ถ„์„๋œ ์ค„ ์ˆ˜
3
๋ฐœ๊ฒฌ ์‚ฌํ•ญ
4
์ด ๊ฐ์‚ฌ ์ˆ˜
๋‚ฎ์€ ์œ„ํ—˜ ๋ฌธ์ œ (1)
Documentation Contains Security Tool Examples
The skill documentation includes examples of using QEMU, GDB, Frida, and strace for binary analysis. These are legitimate security research tools used for authorized reverse engineering. The skill explicitly requires human approval before execution and emphasizes sandbox configuration. All flagged patterns are documentation examples, not executable code.

์œ„ํ—˜ ์š”์ธ

โš™๏ธ ์™ธ๋ถ€ ๋ช…๋ น์–ด (3)
๐Ÿ“ ํŒŒ์ผ ์‹œ์Šคํ…œ ์•ก์„ธ์Šค (2)

ํ’ˆ์งˆ ์ ์ˆ˜

38
์•„ํ‚คํ…์ฒ˜
100
์œ ์ง€๋ณด์ˆ˜์„ฑ
87
์ฝ˜ํ…์ธ 
22
์ปค๋ฎค๋‹ˆํ‹ฐ
88
๋ณด์•ˆ
78
์‚ฌ์–‘ ์ค€์ˆ˜

๋งŒ๋“ค ์ˆ˜ ์žˆ๋Š” ๊ฒƒ

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.

์ด ํ”„๋กฌํ”„ํŠธ๋ฅผ ์‚ฌ์šฉํ•ด ๋ณด์„ธ์š”

Basic Syscall Trace
Use QEMU to run this ARM binary and trace all syscalls to identify what network connections it makes
Debug with Breakpoints
Start this binary under QEMU with GDB attached, set a breakpoint at address 0x8400, and show me the register state when it hits
Hook Network Functions
Create a Frida script to intercept all connect() calls in this binary and log the IP addresses and ports it tries to reach
Cross-Platform Container Execution
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?
This skill focuses on Linux ELF binaries. For Windows PE analysis, you would need Wine or a Windows VM rather than QEMU user-mode emulation.
Is it safe to run malware with this skill?
The skill emphasizes sandbox isolation using QEMU, Docker, or nsjail. However, you must configure appropriate network isolation and get human approval before executing any suspicious binary.
Why does Frida not work with QEMU emulated binaries?
Frida requires native architecture execution to inject its agent. QEMU user-mode creates a different process space that Frida cannot attach to. Use on-device frida-server for cross-arch targets.
What sandbox configuration should I use for unknown binaries?
Start with QEMU user-mode which provides high isolation. Add network blocking, resource limits, and run as unprivileged user. Document your configuration and get approval before execution.
Can I debug ARM binaries on an x86 machine?
Yes, QEMU user-mode emulation allows running ARM binaries on x86 hosts. You can attach gdb-multiarch for debugging. On macOS, use Docker with platform emulation.
How do I handle anti-debugging techniques in binaries?
QEMU user-mode bypasses many anti-debug checks like ptrace detection and /proc inspection. For timing checks, use GDB or patch the detection code. The skill provides mitigation strategies in the documentation.

๊ฐœ๋ฐœ์ž ์„ธ๋ถ€ ์ •๋ณด

์ž‘์„ฑ์ž

2389-research

๋ผ์ด์„ ์Šค

MIT

์ฐธ์กฐ

main

ํŒŒ์ผ ๊ตฌ์กฐ

๐Ÿ“„ SKILL.md