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/extracting-config-from-a-running-sampleMalware and ransomware analysis

extracting-config-from-a-running-sample

⁨Extracts an embedded malware configuration (C2 hosts, ports, campaign IDs, keys) from⁩

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/extracting-config-from-a-running-sample

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

SignatureSigned, ed25519
lF5CFi5W/X…Qad533Bw==The CLI checks the SHA-256 and the signature before it writes a file.
Package08d789f6…5196a478
08d789f66117…f7d95196a4784 files · ⁦3.0 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/extracting-config-from-a-running-sample@da7600a

When to Use

  • You have a process memory dump of a detonated sample whose config is decrypted in memory.
  • You need to recover C2 endpoints, ports, campaign/botnet IDs, mutexes, and keys.

Do not use this to detonate the sample — it consumes a dump already captured in an isolated sandbox. For static-only config decryption, use the dedicated config-decryptor workflow.

Prerequisites

  • A process memory dump (.dmp/raw region) captured after the config was decrypted.

Safety & Handling

  • Treat the dump as malicious data; read it inertly and defang recovered endpoints.

Workflow

Step 1: Hunt config indicators

bash
python scripts/analyst.py hunt process.dmp

Scans for URLs, IPv4:port pairs, mutex-like tokens, base64 blobs, and printable key/value candidates in decrypted regions.

Step 2: Decode obfuscation layers

For candidate blobs, try common transforms (single-byte XOR brute force, base64) and re-scan the decoded output for endpoints.

Step 3: Structure and validate the config

Assemble recovered fields into a structured config and sanity-check (valid hosts, plausible ports, consistent campaign IDs).

Step 4: Defang and report

Defang hosts/URLs and document the offsets where the config was recovered.

Validation

  • Recovered endpoints are real, parseable hosts/ports — not random byte noise.
  • XOR/base64 decode is confirmed by the decoded output containing new endpoints/strings.
  • The final config is defanged before sharing.

Pitfalls

  • Mistaking unrelated in-memory URLs (browser, OS) for C2 — corroborate with the sample's region.
  • Single-byte XOR brute force producing coincidental strings; require multiple corroborating hits.
  • Reporting raw, live C2 endpoints without defanging.

References

  • See references/api-reference.md for the hunter/decoder.
  • ATT&CK T1140 and T1027 (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, 2026da7600a08d789f6Signed–

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