Skip to content
cccskills
FreePublished on GitHub

handling-malware-samples-safely

Establishes safe practices for acquiring, storing, transferring, and disposing of malware samples: password-protected archives, neutralized extensions, hashing for identity, and chain-of-custody. Activates for requests about safely storing or sharing malware, sample handling hygiene, or defanging artifacts.

The English summary is being prepared. Showing the original description.

See how to install

Files included (4)

  • SKILL.md4.0 KB
  • LICENSE340 B
  • references/api-reference.md1.4 KB
  • scripts/analyst.py2.8 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Handling Malware Samples Safely

When to Use

  • You are receiving, storing, or sharing a malicious file and need to prevent accidental execution or contamination.
  • You need a consistent naming and identity scheme so a sample can be tracked across tools and tickets.
  • You are packaging a sample to send to another analyst or a sandbox.

Do not use these conventions as a substitute for an isolated detonation environment; safe storage prevents accidents but analysis still requires an isolated lab.

Prerequisites

  • An archive tool that supports password-protected, encrypted archives (7-Zip).
  • A hashing utility (sha256sum, certutil, or the bundled script).
  • A defined storage location with restricted access, separate from general file shares.

Safety & Handling

  • Treat every sample as live. Never double-click; never leave it with its original executable extension on a working machine.
  • Store samples inside an encrypted, password-protected archive with the conventional password infected.
  • Neutralize the extension on disk (e.g. sample.exe → sample.exe.bin or sample.exe_) so the OS will not execute it on a stray click.
  • Defang indicators in any text leaving the lab: hxxp://, 1.2.3[.]4, evil[.]com.

Workflow

Step 1: Identify the sample by hash

A sample's identity is its SHA-256, not its filename. Compute hashes immediately:

python scripts/analyst.py hash sample.exe
# md5, sha1, sha256, size, ssdeep-like size bucket

Rename the working copy to its SHA-256 so identity travels with the file:

mv sample.exe 9f86d0818...<sha256>.bin

Step 2: Store in an encrypted archive

7z a -p"infected" -mhe=on <sha256>.7z <sha256>.bin
# -mhe=on encrypts filenames too

Keep the loose, neutralized copy only inside the lab; the archive is the storage/transfer form.

Step 3: Record provenance

Capture where the sample came from, when, and who handled it. The script can emit a JSON metadata record:

python scripts/analyst.py record <sha256>.bin --source "MalwareBazaar" --case CASE-001

Step 4: Defang before sharing

When pasting URLs/IPs into a report or ticket, defang them:

python scripts/analyst.py defang ioc.txt
# http://evil.com/x -> hxxp://evil[.]com/x

Validation

  • 7z l -slt <sha256>.7z shows encrypted headers (filenames not visible without password).
  • The on-disk working copy has a neutralized extension and matches the recorded SHA-256.
  • The provenance record contains source, timestamp, case ID, and all three hashes.
  • No raw clickable URLs/IPs remain in any artifact destined to leave the lab.

Pitfalls

  • Sharing a sample in a plain zip — mail gateways and AV will quarantine or mangle it, and recipients risk accidental execution. Always password-encrypt.
  • Trusting the filename or first-seen label as identity; only the hash is authoritative.
  • Forgetting filename encryption (-mhe=on), which leaks the sample name and your naming scheme.
  • Defanging only URLs but leaving live IPs or email addresses in the report.

References

  • See references/api-reference.md for the hashing, provenance, and defang tooling.
  • MalwareBazaar and NIST SP 800-86 (linked in frontmatter).

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Reverses Android malware: unpacking APKs, decompiling DEX bytecode to readable Java, auditing the manifest for abused permissions and components, and locating dynamically loaded or native payloads. Activates for requests to analyze an APK, decompile DEX, or investigate a suspicious Android app.

The English summary is being prepared. Showing the original description.

meltedinhex/analyst-ai-pack22Updated Jul 7, 2026

Analyzes API call traces from a sandbox or API monitor (JSON) to group calls by category, reconstruct high-level behaviors (process injection, file drops, network, crypto), and flag suspicious call sequences. Activates for requests to analyze an API trace, interpret sandbox API logs, or identify behavior from Win32/Native API calls.

The English summary is being prepared. Showing the original description.

meltedinhex/analyst-ai-pack22Updated Jul 7, 2026

Analyzes Windows Authenticode signatures on PE files: checking for a signature, reading the signer certificate chain, detecting revoked/expired/stolen certs, and recognizing signature-stripping and catalog-signing abuse. Activates for requests to analyze a code signature, verify Authenticode, or assess signer trust on a PE.

The English summary is being prepared. Showing the original description.

meltedinhex/analyst-ai-pack22Updated Jul 7, 2026

Analyzes banking trojan webinject configurations to extract targeted institutions, injected JavaScript/HTML, and data-theft hooks, mapping the fraud workflow. Activates for requests to analyze banking trojan webinjects, parse a webinject config, or map targeted banks and credential-theft injections.

The English summary is being prepared. Showing the original description.

meltedinhex/analyst-ai-pack22Updated Jul 7, 2026

Analyzes Python-based malware packaged as PyInstaller/py2exe executables by detecting the packer, locating the embedded archive, and identifying bundled .pyc modules for extraction and decompilation. Activates for requests to analyze compiled Python malware, unpack a PyInstaller binary, or extract pyc modules from a frozen Python executable.

The English summary is being prepared. Showing the original description.

meltedinhex/analyst-ai-pack22Updated Jul 7, 2026

Analyzes cryptojacking/coinminer malware by extracting mining pool endpoints (stratum), wallet addresses, algorithm and miner identifiers (XMRig and forks), and persistence or resource-control settings from static strings and config. Activates for requests to analyze a cryptominer, extract mining pool and wallet IOCs, or identify coinminer configuration.

The English summary is being prepared. Showing the original description.

meltedinhex/analyst-ai-pack22Updated Jul 7, 2026

See all skills by meltedinhex

Report a problem with this skill