Vai al contenuto
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
meltedinhex/analyzing-elf-binaries-on-linuxReverse engineering e fuzzing

analyzing-elf-binaries-on-linux

⁨Statically analyzes Linux ELF malware: ELF header and sections, dynamic symbols⁩

v1.0.03 installazioni+3 in 7 giorni24 StelleApache-2.0sincronizzato 10 ore fa

Installa

Non hai ancora la CLI di NotHoly? Installala prima.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install meltedinhex/analyzing-elf-binaries-on-linux

Scrive in ⁦~/.notholy/skills⁩ dopo aver controllato la firma e lo SHA-256.

FirmaFirmato, ed25519
QWdNyk2b1E…VhPkS2CQ==La CLI controlla lo SHA-256 e la firma prima di scrivere qualsiasi file.
Pacchetto8b52f1c4…a4b2e53a
8b52f1c425bb…3079a4b2e53a4 file · ⁦3.6 KB⁩
ScansioneMedio2 segnalazioni
  • Script eseguibile incluso nella skillscripts/analyst.py
  • Link a domini esterni
Vedi la scansione completa
Sorgentegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/analyzing-elf-binaries-on-linux@da7600a

Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.

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

bash
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

  • See references/api-reference.md for the ELF analyzer.
  • ELF/System V ABI spec and pyelftools (linked in frontmatter).

File di questa versione

Permessi

PermessoDichiaratoTrovato dalla scansione
Legge fileNoNo
Scrive fileNoNo
Esegue comandi shellSìSì
Usa la reteSìSì
Usa i connettoriNoNo
Controlla un browserNoNo

Segnalazioni della scansione

Rivisto il 13 nov 2026

  1. MediaFile · Script eseguibile incluso nella skillscripts/analyst.py
  2. InfoLink · Link a domini esterni

Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.

VersionePubblicataCommitSHA-256FirmaCambio di permessi
v1.0.013 nov 2026da7600a8b52f1c4Firmata–

Chiedi tutto quello che il tuo perimetro consente.

Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.

  1. 1/3

    Crea l'account

    Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.

    PrivatoAzienda
  2. 2/3

    Aggiungi crediti

    Con carta. Paghi a token, senza abbonamento.

    $5.00ricarica minima
  3. 3/3

    Chiedi

    In chat, oppure installa la CLI ed esegui notholy login nel terminale.

    $ notholy login