binary-re:triage

To identify the architecture and endianness of an unknown ELF binary, this skill fingerprints the executable using rabin2 and readelf data to extract bits, ABI, and interpreter paths for rapid triage.

Finding linked libraries in a firmware blob is done through dependency discovery, which enumerates shared libraries to assess risk and determine required toolchains for subsequent analysis steps.

Yes, you can use rabin2 to extract entry points and exports from a static executable, listing program entry points and shared-library exports to guide reverse engineering workflows.

Binary triage supports mixed ELF and PE samples during first-contact analysis, fingerprinting unknown executables to classify architecture, ABI, and basic dependencies to guide tool choice.

Yes, you need radare2 installed to perform static analysis and architecture detection, as the skill requires rabin2 from the radare2 suite alongside readelf-based data to extract interpreter paths and dependencies.

Fingerprinting an unknown binary before reverse engineering is necessary to determine architecture, bitness, and dynamic versus static linking, enabling a targeted analysis plan and informed tool selection.