November 19, 2026
Building an Isolated Malware Analysis Home Lab with FLARE-VM and REMnux on VirtualBox
Introduction
By Miruma
7 min read
Introduction
As part of my cybersecurity learning journey, I decided to take a practical step towards understanding malware analysis by building my own home lab.
My goal was to create a controlled environment where I could investigate suspicious files, understand malware behaviour, perform static and dynamic analysis, and explore reverse engineering without putting my personal computer at risk.
For this project, I used two specialised environments: FLARE-VM and REMnux, running as separate virtual machines on Oracle VirtualBox.
FLARE-VM provides a Windows-based environment for malware analysis, while REMnux provides a Linux-based environment with tools for investigating malicious files, network traffic and suspicious communications.
The process came with a few challenges, particularly around hardware limitations, installation, snapshots and network configuration. However, each challenge provided an opportunity to learn something new.
Here is how I built my lab.
1. Understanding the Lab Environment
Before starting, I wanted to understand the purpose of each environment.
FLARE-VM (Windows 10)
FLARE-VM is a Windows-based malware analysis distribution developed by Mandiant. It provides tools for reverse engineering, debugging and investigating suspicious Windows applications.
Some of the tools I intended to use included:
- PEStudio: Inspecting Portable Executable (PE) files.
- FLOSS: Extracting readable strings from malware.
- Procmon: Monitoring process, file and registry activity.
- FakeNet-NG: Simulating network services.
- x64dbg: Debugging Windows executables.
- JADX-GUI: Analysing Android applications.
REMnux (Linux)
REMnux is a Linux-based toolkit designed for malware analysis and reverse engineering.
It provides tools for:
- Analysing suspicious files and documents.
- Investigating network traffic.
- Examining malicious scripts.
- Analysing URLs and network indicators.
- Extracting information from suspicious files.
I also planned to use INetSim, a tool that simulates internet services, allowing me to observe how suspicious programs attempt to communicate with external systems.
Together, these environments provide different capabilities for investigating malware.
2. My Host Machine Specifications
My host computer runs Windows 11, with the following specifications:
ComponentSpecificationOperating SystemWindows 11RAM8 GB (7.41 GB usable)ProcessorIntel Core i5โ6300U @ 2.40 GHzVirtualisationOracle VirtualBoxStorageD: Drive
Because I had only 8 GB of RAM, resource allocation required careful consideration.
I initially attempted to allocate approximately 6 GB of RAM to my Windows VM, but VirtualBox displayed memory warnings and the machine failed to start.
After checking Task Manager, I realised my host system was already using a significant portion of the available memory.
I eventually settled on a more practical configuration.
3. Installing Windows 10 and Preparing FLARE-VM
Although my host computer runs Windows 11, I chose Windows 10 Pro 22H2 (64-bit) for the FLARE-VM environment.
I downloaded the Windows 10 ISO using Microsoft's Media Creation Tool and created a new virtual machine in VirtualBox.
My configuration was:
ComponentConfigurationOperating SystemWindows 10 ProRAM4096 MBCPUs2Disk TypeVDIDisk Size100 GBStorage LocationD: Drive
During installation, I created a local Windows account instead of linking my personal Microsoft account.
After reaching the desktop, I installed VirtualBox Guest Additions to improve mouse integration, display resolution and overall usability.
Installing FLARE-VM
Before installing FLARE-VM, I reviewed its pre-installation checks.
One warning caught my attention:
Windows Defender Disabled = False
I temporarily adjusted the relevant Microsoft Defender settings inside the dedicated analysis VM to prevent interference with the installation.
I then opened PowerShell as Administrator and ran the installation commands:
Unblock-File .\install.ps1
Set-ExecutionPolicy Unrestricted -Force
.\install.ps1Unblock-File .\install.ps1
Set-ExecutionPolicy Unrestricted -Force
.\install.ps1The installer launched and performed its environment validation checks.
Rather than installing every available package, I decided to focus on tools that would be useful for my initial malware analysis exercises.
Some of the tools I wanted to explore included PEStudio, FLOSS, Procmon, FakeNet-NG and HashMyFiles.
Package availability and installation names can vary between releases, so I referred to the official FLARE-VM documentation when checking the available packages.
Creating a Clean Snapshot
One lesson I learned during this process was the importance of snapshots.
I had initially started the FLARE-VM installation before creating a snapshot. Fortunately, I stopped before the packages were installed.
I shut down the VM and created a snapshot named:
Clean Windows 10 Before FLARE-VM
This gave me a recovery point in case anything went wrong during installation or configuration.
4. Installing REMnux
For the Linux environment, I used the prebuilt REMnux virtual appliance instead of installing the operating system and tools individually.
I downloaded the appliance from the official REMnux website.
In VirtualBox, I selected:
File โ Import Appliance
I located the downloaded OVA file and completed the import.
After importing, I reviewed the VM settings and disabled shared clipboard, drag-and-drop and unnecessary shared folders to reduce interaction between the virtual machine and my host computer.
Once REMnux started, I logged in and changed the default password:
passwdpasswdThis completed the initial REMnux setup.
5. Configuring INetSim on REMnux
One important part of my setup was configuring REMnux to simulate internet services using INetSim.
INetSim can simulate services such as DNS, HTTP, SMTP and FTP. This allows an analyst to observe how suspicious software attempts to communicate with external services without relying on the real internet.
I opened the configuration file:
sudo nano /etc/inetsim/inetsim.confsudo nano /etc/inetsim/inetsim.confI located the relevant settings and configured the following:
start_service dns
service_bind_address 0.0.0.0
dns_default_ip 192.168.77.4start_service dns
service_bind_address 0.0.0.0
dns_default_ip 192.168.77.4The settings serve different purposes:
start_service dnsenables the DNS simulation service.service_bind_address 0.0.0.0allows INetSim to listen on its network interfaces.dns_default_ip 192.168.77.4directs simulated DNS responses to the REMnux address.
I intended to assign REMnux the static IP address 192.168.77.4.
After saving the configuration, I started INetSim:
sudo inetsimsudo inetsimI left the terminal running so I could monitor the simulated services and their logs.
6. Connecting FLARE-VM and REMnux
With both environments prepared, I needed to connect them without providing a direct route to my host computer or the public internet.
VirtualBox offers different networking options, including NAT, Host-only and Internal Network.
I selected Internal Network because it allows virtual machines on the same internal network to communicate without directly connecting that network to the host or external internet.
Configuring VirtualBox Networking
I powered off both virtual machines and opened their network settings.
For Adapter 1, I selected:
- Attached to: Internal Network
- Network Name:
malnet
I used the same network name for both machines and disabled the remaining network adapters.
I also confirmed that shared folders, shared clipboard and drag-and-drop were disabled.
Assigning an IP Address to REMnux
I started REMnux and checked its network connections:
nmcli con shownmcli con showAfter identifying the wired connection, I assigned its static IP:
sudo nmcli con mod "Wired connection 1" ipv4.method manual ipv4.addresses 192.168.77.4/24sudo nmcli con mod "Wired connection 1" ipv4.method manual ipv4.addresses 192.168.77.4/24I activated the connection:
sudo nmcli con up "Wired connection 1"sudo nmcli con up "Wired connection 1"Then I verified the address:
ip aip aThe expected address was:
192.168.77.4/24
Configuring FLARE-VM
On FLARE-VM, I pressed Win + R, entered ncpa.cpl and opened the Ethernet adapter properties.
Under Internet Protocol Version 4 (TCP/IPv4), I configured:
SettingValueIP Address192.168.77.3Subnet Mask255.255.255.0Default GatewayLeave blankPreferred DNS192.168.77.4
I left the default gateway blank to prevent this network configuration from providing an external route.
Finally, I ran ipconfig in PowerShell to confirm the settings.
7. Testing the Lab
After configuring both machines, I needed to verify that they could communicate and that the intended network isolation was in place.
With INetSim running on REMnux, I opened PowerShell in FLARE-VM.
Test 1: Communication between virtual machines
ping 192.168.77.4ping 192.168.77.4A successful response confirmed that FLARE-VM could communicate with REMnux.
Test 2: Public internet connectivity
ping 8.8.8.8ping 8.8.8.8The expected result was no response. However, a failed ping alone does not prove isolation, so I also checked the VirtualBox adapters and network routes to ensure no external connection was available.
Test 3: DNS simulation
nslookup google.com 192.168.77.4nslookup google.com 192.168.77.4The expected response was the REMnux address rather than Google's actual public IP.
Test 4: HTTP simulation
I opened a browser inside FLARE-VM and visited:
Instead of reaching the real website, the browser displayed INetSim's default simulated page.
This helped confirm that DNS requests were being directed to REMnux and that INetSim was responding to HTTP requests.
8. Challenges and Lessons Learned
Building this lab taught me several practical lessons beyond simply installing the tools.
- Hardware limitations: Working with 8 GB of RAM meant I had to be deliberate about resource allocation and avoid running both VMs simultaneously when the host struggled.
- Installation issues: Some tools triggered Windows Defender warnings, reminding me to understand the tools and keep security changes restricted to the dedicated analysis environment.
- Package verification: I encountered difficulties checking installed Chocolatey packages using
Select-String. Usingfindstrprovided a simpler alternative in my environment. - INetSim configuration: I learned the importance of checking service configurations and identifying port conflicts before making changes.
- Network isolation: Both machines needed the correct static IP addresses and the same Internal Network configuration.
- Snapshots: Creating recovery points before major changes made troubleshooting less stressful.
My biggest takeaway was that every configuration should be tested before moving to the next stage.
9. Safety Considerations
A malware analysis lab must be configured carefully.
Some precautions I intend to maintain include:
- Keep the virtual machines on the dedicated Internal Network during malware execution.
- Disable NAT, Bridged and Host-only adapters when working with suspicious samples.
- Disable shared folders, clipboard and drag-and-drop.
- Avoid using personal accounts within the analysis environment.
- Create snapshots before significant changes.
- Never execute suspicious files on the host computer.
- Restore the virtual machines to a clean state after an investigation.
Virtualisation reduces risk, but it does not make malware harmless. Some malware can detect virtual environments or behave differently during analysis.
Conclusion
Building this malware analysis home lab has been an interesting part of my cybersecurity learning journey.
From installing Windows 10 and FLARE-VM to importing REMnux, configuring INetSim and connecting both environments through an isolated network, each stage helped me understand the practical considerations involved in malware analysis.
I also learned that building a lab is not just about installing tools. It is about understanding how they work together, configuring them correctly and creating a controlled environment for investigation.
I am looking forward to using this lab to explore static analysis, dynamic analysis, reverse engineering and network traffic investigation.
This is one more step towards becoming more confident in practical cybersecurity.
References
- Mandiant. (n.d.). FLARE-VM: A Windows-based platform for malware analysis. GitHub. https://github.com/mandiant/flare-vm
- REMnux. (n.d.). REMnux documentation. https://docs.remnux.org/
- REMnux. (n.d.). Getting the REMnux virtual appliance. https://docs.remnux.org/install-distro/get-virtual-appliance
- INetSim. (n.d.). Internet Services Simulation Suite. https://www.inetsim.org/
- Oracle. (n.d.). Oracle VM VirtualBox User Manual. https://www.virtualbox.org/manual/
- Oracle. (n.d.). VirtualBox networking details. https://docs.oracle.com/en/virtualization/virtualbox/7.2/user/networkingdetails.html