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/collecting-volatile-evidence-from-a-suspect-hostReporting and compliance

collecting-volatile-evidence-from-a-suspect-host

⁨Collects volatile evidence from a potentially compromised host in correct order of⁩

v1.0.03 installs+3 in 7 days24 StarsApache-2.0synced 11 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install meltedinhex/collecting-volatile-evidence-from-a-suspect-host

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

SignatureSigned, ed25519
3TASNgMVie…i5tBhdDw==The CLI checks the SHA-256 and the signature before it writes a file.
Packagebc51d343…6c4d9e8e
bc51d343ead5…c8c76c4d9e8e4 files · ⁦3.2 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/collecting-volatile-evidence-from-a-suspect-host@da7600a

When to Use

  • A host is suspected of compromise and you must capture state that disappears on reboot.
  • You are performing live response before isolating or imaging the machine.
  • You need an ordered, integrity-preserving collection for later analysis.

Do not use this as a substitute for full disk imaging when persistence matters — volatile collection complements, not replaces, a forensic image. And do not reboot before collecting.

Prerequisites

  • Trusted, statically linked collection tools run from external media (not host binaries).
  • Authorization to collect, and a destination on external/write-once media.

Safety & Handling

  • Assume host tools are compromised; use your own trusted binaries to avoid rootkit deception.
  • Hash every artifact at collection time and record actions for chain of custody; minimize changes to the host.

Workflow

Step 1: Follow the order of volatility

Collect most-volatile first (RFC 3227): CPU/registers and cache → RAM → network state and connections → running processes → logged-on users/sessions → open files/handles → then disk.

Step 2: Capture memory first

Acquire a full RAM image with a trusted acquisition tool before anything that alters memory; it is the richest and most perishable source.

Step 3: Snapshot network and process state

Record active connections, listening ports, ARP/DNS cache, running processes with command lines and parent links, and loaded modules.

bash
python scripts/analyst.py manifest ./collection --case IR-42 --host WS01

Step 4: Record users and handles

Capture logged-on users, sessions, scheduled tasks, and open handles/files.

Step 5: Hash, log, and hand off

Hash each artifact, write a collection manifest with timestamps, and transfer to the analysis environment preserving integrity.

Validation

  • Artifacts are collected in order of volatility, memory first, before any reboot.
  • Every artifact has a recorded hash and collection timestamp in the manifest.
  • Trusted external tools were used; host changes are documented.

Pitfalls

  • Rebooting or shutting down before capturing RAM, destroying the best evidence.
  • Using the host's own (possibly trojaned) tools and trusting their output.
  • No hashing/manifest, undermining evidentiary integrity.

References

  • See references/api-reference.md for the manifest helper.
  • RFC 3227 and NIST SP 800-86 (linked in frontmatter).

Files in this version

Permissions

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

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