resolving-dynamic-api-hashing
Resolves dynamically hashed Windows API names by brute-forcing observed hash constants
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/resolving-dynamic-api-hashingScrive in ~/.notholy/skills dopo aver controllato la firma e lo SHA-256.
FirmaFirmato, ed25519
Pacchetto0ef6dbed…2a82345b
0ef6dbed1c97…539c2a82345b4 file · 3.3 KBScansioneMedio3 segnalazioni
- injection.no_confirmationSKILL.md:77
- Script eseguibile incluso nella skillscripts/analyst.py
- Link a domini esterni
Sorgentegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/resolving-dynamic-api-hashing@da7600a
Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.
In questa pagina
When to Use
- A sample resolves APIs by hash (no plaintext import names) and you have the hash constants from disassembly.
- You need to map each hash back to an API/DLL name to understand functionality.
Do not use this to execute the resolver — it computes hashes over a name wordlist statically and matches them to your observed constants.
Prerequisites
- The hash constants observed in the binary and (optionally) a names wordlist.
Workflow
Step 1: Identify the algorithm
python scripts/analyst.py id 0x6A4ABC5BComputes the constant under each supported algorithm against a built-in seed list to suggest which algorithm/seed reproduces known API hashes.
Step 2: Resolve hashes against a wordlist
python scripts/analyst.py resolve hashes.txt --algo ror13 --wordlist names.txtBrute-forces the provided hashes against the wordlist using the chosen algorithm and reports matches.
Step 3: Annotate the disassembly
Label resolved call sites with their API names to recover behavior.
Step 4: Document the routine
Record the algorithm, seed/initial value, and any key so the routine is reusable.
Validation
- The chosen algorithm reproduces at least one known API hash (sanity anchor).
- Resolved names are real exported symbols of plausible DLLs.
- Unresolved hashes are reported, not silently dropped.
Pitfalls
- Wrong endianness/rotation direction producing no matches — try variants.
- Algorithms seeded with a per-sample key; without the key, matches fail.
- Case sensitivity: some routines hash uppercased names, others as-is.
References
- See
references/api-reference.mdfor the resolver. - ATT&CK T1027.007 and the Windows API Index (linked in frontmatter).
File di questa versione
references/11.2 KB
- api-reference.md1.2 KB
scripts/13.3 KB
- analyst.py3.3 KB
- LICENSE340 B
- SKILL.md2.6 KB
Permessi
| Permesso | Dichiarato | Trovato dalla scansione |
|---|---|---|
| Legge file | No | No |
| Scrive file | No | No |
| Esegue comandi shell | Sì | Sì |
| Usa la rete | Sì | Sì |
| Usa i connettori | No | No |
| Controlla un browser | No | No |
Segnalazioni della scansione
Rivisto il 13 nov 2026
- MediaPrompt injection · injection.no_confirmationSKILL.md:77
- MediaFile · Script eseguibile incluso nella skillscripts/analyst.py
- InfoLink · Link a domini esterni
Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.
| Versione | Pubblicata | Commit | SHA-256 | Firma | Cambio di permessi |
|---|---|---|---|---|---|
| v1.0.0 | 13 nov 2026 | da7600a | 0ef6dbed | Firmata | – |
Altro da meltedinhex
Tutto da questo editore- writing-yara-rules-from-reversed-codemeltedinhex/writing-yara-rules-from-reversed-code4
- validating-detections-with-atomic-testsmeltedinhex/validating-detections-with-atomic-tests4
- writing-suricata-and-snort-rulesmeltedinhex/writing-suricata-and-snort-rules3
- writing-sigma-detection-rulesmeltedinhex/writing-sigma-detection-rules3
Altro in API, SaaS e identità
Vai alla categoria- testing-for-sensitive-data-exposuremukul975/testing-for-sensitive-data-exposure5
- performing-jwt-none-algorithm-attackmukul975/performing-jwt-none-algorithm-attack5
- sharp-edgestrailofbits/sharp-edges4
- hydraaeondave/hydra4
- implementing-google-workspace-admin-securitymukul975/implementing-google-workspace-admin-security4
- implementing-api-security-posture-managementmukul975/implementing-api-security-posture-management4
Chiedi tutto quello che il tuo perimetro consente.
Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.
- 1/3
Crea l'account
Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.
PrivatoAzienda - 2/3
Aggiungi crediti
Con carta. Paghi a token, senza abbonamento.
$5.00ricarica minima - 3/3
Chiedi
In chat, oppure installa la CLI ed esegui notholy login nel terminale.
$ notholy login