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/analyzing-malware-in-memory-with-volatility3Análise de malware e ransomware

analyzing-malware-in-memory-with-volatility3

⁨Analyzes a memory image with Volatility 3 to find malware: rogue processes,⁩

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/analyzing-malware-in-memory-with-volatility3

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

AssinaturaAssinado, ed25519
ijy9Ilt+lH…tvpLjcCQ==A CLI confere o SHA-256 e a assinatura antes de gravar qualquer arquivo.
Pacote12fd2a56…f83f2ddd
12fd2a56d3a8…c877f83f2ddd4 arquivos · ⁦3.3 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/analyzing-malware-in-memory-with-volatility3@da7600a

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

When to Use

  • You have a RAM image from a suspected-infected host and need to find malicious activity.
  • Disk artifacts are insufficient (fileless/in-memory malware) and you need volatile evidence.
  • You want to extract injected code, command lines, or network connections for analysis.

Do not use Volatility plugins blindly without an order of investigation — start broad (processes, network) before deep per-process dumps.

Prerequisites

  • Volatility 3 (pip install volatility3) with appropriate symbol tables.
  • A memory image acquired with a sound tool (WinPmem, LiME, or hypervisor snapshot).
  • Knowledge of the source OS/version to select the right symbols.

Safety & Handling

  • Work on a copy of the image; preserve the original with a recorded hash.
  • Treat any dumped executable region as a live sample — store and handle it accordingly.

Workflow

Step 1: Enumerate processes and spot anomalies

bash
vol -f memory.raw windows.pslist
vol -f memory.raw windows.pstree

Look for unusual parents (Word spawning cmd/powershell), masquerading names (scvhost.exe), processes with no disk path, and orphaned children.

Step 2: Hunt injected code

bash
vol -f memory.raw windows.malfind

malfind flags private, executable, RWX regions with no backing file — classic injection. Note the PID and base address for dumping.

Step 3: Review network connections

bash
vol -f memory.raw windows.netscan

Correlate listening/established connections with suspicious PIDs and the C2 endpoints from other analysis.

Step 4: Check modules, handles, and persistence

Examine loaded DLLs (windows.dlllist), services, and registry (windows.registry.*) for persistence and unexpected modules.

Step 5: Dump artifacts

Dump the suspicious process or injected region for static/RE analysis:

bash
vol -f memory.raw windows.dumpfiles --pid <pid>

The helper script parses Volatility's JSON renderer output to highlight injection candidates.

bash
vol -f memory.raw -r json windows.malfind | python scripts/analyst.py malfind -

Validation

  • Injection candidates from malfind correspond to anomalous processes from pstree.
  • Network connections map to known C2 or the sample's extracted config.
  • Dumped regions disassemble into meaningful code, not random bytes.

Pitfalls

  • Wrong symbols/profile producing empty or garbage results — confirm OS build first.
  • Treating every RWX region as malicious; some legitimate JIT engines use RWX. Corroborate.
  • Forgetting to hash and preserve the original image before analysis.

References

  • See references/api-reference.md for the malfind output parser.
  • Volatility 3 documentation and memory-forensics concepts (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 2026da7600a12fd2a56Assinada–

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