Skip to content

meltedinhex/analyst-ai-pack / skills/resolving-dynamic-api-hashing

resolving-dynamic-api-hashing

Verified

Resolves dynamically hashed Windows API names by brute-forcing observed hash constants against a wordlist of API/DLL names using common malware hashing algorithms (ROR13, djb2, FNV, CRC32). Activates for requests to resolve API hashes, identify hashed imports, or reverse an API hashing routine.

FileKindSize
LICENSEother340 B
SKILL.mdskill md2.6 KB
references/api-reference.mdmarkdown1.2 KB
scripts/analyst.pyscript3.3 KB

references/api-reference.md

View on GitHub
# API Reference: Resolving Dynamic API Hashing

## Overview

`scripts/analyst.py` implements common malware API-hash algorithms (ROR13-add, djb2, FNV-1a, CRC32)
and matches observed 32-bit hash constants against a names wordlist. It is pure computation over
name strings and never loads or executes the sample.

## Dependencies

| Package | Version | Purpose |
|---------|---------|---------|
| (stdlib) | — | binascii (CRC32), JSON, file IO |

## Core functions

### `ror13_add(name)`, `djb2(name)`, `fnv1a(name)`, `crc32(name)`
The supported 32-bit hashing algorithms.

### `identify(value)`
Tries each algorithm against a small seed API list to suggest which algorithm a constant came from.

### `resolve(hashes, algo, names)`
Builds a hash→name table for the wordlist and resolves the provided hashes; reports unresolved.

## Usage

```bash
python scripts/analyst.py id 0x6A4ABC5B
python scripts/analyst.py resolve hashes.txt --algo ror13 --wordlist names.txt
```

## Sources

- MITRE ATT&CK T1027.007 Dynamic API Resolution — https://attack.mitre.org/techniques/T1027/007/
- ROR13 PEB-walk shellcode hashing pattern (public shellcode/RE literature)
- djb2 (Daniel J. Bernstein), FNV-1a (Fowler/Noll/Vo), CRC-32 (ISO 3309) standard definitions
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 319kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 319kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 319kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 319kUpdated Claude CodeCodexVerifiedInstall