aeondave/strace
offensive-tools/rev/strace/SKILL.md
strace: Linux syscall tracer for observing file, process, network, memory, and signal behavior at runtime. Use when you need to understand what a binary really does under execution, debug loader failures, trace sandboxed challenges, or triage malware and exploit behavior from the kernel boundary.
$ install --global
skillsauthnpx skillsauth add aeondave/malskill straceInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 19, 2026, 4:56 AM131.5s1 file scanned
SKILL.md
- name:
- strace
- description:
- strace: Linux syscall tracer for observing file, process, network, memory, and signal behavior at runtime. Use when you need to understand what a binary really does under execution, debug loader failures, trace sandboxed challenges, or triage malware and exploit behavior from the kernel boundary.
- compatibility:
- Linux primary; requires ptrace capability; not a native Windows tool
- author:
- AeonDave
- version:
- 1.0
strace
Runtime truth serum for Linux programs: if the kernel saw it, strace can usually tell you.
When to use strace
Use strace when you need to:
- see opened files, sockets, child processes, and exec chains
- debug missing libraries, bad paths, permission failures, or seccomp kills
- observe exact syscall arguments around exploit or malware activity
- confirm environment assumptions before touching the target in a debugger
Quick Start
# Trace a process and its syscalls
strace ./chall
# Follow children and save output
strace -f -o trace.log ./chall
# Show more string data
strace -f -s 256 ./chall
High-Value Workflows
Scope the trace to what matters
strace -f -e trace=file ./chall
strace -f -e trace=network,process ./chall
strace -f -e trace=openat,execve,connect ./chall
Attach to an existing process
strace -p 1234
strace -f -p 1234 -e trace=file,network
Timing and descriptor-aware logging
strace -ff -tt -yy -o trace ./chall
Practical Notes
- Start with
-f -s 256 -o trace.logfor a readable baseline that survives noisy runs. -e trace=fileis excellent for loader and path debugging.-yyhelps map file descriptors and socket addresses to something human-friendly.- Pair with
ltracewhen libc-level behavior matters more than raw syscalls.
Caveats
straceslows programs down and can perturb timing-sensitive targets.- Anti-debug or ptrace-restricted environments may block attach or distort behavior.
- Syscall visibility does not automatically reveal higher-level intent; correlate with binary context.
Resources
No bundled scripts/, references/, or assets/.
Use the strace man page for class filters, decoding controls, and fault-injection features.
Related Skills
aeondave/offensive-linux-role
data-ai
VerifiedTrustedCommunity
Scoped routing: Linux operator; hosts, sessions, users, services, packages, logs, containers, SSH, network paths, privilege evidence.
4SKILL.mdUpdated Jun 5, 2026
aeondave/ics-technique
development
VerifiedTrustedCommunity
Offensive methodology for ICS/OT/SCADA environments in authorized industrial penetration testing and red team operations. Use when assessing PLCs, RTUs, HMIs, engineering workstations, historians, or field devices running Modbus, DNP3, EtherNet/IP, S7comm/S7+, Profinet, IEC 60870-5-104, BACnet, or OPC-UA. Covers passive OT network enumeration, protocol-level device interrogation, PLC coil/register read-write attacks, HMI session exploitation, historian and engineering workstation compromise, and safe escalation rules for critical infrastructure scope. Does not cover: general IT network exploitation (network-technique), physical hardware interfaces UART/JTAG/SPI (hardware-technique), wireless sensor network attacks (wireless-technique), RF/SDR signal analysis (hardware-ctf or wireless-technique), or CTF-framed ICS lab tasks (ics-ctf).
4SKILL.mdUpdated Jun 2, 2026
aeondave/game-technique
tools
VerifiedTrustedCommunity
Offensive methodology for authorized game security assessments, game client security research, and game-adjacent penetration testing in real-world engagements. Use when assessing game clients for cheating vulnerabilities, testing anti-cheat effectiveness, auditing game server protocols for score manipulation or economic fraud, reverse engineering game DRM or license validation, analyzing game save file protection, or assessing game mod/plugin security. Covers: process memory scanning and manipulation (Cheat Engine methodology), game binary reversing for license and DRM bypass, game network protocol analysis and packet replay, anti-cheat mechanism analysis, save file format reversing and tampering, speed hack and value injection techniques. Does NOT cover: CTF game challenges (game-ctf), game engine source code auditing (web-exploit-technique or vuln-search-technique for the backend), or general binary exploitation (pwn-ctf or reversing-technique).
4SKILL.mdUpdated Jun 2, 2026
aeondave/hardware-technique
development
VerifiedTrustedCommunity
Auth assessment: hardware/embedded methodology; UART/JTAG/SWD/SPI/I2C, firmware extraction, boot/debug paths, embedded OS evidence.
4SKILL.mdUpdated Jun 2, 2026