An isolated Proxmox environment for static analysis, dynamic analysis, reverse engineering, and monitoring potentially malicious behavior.
โ ๏ธ Disclaimer
Malware is dangerous and is not a toy. Always ensure your environment is fully secured to prevent accidental escape.
This lab project is provided strictly for educational and research purposes within authorized environments (e.g., home labs, classrooms, or licensed training environments).
You must not use any included tools, scripts, or methodologies on any system or network for which you do not have explicit written permission. Unauthorized use is illegal and may be punishable by law. The authors assume no liability for misuse or damage resulting from the use of this material.
๐ License
This project is licensed under the Creative Commons Attribution-NonCommercial 4.0 International (CC BY-NC 4.0) license.
๐ Full License Text
๐งโ๐ป Author
Rogue Labs (Dylan Barrett)
๐ Visit Portfolio
๐ฅ What's Included
| Component | Description |
|---|---|
| Inet | A controlled "Internet" simulation used to monitor C2 and external behavior |
| pfSense | Firewall/router for monitoring outbound traffic and controlling internet access |
| Windows Flare VMs | Windows VMs configured for static and dynamic malware analysis |
| REMnux | Linux distribution for static analysis of malware artifacts (packers, scripts, etc.) |
| Security Onion | SOC tooling (IDS/ELK/etc.) for network and host monitoring |
| Ubuntu (CapeV2) | Ubuntu VM running Cape (Cape-v2) for automated dynamic analysis |
๐ฅ๏ธ Lab Architecture (Planned)
graph TD;
Proxmox --> Inet
Inet --> PFsense
PFsense --> Windows_11_Flare_VM
PFsense --> Remnux
PFsense --> Security_Onion
PFsense --> Windows_10_Flare_VM
PFsense --> Ubuntu
Ubuntu --> CapeV2
Note: The "Inet" node represents a controlled/simulated internet environment (for safe C2 testing). The real LAN/Internet should be administratively isolated from the lab by default.
๐ Directory
| ๐ Section | ๐ Description |
|---|---|
| ๐ Proxmox Malware Lab Setup | Deploy, configure, and initialize the lab in Proxmox VE. |
| ๐งช Analysis Library โ Planned | Analysis notes and write-ups for public malware samples. |
Safety & Operational Notes (Short)
- Keep lab bridges isolated (no host IP assigned) unless connectivity is required.
- Use pfSense to strictly control and log outbound traffic.
- Prefer a simulated "internet" VM for C2 testing instead of exposing the real internet.
- Snapshot VMs before any detonation or intrusive testing.
- Limit admin access to the Proxmox console and lab VMs.