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/setting-up-an-isolated-malware-analysis-labAnálise de malware e ransomware

setting-up-an-isolated-malware-analysis-lab

⁨Builds a safe, isolated environment for detonating and analyzing malware⁩

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/setting-up-an-isolated-malware-analysis-lab

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

AssinaturaAssinado, ed25519
2DLePBuIi3…EjAQY8Ag==A CLI confere o SHA-256 e a assinatura antes de gravar qualquer arquivo.
Pacotec3c4e6e3…88eebfb7
c3c4e6e364bb…e42b88eebfb74 arquivos · ⁦4.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/setting-up-an-isolated-malware-analysis-lab@da7600a

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

When to Use

  • You need to run unknown or known-malicious binaries to observe behavior without risk to production systems or the internet.
  • You are standing up a repeatable analysis environment for static and dynamic work.
  • You want a reverting, snapshot-based workflow so each sample starts from a clean state.

Do not use this as guidance for detonating samples on a host OS or a cloud VM with live egress; that risks self-spreading malware escaping. Use a dedicated, network-isolated hypervisor instead.

Prerequisites

  • A host with a type-2 hypervisor (VMware Workstation/Fusion or VirtualBox) or a dedicated type-1 host. At least 16 GB RAM and 200 GB disk for two guests.
  • A victim guest (Windows 10/11) for detonation — e.g. built with FLARE-VM tooling.
  • An analysis services guest (REMnux, Linux) to simulate internet services and capture traffic.
  • Host networking able to provide a host-only / internal network with no NAT or bridged adapter on the victim.

Safety & Handling

  • The victim VM must have no bridged or NAT adapter — host-only/internal only. All "internet" is simulated by the REMnux guest running INetSim.
  • Disable shared folders, drag-and-drop, and clipboard sharing on the victim before detonation; these are escape and contamination paths.
  • Take a clean base snapshot before any sample touches the VM and revert to it after every run.
  • Store samples in password-protected archives (infected) and only extract them inside the victim VM.

Workflow

Step 1: Create and harden the victim VM

Install Windows in a new VM, apply analysis tooling, then strip escape paths:

text
VM settings (victim):
  Network adapter   -> Host-only (vmnet1) or Internal network
  Shared folders    -> Disabled
  Clipboard/DnD     -> Disabled
  USB controller    -> Disabled
  Snapshots         -> enabled

Step 2: Stand up simulated internet on REMnux

On the REMnux guest (same host-only network), give it a static IP and run INetSim so the victim's DNS/HTTP/SMTP requests are answered locally:

bash
# REMnux guest, e.g. 10.0.0.2 on the host-only network
sudo nano /etc/inetsim/inetsim.conf   # set service_bind_address and dns_default_ip
sudo systemctl start inetsim

Point the victim's DNS and default gateway at the REMnux IP so all resolution and traffic flow to the simulator.

Step 3: Start packet capture

Capture from the REMnux side so the victim never sees a sniffer:

bash
sudo tcpdump -i eth0 -w /cases/<sample-sha256>.pcap

Step 4: Snapshot, detonate, observe, revert

text
1. Snapshot victim as "clean-base"
2. Transfer the sample into the victim (read-only ISO or one-way copy)
3. Run procmon / process monitoring, then execute the sample
4. Observe for 3-10 minutes; collect artifacts (pcap, procmon log, dropped files)
5. Revert victim to "clean-base"

Use the helper script to verify a victim VM's adapters are isolated before you detonate.

bash
python scripts/analyst.py --check-config vmx/victim.vmx

Validation

  • From the victim, nslookup example.com resolves to the REMnux IP (proves DNS is simulated, not real).
  • A browser request from the victim returns INetSim's default page, not live content.
  • tcpdump on REMnux shows the victim's traffic; nothing reaches a real upstream gateway.
  • Reverting the snapshot returns the victim to the exact clean state (no dropped files persist).

Pitfalls

  • Leaving a NAT/bridged adapter "just to download a tool" — malware will use it. Install all tooling before isolating, then remove the adapter.
  • Forgetting to disable VMware Tools / guest additions clipboard, which some samples abuse.
  • Detonating before snapshotting, so you cannot cleanly revert.
  • Some samples detect INetSim's generic responses; if behavior stalls, consider FakeNet-NG or tailored service responses.

References

  • See references/api-reference.md for the config-check tool and full source list.
  • INetSim, FLARE-VM, and REMnux documentation (linked in frontmatter).

Arquivos desta versão

Permissões

PermissãoDeclaradaEncontrada na varredura
Lê arquivosNãoNão
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 2026da7600ac3c4e6e3Assinada–

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