Skip to content
cccskills
FreePublished on GitHub

analyzing-elf-binaries-on-linux

Statically analyzes Linux ELF malware: ELF header and sections, dynamic symbols and imports, segment permissions, embedded strings, and packing indicators to infer capability without execution. Activates for requests to analyze an ELF binary, Linux malware, or shared object.

The English summary is being prepared. Showing the original description.

See how to install

Files included (4)

  • SKILL.md3.1 KB
  • LICENSE340 B
  • references/api-reference.md1.2 KB
  • scripts/analyst.py3.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Analyzing ELF Binaries on Linux

When to Use

  • You have a Linux executable or shared object and need to assess it statically.
  • You want to read the ELF header, segments, dynamic symbols, and strings to infer behavior.
  • You are checking for static linking, stripped symbols, or packing.

Do not use symbol absence as proof of nothing — stripped or statically linked Go/Rust binaries hide structure; switch to disassembly when static metadata is thin.

Prerequisites

  • readelf/nm/strings (binutils) or pyelftools (pip install pyelftools).
  • The sample in neutralized form inside the lab.

Safety & Handling

  • Static only: parse the file; do not set it executable or run it.

Workflow

Step 1: Read the ELF header

python scripts/analyst.py analyze sample.elf

Note class (ELF32/64), endianness, type (EXEC/DYN/REL), machine (x86-64, ARM, MIPS), and whether it is stripped.

Step 2: Examine segments and section permissions

Writable+executable segments, or a single large segment, suggest packing or self-modifying code. Compare PT_LOAD permissions against expectations.

Step 3: Inspect dynamic symbols and needed libraries

Imported functions hint at capability: socket/connect (network), ptrace (anti-debug or injection), fork/execve (process control), crypt/EVP_* (encryption).

Step 4: Detect static linking and packing

Static binaries lack a dynamic symbol table and NEEDED entries. High whole-file entropy and a tiny section table suggest a packer (e.g. UPX leaves UPX! markers).

Step 5: Skim strings and constructors

Check .init_array/constructors (code before main), and strings for paths, URLs, and shell commands.

Validation

  • Header type and segment permissions are consistent with the inferred behavior.
  • Imported symbols correspond to plausible capabilities.
  • Packing call (entropy + missing sections) matches the strings observed.

Pitfalls

  • Assuming dynamic symbols are complete — they only cover imported/exported names, not internal functions.
  • Treating a stripped Go binary as "empty"; its structure lives in runtime metadata, not the symbol table.
  • Ignoring constructors/.init_array, which run before main.

References

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Reverses Android malware: unpacking APKs, decompiling DEX bytecode to readable Java, auditing the manifest for abused permissions and components, and locating dynamically loaded or native payloads. Activates for requests to analyze an APK, decompile DEX, or investigate a suspicious Android app.

The English summary is being prepared. Showing the original description.

meltedinhex/analyst-ai-pack22Updated Jul 7, 2026

Analyzes API call traces from a sandbox or API monitor (JSON) to group calls by category, reconstruct high-level behaviors (process injection, file drops, network, crypto), and flag suspicious call sequences. Activates for requests to analyze an API trace, interpret sandbox API logs, or identify behavior from Win32/Native API calls.

The English summary is being prepared. Showing the original description.

meltedinhex/analyst-ai-pack22Updated Jul 7, 2026

Analyzes Windows Authenticode signatures on PE files: checking for a signature, reading the signer certificate chain, detecting revoked/expired/stolen certs, and recognizing signature-stripping and catalog-signing abuse. Activates for requests to analyze a code signature, verify Authenticode, or assess signer trust on a PE.

The English summary is being prepared. Showing the original description.

meltedinhex/analyst-ai-pack22Updated Jul 7, 2026

Analyzes banking trojan webinject configurations to extract targeted institutions, injected JavaScript/HTML, and data-theft hooks, mapping the fraud workflow. Activates for requests to analyze banking trojan webinjects, parse a webinject config, or map targeted banks and credential-theft injections.

The English summary is being prepared. Showing the original description.

meltedinhex/analyst-ai-pack22Updated Jul 7, 2026

Analyzes Python-based malware packaged as PyInstaller/py2exe executables by detecting the packer, locating the embedded archive, and identifying bundled .pyc modules for extraction and decompilation. Activates for requests to analyze compiled Python malware, unpack a PyInstaller binary, or extract pyc modules from a frozen Python executable.

The English summary is being prepared. Showing the original description.

meltedinhex/analyst-ai-pack22Updated Jul 7, 2026

Analyzes cryptojacking/coinminer malware by extracting mining pool endpoints (stratum), wallet addresses, algorithm and miner identifiers (XMRig and forks), and persistence or resource-control settings from static strings and config. Activates for requests to analyze a cryptominer, extract mining pool and wallet IOCs, or identify coinminer configuration.

The English summary is being prepared. Showing the original description.

meltedinhex/analyst-ai-pack22Updated Jul 7, 2026

See all skills by meltedinhex

Report a problem with this skill