offensive-tools/rev/objdump/SKILL.md
objdump: binutils inspection and disassembly tool for ELF and many other object formats. Use when you need fast CLI disassembly, section dumps, symbol views, or mixed source and assembly output during reverse engineering, exploit triage, or binary diffing.
npx skillsauth add aeondave/malskill objdumpInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Quick static inspection and disassembly without firing up a full GUI. Tiny hammer, surprisingly sharp.
Use objdump when you need to:
.rodata or .text# Disassemble executable sections
objdump -d ./chall
# Disassemble all sections, not just code-marked ones
objdump -D ./chall
# Intel syntax on x86/x86-64
objdump -d -Mintel ./chall
objdump -d -Mintel ./chall
objdump -t ./chall
objdump -T ./chall
objdump -x ./chall
objdump -s -j .rodata ./chall
objdump -s -j .data ./chall
objdump -S -Mintel ./chall
readelf when you need canonical ELF metadata rather than a friendlier summary.-D is useful for hand-marked shellcode regions or strange packer output where section flags lie.objdump -s -j .rodata with strings when looking for nearby format strings, keys, or banners.gdb, strings, and readelf instead of trusting a single view.No bundled scripts/, references/, or assets/.
Use the GNU binutils manual for architecture-specific -M options and file-format nuances.
data-ai
Scoped routing: Linux operator; hosts, sessions, users, services, packages, logs, containers, SSH, network paths, privilege evidence.
development
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).
tools
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).
development
Auth assessment: hardware/embedded methodology; UART/JTAG/SWD/SPI/I2C, firmware extraction, boot/debug paths, embedded OS evidence.