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/identifying-cryptographic-routines-in-binariesReverse engineering and fuzzing

identifying-cryptographic-routines-in-binaries

⁨Identifies cryptographic algorithms embedded in a binary by scanning for well-known⁩

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/identifying-cryptographic-routines-in-binaries

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

SignatureSigned, ed25519
Oy5ByWAqgU…xItuW5Bw==The CLI checks the SHA-256 and the signature before it writes a file.
Packageb11c5c28…a12470e7
b11c5c285c05…dfd8a12470e74 files · ⁦3.4 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/identifying-cryptographic-routines-in-binaries@da7600a

When to Use

  • You need to determine which cryptographic algorithms a sample implements (ransomware crypto, C2 encryption, config protection) by locating constant tables.
  • You want fast triage before manually reversing the crypto routine.

Do not use constant detection as proof of a specific mode/usage — it identifies the primitive, not how it is applied. This skill reads the binary statically and executes nothing.

Prerequisites

  • The binary (read inertly).

Safety & Handling

  • Read bytes statically; treat the sample as malicious data.

Workflow

Step 1: Scan for crypto constants

bash
python scripts/analyst.py scan sample.bin

Searches for AES S-box/Te tables, SHA-256 H/K init constants, MD5 init, ChaCha/Salsa expand 32-byte k sigma, the CRC32 polynomial table, and the base64 alphabet, reporting offsets.

Step 2: Corroborate with imports/strings

Pair constant hits with crypto API imports (CryptDecrypt, BCryptEncrypt, EVP_*) or library strings to confirm.

Step 3: Locate the routine

Use the constant offset to find the referencing function for deeper reversing/key extraction.

Step 4: Document

Record which primitives are present and where, mapping to behavior (e.g., AES → file encryption).

Validation

  • Each hit references a real, named constant table (not a coincidental byte run).
  • Detected primitives are corroborated by imports/strings where possible.
  • Offsets point into the binary and can be navigated in a disassembler.

Pitfalls

  • Statically linked crypto libraries adding constants unused by the malware's logic.
  • Custom/modified S-boxes evading exact-match detection.
  • Assuming AES presence implies ransomware — corroborate with behavior.

References

  • See references/api-reference.md for the scanner.
  • FIPS 197 and FIPS 180-4 constant references (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, 2026da7600ab11c5c28Signed–

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