Skip to content
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/building-config-extractorsMalware and ransomware analysis

building-config-extractors

⁨Builds reusable malware configuration extractors by applying a declarative JSON spec⁩

v1.0.03 installs+3 in 7 days24 StarsApache-2.0synced 10 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install meltedinhex/building-config-extractors

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
+0PkKaEkSt…HjbFq1AA==The CLI checks the SHA-256 and the signature before it writes a file.
Package9b1e780d…59968f75
9b1e780dfbff…20c059968f754 files · ⁦3.3 KB⁩
ScanMedium2 findings
  • Executable script shipped with the skillscripts/analyst.py
  • Links to outside domains
See the full scan
Sourcegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/building-config-extractors@da7600a

When to Use

  • You have reversed a family's config format and want a reusable, declarative extractor instead of one-off scripts.
  • You need to apply a spec (offset, XOR/base64 layers, field map) to many samples and emit structured, defanged config.

Do not use a spec built for one variant blindly on another — re-verify offsets/keys per variant. This skill reads samples statically and executes nothing.

Prerequisites

  • A reversed understanding of the config (location, decode layers, fields) expressed as a JSON spec.

Safety & Handling

  • Read bytes statically; defang recovered endpoints in output.

Workflow

Step 1: Write the extraction spec

Define a JSON spec: blob offset/length (or a marker to search), ordered decode layers (xor with key, base64), and fields (name, offset, length, type: str/u16/u32/ipv4).

Step 2: Run the extractor

bash
python scripts/analyst.py extract sample.bin --spec family.json

Locates the blob, applies decode layers, parses fields, and defangs URL/IP fields.

Step 3: Validate output

Confirm fields are plausible (valid hosts, ports, IDs); adjust the spec as needed.

Step 4: Reuse

Store the spec per family and apply across the corpus.

Validation

  • The spec round-trips on a known sample to the expected config.
  • Decode layers are applied in order and produce readable output.
  • URL/IP fields are defanged in the emitted config.

Pitfalls

  • Hardcoding a variant-specific offset that shifts in other builds — prefer markers.
  • Wrong field endianness (u16/u32 little vs big) producing garbage ports.
  • Forgetting a decode layer (base64 over XOR) and parsing ciphertext as fields.

References

  • See references/api-reference.md for the extractor engine.
  • ATT&CK T1140 and config-extractor framework concepts (linked in frontmatter).

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsYesYes
Uses the networkYesYes
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

  1. MediumFile · Executable script shipped with the skillscripts/analyst.py
  2. InfoLink · Links to outside domains

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v1.0.0Nov 13, 2026da7600a9b1e780dSigned–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login