setting-up-an-isolated-malware-analysis-lab
Builds a safe, isolated environment for detonating and analyzing malware
v1.0.03 installs+3 in 7 days24 StarsApache-2.0synced 10 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install meltedinhex/setting-up-an-isolated-malware-analysis-labWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Packagec3c4e6e3…88eebfb7
c3c4e6e364bb…e42b88eebfb74 files · 4.2 KBScanMedium2 findings
- Executable script shipped with the skillscripts/analyst.py
- Links to outside domains
Sourcegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/setting-up-an-isolated-malware-analysis-lab@da7600a
On this page
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:
VM settings (victim):
Network adapter -> Host-only (vmnet1) or Internal network
Shared folders -> Disabled
Clipboard/DnD -> Disabled
USB controller -> Disabled
Snapshots -> enabledStep 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:
# 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 inetsimPoint 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:
sudo tcpdump -i eth0 -w /cases/<sample-sha256>.pcapStep 4: Snapshot, detonate, observe, revert
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.
python scripts/analyst.py --check-config vmx/victim.vmxValidation
- From the victim,
nslookup example.comresolves to the REMnux IP (proves DNS is simulated, not real). - A browser request from the victim returns INetSim's default page, not live content.
tcpdumpon 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.mdfor the config-check tool and full source list. - INetSim, FLARE-VM, and REMnux documentation (linked in frontmatter).
Files in this version
references/11.5 KB
- api-reference.md1.5 KB
scripts/12.9 KB
- analyst.py2.9 KB
- LICENSE340 B
- SKILL.md4.8 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | Yes | Yes |
| Uses the network | Yes | Yes |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
- MediumFile · Executable script shipped with the skillscripts/analyst.py
- InfoLink · Links to outside domains
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v1.0.0 | Nov 13, 2026 | da7600a | c3c4e6e3 | Signed | – |
More from meltedinhex
All from this publisher- writing-yara-rules-from-reversed-codemeltedinhex/writing-yara-rules-from-reversed-code4
- validating-detections-with-atomic-testsmeltedinhex/validating-detections-with-atomic-tests4
- writing-suricata-and-snort-rulesmeltedinhex/writing-suricata-and-snort-rules3
- writing-sigma-detection-rulesmeltedinhex/writing-sigma-detection-rules3
More in Malware and ransomware analysis
See the category- yara-sigsdariushoule/yara-sigs4
- monitoring-darkweb-sourcesmukul975/monitoring-darkweb-sources3
- deploying-ransomware-canary-filesmukul975/deploying-ransomware-canary-files3
- implementing-honeypot-for-ransomware-detectionmukul975/implementing-honeypot-for-ransomware-detection3
- yaraaeondave/yara3
- testing-ransomware-recovery-proceduresmukul975/testing-ransomware-recovery-procedures3
Ask anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login