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/defeating-string-and-api-obfuscationAPI, SaaS e identità

defeating-string-and-api-obfuscation

⁨Recovers obfuscated strings and resolves dynamically loaded APIs in malware:⁩

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/defeating-string-and-api-obfuscation

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

FirmaFirmato, ed25519
G0L9+MKrBg…Qwzg8VDg==La CLI controlla lo SHA-256 e la firma prima di scrivere qualsiasi file.
Pacchettob2d1f914…e8c2da27
b2d1f914d95c…8712e8c2da274 file · ⁦3.7 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/defeating-string-and-api-obfuscation@da7600a

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

When to Use

  • A binary has few readable strings because they are XOR/stack-encoded or built at runtime.
  • The import table is sparse because APIs are resolved by hash at runtime.
  • You need to recover C2 URLs, paths, and the real API set to understand behavior.

Do not use plain strings and conclude "no indicators" — modern malware hides strings; absence of readable strings is itself a sign of obfuscation.

Prerequisites

  • A disassembler/decompiler to read the decode routine, plus the bundled XOR/hash tooling.
  • Optionally FLOSS for automated stack/decoded-string recovery.

Workflow

Step 1: Recognize the obfuscation type

text
Stack strings  : bytes mov'd to the stack one/few at a time, then used
Single-byte XOR: a loop XORing a buffer with a constant
Multi-byte/RC4 : a keyed stream over a blob
API hashing    : a hash compared against export-name hashes to resolve functions

Step 2: Recover XOR-encoded strings

If you find the key and ciphertext, decode directly. The script brute-forces single-byte XOR and surfaces readable results:

bash
python scripts/analyst.py xor-strings sample.bin

Step 3: Reconstruct stack strings

Read the decompiler to collect the byte sequence assembled on the stack and reassemble it. For volume, FLOSS emulates and extracts these automatically.

Step 4: Resolve API hashing

Identify the hash algorithm (often ROR13/ROR7 additive, or djb2). Precompute hashes for known export names and match the constants in the binary back to functions:

bash
python scripts/analyst.py api-hash --algo ror13 --hash 0x726774C

Step 5: Reannotate and extract IOCs

Apply recovered strings and API names back in the disassembler and extract the now-visible URLs, paths, and behavior.

Validation

  • Decoded strings are meaningful (URLs, DLL/API names, paths), not random bytes.
  • Resolved API names match the calls' usage in the surrounding code.
  • The recovered API set explains behavior seen dynamically.

Pitfalls

  • Assuming single-byte XOR when it is keyed/RC4; check key length and the decode loop.
  • Using the wrong hash algorithm/seed and getting no matches — verify against a known function.
  • Recovering strings but not feeding them back into the analysis.

References

  • See references/api-reference.md for the XOR and API-hash tools.
  • FLOSS and API-hashing references (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 2026da7600ab2d1f914Firmata–

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