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-a-sample-management-workflowMalware and ransomware analysis

building-a-sample-management-workflow

⁨Establishes a disciplined malware sample repository: content-addressed storage by⁩

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-a-sample-management-workflow

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

SignatureSigned, ed25519
fYK7tEUaAx…OJB4GpBg==The CLI checks the SHA-256 and the signature before it writes a file.
Packageb35ae394…353db5a9
b35ae394495b…4ab3353db5a94 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/building-a-sample-management-workflow@da7600a

When to Use

  • You are accumulating malware samples and need a repeatable, safe way to store and find them.
  • You need metadata and provenance (source, date, case) attached to every sample.
  • You want content-addressed storage so the same sample is never duplicated or misnamed.

Do not use original filenames or loose folders as the organizing principle — names are attacker-controlled and collide; address samples by hash.

Prerequisites

  • The hashing skill for content addressing; encrypted/password-protected archive tooling.
  • A defined storage location inside the isolated lab.

Safety & Handling

  • Store every sample inside a password-protected archive (commonly infected) so it cannot auto-execute or be scanned/quarantined by host AV.
  • Strip the executable bit / neutralize the extension at rest; restore only inside the lab.

Workflow

Step 1: Content-address on intake

On receipt, compute SHA-256 and store the sample under a path derived from its hash (e.g., samples/ab/cd/<sha256>), preventing duplicates and name collisions.

bash
python scripts/analyst.py intake sample.bin --source "phishing-case-42" --store ./samples

Step 2: Record metadata

Write a metadata record per sample: hashes, original name, source, intake date, case ID, file type, and analyst — kept next to the sample or in an index.

Step 3: Archive safely

Wrap the sample in a password-protected archive; keep the inert copy out of host AV's reach and the metadata in plaintext for searchability.

Step 4: Maintain chain of custody

Append-only log each access/action (who, when, what) so the sample's handling is auditable.

Build a searchable index over metadata so samples can be found by hash, family, source, or case without touching the raw bytes.

Validation

  • The same sample always lands at the same hash-derived path (idempotent intake).
  • Every sample has a complete metadata record and an access log entry.
  • Samples are stored password-protected; metadata is searchable in plaintext.

Pitfalls

  • Organizing by attacker-supplied filename, causing collisions and confusion.
  • Storing live samples unarchived where host AV deletes them mid-analysis.
  • Losing provenance, so an indicator cannot be traced back to its case.

References

  • See references/api-reference.md for the intake/indexer.
  • NIST SP 800-86 and MalwareBazaar conventions (linked in frontmatter).

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesYesYes
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, 2026da7600ab35ae394Signed–

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