aeondave/ltrace
offensive-tools/rev/ltrace/SKILL.md
ltrace: Linux library-call tracer for glibc and dynamically linked userspace APIs. Use when you need to watch `malloc`, `strcmp`, crypto helpers, networking wrappers, or other imported functions at a level above raw syscalls during reverse engineering or runtime triage.
$ install --global
skillsauthnpx skillsauth add aeondave/malskill ltraceInstall 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 AM206.7s1 file scanned
SKILL.md
- name:
- ltrace
- description:
- ltrace: Linux library-call tracer for glibc and dynamically linked userspace APIs. Use when you need to watch `malloc`, `strcmp`, crypto helpers, networking wrappers, or other imported functions at a level above raw syscalls during reverse engineering or runtime triage.
- compatibility:
- Linux primary; best with dynamically linked binaries; not reliable for static or heavily obfuscated targets
- author:
- AeonDave
- version:
- 1.0
ltrace
If strace shows what the kernel saw, ltrace shows what userland asked its libraries to do.
When to use ltrace
Use ltrace when you need to:
- watch libc/API usage such as
strcmp,fopen,memcpy, orsystem - infer control-flow choices from arguments and return values
- identify likely string checks, password comparisons, or parsing logic
- complement
stracewith a friendlier view of dynamic library behavior
Quick Start
# Trace library calls
ltrace ./chall
# Follow children and save output
ltrace -f -o ltrace.log ./chall
# Show longer strings
ltrace -f -s 256 ./chall
High-Value Workflows
Focus on suspicious calls
ltrace -e strcmp+strncmp+memcmp ./chall
ltrace -e malloc+free+realloc ./chall
ltrace -e fopen+fread+fwrite+system ./chall
Attach to an already running process
ltrace -p 1234
Practical Notes
- Start here when you suspect a challenge is hiding comparisons or parser behavior in libc calls.
- Combine with
stringsto guess a secret check, then useltrace -e strcmp+memcmpto confirm it. - Pair with
stracewhen you need both the high-level call and the final syscall effect.
Caveats
- Static binaries, direct syscalls, or stripped custom runtimes reduce usefulness sharply.
- Some optimized calls inline away the exact function you hoped to observe.
- Anti-debug protections can interfere just as they do with other ptrace-based tools.
Resources
No bundled scripts/, references/, or assets/.
Use the ltrace man page for expression filters, prototype handling, and timing output.
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