Core-remnux-focal
REMnux is a Linux-based toolkit for reverse-engineering and analysing malicious software, delivered here as a preconfigured Kasm Web workspace you access…
Platform availability
Available on 0 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
27/100 Low
- Maintained
- 43last commit 296 days ago
- Popular
- 00 GitHub stars
- Easy to install
- 250 install platforms, install notes, Docker image
- Light to run
- 304 GB minimum RAM
- GitHub stars
- 0
- Open issues
- 0
- Last commit
- 2026-01-29
- Activity
- stale
Checked 16 days ago - source: GitHub (thw01f/REMnux)
Resources & Compatibility
Minimum requirements: 4 GB RAM, 2 CPU core(s), 30 GB disk. ARM (e.g. Raspberry Pi) is not supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Set PORT, HOST, and LOG_LEVEL before start Use environment variables (plain settings the container reads) to set PORT, HOST, and LOG_LEVEL before starting. Without them, it may fall back to defaults like port 8080 and listening on all network interfaces, which can conflict with another app or expose the service. source
- Expose HTTP only on port 8080 if you need it The HTTP example binds to 0.0.0.0:8080, meaning it listens on all network interfaces at port 8080. Port-forward 8080 only if you want to open the web UI from another device; otherwise keep it closed to reduce risk. source
- Keep gRPC port 50051 closed unless needed The gRPC example uses 0.0.0.0:50051 for an app-to-app service connection, not a normal browser site. Only expose 50051 if a client you trust explicitly needs to talk to that gRPC service; otherwise keep it closed. source
Fetched 42 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
How should I request help if I run into a REMnux problem?
Open an issue in the Issues area of the REMnux repository on GitHub. Choose the issue area that best matches your request.
Which guest tools does REMnux install automatically for common hypervisors?
Running remnux install detects the hypervisor and installs the matching tools. It installs open-vm-tools on VMware and qemu-guest-agent plus spice-vdagent on KVM, QEMU, or Proxmox. For VirtualBox, install Guest Additions from the ISO.
Is the initial sandbox setup okay if I later delete and reinstall testbeds?
The Malware subreddit discussion says the initial sandbox setup is fine even if you later delete and reinstall testbeds.
Answers sourced from docs.remnux.org, docs.remnux.org, www.reddit.com
Community
- REMnux : r/Malware - Reddit (reddit)
Collected 48 days ago - public community threads