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-encryption-keys-from-binariesReverse engineering and fuzzing

extracting-encryption-keys-from-binaries

⁨Locates candidate encryption keys in a binary by finding high-entropy fixed-size⁩

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-encryption-keys-from-binaries

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

SignatureSigned, ed25519
6Y8nZKSDmb…edjEQwAw==The CLI checks the SHA-256 and the signature before it writes a file.
Package7b99166b…8e5d517c
7b99166b17aa…23808e5d517c4 files · ⁦3.1 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-encryption-keys-from-binaries@da7600a

When to Use

  • You have a sample with hardcoded crypto and want to surface candidate keys/IVs (16/24/32-byte high-entropy blocks) and passphrase strings.
  • You are recovering material to decrypt config, C2 traffic, or ransomware test vectors.

Do not use entropy alone as proof a region is a key — corroborate with proximity to crypto constants/APIs and by attempting decryption. This skill reads the binary statically and executes nothing.

Prerequisites

  • The binary (read inertly). Pairs well with the crypto-constant scanner.

Safety & Handling

  • Read bytes statically; handle recovered keys as sensitive and store securely.

Workflow

Step 1: Find high-entropy key-sized regions

bash
python scripts/analyst.py keys sample.bin

Slides a window of 16/24/32 bytes and reports regions whose entropy exceeds a threshold (likely random key material), with offsets.

Step 2: Surface printable secrets

Extract printable strings that look like passphrases/hex keys (e.g., 32/64-hex, base64 of 16/32 bytes).

Step 3: Corroborate

Rank candidates by proximity to crypto constants/API references and confirm by decrypting a known ciphertext.

Step 4: Document

Record candidate keys, sizes, offsets, and the corroborating evidence.

Validation

  • Candidate regions are exactly key-sized (16/24/32 bytes) and high-entropy.
  • Hex/base64 key strings are length-consistent with a real key size.
  • A candidate is confirmed only by successful decryption, not entropy alone.

Pitfalls

  • Compressed/packed data producing many false high-entropy regions — unpack first.
  • Keys derived at runtime (KDF) not present statically.
  • Endianness/encoding of the key (raw vs hex vs base64) before use.

References

  • See references/api-reference.md for the extractor.
  • FIPS 197 and ATT&CK T1573 (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, 2026da7600a7b99166bSigned–

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