Pular para o conteúdo
Novo

DeepSeek V4.1 Flash grátis por 7 dias: 10M tokens por dia após recarga de $10 ou mais. Até 30/11.

Como funciona
meltedinhex/collecting-volatile-evidence-from-a-suspect-hostRelatórios e compliance

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

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

v1.0.03 instalações+3 em 7 dias24 EstrelasApache-2.0sincronizado há 10 horas

Instalar

Ainda não tem a CLI da NotHoly? Instale primeiro.

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

Grava em ⁦~/.notholy/skills⁩ depois de conferir a assinatura e o SHA-256.

AssinaturaAssinado, ed25519
3TASNgMVie…i5tBhdDw==A CLI confere o SHA-256 e a assinatura antes de gravar qualquer arquivo.
Pacotebc51d343…6c4d9e8e
bc51d343ead5…c8c76c4d9e8e4 arquivos · ⁦3.2 KB⁩
VarreduraMédio2 achados
  • Script executável junto com a skillscripts/analyst.py
  • Links para domínios externos
Ver a varredura completa
Fontegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/collecting-volatile-evidence-from-a-suspect-host@da7600a

Este item ainda não foi escrito no seu idioma, então aparece em English.

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).

Arquivos desta versão

Permissões

PermissãoDeclaradaEncontrada na varredura
Lê arquivosSimSim
Grava arquivosNãoNão
Roda comandos no shellSimSim
Usa a redeSimSim
Usa conectoresNãoNão
Controla um navegadorNãoNão

Achados da varredura

Revisado em 13 de nov. de 2026

  1. MédiaArquivo · Script executável junto com a skillscripts/analyst.py
  2. InfoLink · Links para domínios externos

Uma varredura limpa reduz o risco, mas não prova que o pacote é seguro. Leia o que você instala.

VersãoPublicada emCommitSHA-256AssinaturaMudança de permissão
v1.0.013 de nov. de 2026da7600abc51d343Assinada–

Pergunte tudo o que o seu escopo permite.

Crie a conta, adicione créditos e faça a primeira pergunta no chat ou no terminal.

  1. 1/3

    Crie a conta

    Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.

    Pessoa físicaEmpresa
  2. 2/3

    Adicione créditos

    No cartão. Você paga por token, sem assinatura.

    $5.00recarga mínima
  3. 3/3

    Pergunte

    No chat, ou instale o CLI e rode notholy login no terminal.

    $ notholy login