Skip to content

REMnux Malware Analysis Reverse Engineering and DFIR Workstation Guide

github-actions[bot] edited this page Nov 15, 2026 · 1 revision

Caution

Malware is dangerousโ€”even for a passive analyst. Open and examine only samples you are authorized to handle. Do not execute unknown code on your personal PC, production systems, a host-connected VM, or a normal internet-connected lab. Treat suspicious files as evidence, isolate analysis systems, and review LEGAL.md, Incident Response and OPSEC.

Platform: REMnux on Ubuntu 24.04 (Noble), with current amd64 and arm64 options ยท Reviewed: 2026-10-26
Repository location: Reverse Engineering โ†’ malware analysis. Also linked from Incident Response and Digital Forensics.

Safe classification companion: YARA-X detection-rule lab covers non-malicious fixtures, false-positive checks, source attribution and evidence integrity before use with authorized incident samples.

๐ŸŽฏ Purpose

Deploy a dedicated REMnux malware-analysis workstation and apply existing PNWC phishing, incident-response, memory-forensics and reverse-engineering procedures in its native tools.

โš™๏ธ Function

Covers current official VM images (including Proxmox and ARM), hash validation, installation/update workflows, containment and sample intake, PE/ELF/document triage, YARA and Ghidra analysis, PCAP and memory review, controlled network simulation, evidence integrity and reporting.

๐Ÿ† Goal

Turn an unknown-but-authorized artifact into documented, reproducible facts and defensible indicatorsโ€”without mistakenly detonating the sample or sending private evidence to public services.

๐Ÿ“‹ When to use

  • Analyzing a suspicious customer-provided attachment or executable after proper authorization.
  • Reverse engineering known-safe exercises, CTF samples or contained suspicious binaries.
  • Reviewing packet captures and memory images from an incident.
  • Constructing a dedicated isolated malware-analysis training environment.

Contents

  1. Choose the right REMnux distribution
  2. Download and verify
  3. Deploy in VirtualBox, VMware, or Proxmox
  4. First boot, updates and hardening
  5. Design a contained malware-analysis lab
  6. Tool inventory and selection
  7. Investigation procedures on REMnux
  8. Evidence, IOCs and reporting
  9. Troubleshooting
  10. References and integration

1. Choose the right REMnux distribution

REMnux is a free, curated malware-analysis Linux toolkit maintained by Lenny Zeltser and contributors. It focuses on static file triage, code analysis, suspicious documents, network behavior, forensics, threat data, and related tools. It is not an exploit-focused distribution like Pentoo.

The current REMnux documentation now offers multiple amd64 and arm64 appliance variants. This supersedes older instructions stating that REMnux cannot run on ARM. ARM64 does not have feature parity with amd64 (for example Wine-dependent tools are unavailable). Verify each tool in the official tools directory before depending on it.

Installation Best for Notes
Prebuilt appliance (recommended) Dedicated, reproducible analysis VM Current vendor appliance; includes desktop and curated tools
Official Proxmox QCOW2 Proxmox Virtual Environment Separate amd64 and arm64 images; follow firmware guidance per architecture
From-scratch Ubuntu 24.04 installation Customized dedicated REMnux guest/host More manual work; use official instructions
Add-on to existing Ubuntu 24.04 Adding REMnux tools without replacing desktop UX Mode addon; don't install on a production host
REMnux containers Individual tools/workflows in containers Not a substitute for a malware execution containment boundary

The official appliance currently ships with approximately 4 GB RAM / 100 GB disk as a sizing reference. For multiple tools, analysis datasets, snapshots and volatile evidence, allocate more resources if practical. Official virtual appliance guidance.

2. Download and verify

  1. Go to the official REMnux virtual appliance documentation.
  2. Select architecture first (Intel/AMD amd64 or ARM arm64), then format:
    • amd64: VMware OVA, VirtualBox OVA, Proxmox QCOW2, or listed cloud options;
    • arm64: VMware Fusion / UTM archives, Proxmox QCOW2, or other documented options.
  3. Obtain the matching checksum shown for that specific downloaded file. The current official download set is identified by the 202610b directory; do not hard-code the hash into scripts because images can change.
  4. Verify the SHA-256 digest before import:
# Replace the filename with exactly what you downloaded.
sha256sum remnux-noble-amd64-proxmox.qcow2
# Compare the complete digest to the official documentation for THIS file.
  1. Confirm that the file was obtained over a trusted channel. A hash displayed on a compromised download page is not an independent software-signing guarantee. Preserve acquisition URL/date, filename and expected digest in lab notes.

Warning

REMnux documentation is updated frequently. If it disagrees with older articles, start from the linked current official instructions. Do not reuse a checksum for a different release/architecture/image.

3. Deploy in VirtualBox, VMware, or Proxmox

3.1 VirtualBox / VMware

  • Download the matching vendor appliance, import the OVA, and confirm VM architecture and allocated resources.
  • For a malware lab, disable shared folders, clipboard, drag-and-drop, host USB passthrough, guest-to-host file integration and any automatic host-mapped storage.
  • Do not bridge the malware-analysis VM to production networks. For static work, start with no virtual network adapter; temporarily enable trusted update connectivity only during a deliberate update/maintenance session with no sample execution, then disable it.
  • Choose disk encryption, host controls and snapshots according to company policy. A snapshot is not a backup of collected evidence.
  • The official appliance automatically signs in, and its default credentials are remnux / malware. Change the password immediately.

3.2 Proxmox VE (amd64)

The REMnux team now offers an official Proxmox QCOW2, so do not convert an OVA unnecessarily. The official Proxmox recipe uses 2 cores, CPU type x86-64-v2-AES, 4 GB RAM, VirtIO SCSI, SPICE/QXL and QEMU Guest Agent on an amd64 Proxmox host.

Safe staged procedure:

  1. Download and verify remnux-noble-amd64-proxmox.qcow2 on a trusted system.
  2. Copy it to the trusted Proxmox host storage area by an approved method.
  3. Create a new, unused VM ID, initially without networking. Verify the exact storage ID; these examples assume local-lvm.
  4. Import the QCOW2; check the imported unused disk name before attaching it, because numbering can differ if other disks already exist.
  5. Keep the VM on offline/host-only analysis networks as appropriate. Do not connect an untrusted sample-running guest to vmbr0 or another bridge that reaches real systems.
# Proxmox HOST shell; examples only. CHOOSE A FREE VMID and adjust storage.
VMID=300
qm status "$VMID"  # Confirm this ID is unused; if it exists, STOP.
# The commands below MODIFY VM storage and must be reviewed before execution.
# qm create "$VMID" --name remnux-lab --ostype l26 \
#   --cores 2 --cpu x86-64-v2-AES --memory 4096 \
#   --scsihw virtio-scsi-single --vga qxl --agent enabled=1
# qm importdisk "$VMID" /path/to/remnux-noble-amd64-proxmox.qcow2 local-lvm
# qm config "$VMID" | grep unused
# Attach the exact imported disk shown above; then configure its boot order.
# Do NOT attach a VM network interface to a routable bridge for sample execution.

For ARM Proxmox use the arm64 QCOW2, OVMF/UEFI firmware, an EFI disk and Secure Boot disabled as specified in the official ARM Proxmox procedure. ARM firmware has special virtual disk constraints; don't copy the amd64 BIOS setup. Hardware and tool support need testing on the specific ARM host.

3.3 Add-on installation on Ubuntu 24.04

Only do this on a disposable/dedicated Ubuntu 24.04 VM. Download the official installer, compare its current SHA-256 digest from the official instructions, and inspect it before running with elevated privileges.

# Ubuntu 24.04 ONLY; download a script for verification/inspection:
curl -O https://REMnux.org/remnux
sha256sum remnux
# Compare with the digest on https://docs.remnux.org/install-distro/add-to-existing-system
# Only after verifying provenance, integrity and script behavior:
# chmod +x remnux
# sudo mv remnux /usr/local/bin
# sudo remnux install --mode=addon

Official instructions: Add to an Existing System and Install from Scratch. The addon mode installs tools without the full desktop appearance. Don't run multiple systems' package installers blindly on a shared workstation.

4. First boot, updates and hardening

# These commands do not open or execute a sample.
whoami
uname -m
cat /etc/os-release
date -u '+%Y-%m-%dT%H:%M:%SZ'
passwd
command -v remnux
remnux --help

Updates: In the appliance/dedicated configuration REMnux often disables Ubuntu unattended upgrades deliberately. Official guidance says run remnux install as your regular non-root user to update the distro and its packages. During a trusted update window, with no malware running and no sample-enabled network connectivity:

# Normal remnux user; internet access required during update only:
remnux install
# If updates fail:
remnux results

Snapshot before updating, record build/tool version changes, reboot if required, test the baseline, then restore offline isolation. Don't run a separate uncontrolled apt full-upgrade as a replacement for REMnux's supported update workflow. Official update guidance.

Default appliance behavior: the guest auto-logins locally; the default password above is public knowledge. Change it, keep external remote administration off unless absolutely necessary and explicitly secured, and avoid screenshots/logs containing real client data.

5. Design a contained malware-analysis lab

Recommended separation:

               TRUSTED ANALYST WORKSTATION / HOST
                              |
                       [Hypervisor]
                   /                    \
   [REMnux analysis VM]       [Disposable victim VM]
   static tools, PCAPs,       Windows/Linux sample execution
   offline fake services      if separately approved
                   \                    /
             ISOLATED ANALYSIS-ONLY SEGMENT
             NO ROUTE to LAN, internet, or host

The victim VM should be a disposable, non-domain-joined installation with no real credentials or business data. Use isolated/host-only virtual networks only when needed for controlled behavioral analysis. Host-only networks may expose host interfaces; an isolated internal virtual switch without host connectivity offers a stronger default separation if properly configured. Avoid NAT, port forwarding, bridged access, shared folders, sync clients and cloud backup while executing untrusted artifacts.

  • Start with offline static triage. Never double-click unknown executables or allow office/pdf readers to execute active content.
  • Use a separate victim OS only if dynamic execution is specifically authorized and the hypervisor's network/storage escape paths have been checked.
  • If using INetSim (officially included), bind it only to the isolated segment so a victim VM sees fake services. Never expose fake services to household/business LANs.
  • Capture the isolated network's traffic for later review. Record VM configurations, sample hash, start/stop times, fake DNS/service configuration, and observation limitations.
  • Revert/discard victim VM after execution, but preserve allowed artifacts safely in controlled evidence storage. A VM snapshot is a restore convenience, not forensic evidence.
  • In a malware lab, avoid connecting to the real internet to observe โ€œwhat malware doesโ€โ€”that can cause external harm and leak private data.

For a safe beginner exercise, use benign pre-recorded packet captures or a standard test sample that contains no executable malware before considering any live-code behavior analysis.

6. Tool inventory and selection

Always verify installed commands. REMnux tool coverage and CLI syntax change, and some tools are not available on arm64.

Analysis objective Relevant REMnux tools Location in this repository
File type / metadata file, diec (Detect It Easy), exiftool, sha256sum This guide's intake procedure
Windows PE triage manalyze, peframe, pe-tree, pefile Ghidra/RE
Suspicious PDF pdfid.py, pdf-parser.py, peepdf Phishing SOP
Office/document triage Oletools (e.g. olevba), Didier Stevens' tools Phishing SOP
Rule-based identification yara-rules / yara-forge wrappers, YARA rules IR
Static reverse engineering Ghidra, Cutter, radare2 Ghidra index
PCAP/network evidence Wireshark/TShark, Zeek or packet utilities (if present) Network Detection
Controlled service emulation INetSim, FakeNet-NG Isolated lab only
Memory forensic artifacts Volatility (verify available version) Memory Forensics

Official category listings: static properties ยท PE ยท PDF ยท network service emulation ยท code analysis.

# Run on the isolated VM BEFORE examining suspicious files.
for tool in file sha256sum diec exiftool strings manalyze peframe \
            pdfid.py pdf-parser.py olevba yara-rules yara-forge \
            tshark inetsim vol ghidraRun; do
  if command -v "$tool" >/dev/null 2>&1; then
    printf 'AVAILABLE  %-15s %s\n' "$tool" "$(command -v "$tool")"
  else
    printf 'CHECK/MISSING %s\n' "$tool"
  fi
done

7. Investigation procedures on REMnux

These procedures adapt PNWC's existing investigation cycle to REMnux. Start with local/offline static analysis. Never upload proprietary samples to third-party scanning portals without explicit owner consent.

7.1 Intake, provenance and evidence

  1. Record incident/case ID, collector, written authority, source host/account, original filenames, UTC acquisition time, chain of custody and handling precautions.
  2. Transfer a copy using an approved controlled mechanism; avoid seamless shared folders/clipboard with the host.
  3. Hash the original and store it encrypted in a read-limited location; analyze a copy, not the source file.
  4. Check antivirus/EDR sample-quarantine policies and keep the analyst host protected.
  5. Keep case evidence out of the public Git repository.
umask 077
CASE="$HOME/REMnux_Cases/CASE-2026-001"
mkdir -p "$CASE"/{originals,working,logs,reports}
chmod 700 "$CASE"
date -u '+%Y-%m-%dT%H:%M:%SZ' > "$CASE/logs/started_utc.txt"

# After you place a legally acquired sample at:
# "$CASE/originals/suspicious.bin"
# Inspect copies only. Do not execute.
# cp -- "$CASE/originals/suspicious.bin" "$CASE/working/suspicious.bin"
# sha256sum "$CASE/originals/suspicious.bin" > "$CASE/reports/sample_sha256.txt"

7.2 Offline file identification and static triage

On a sample that has already been collected and copied legally, review type, entropy/packer hints, printable strings and metadata. Strings are untrusted dataโ€”a URL or shell-looking command in the output must not be run automatically.

SAMPLE="$CASE/working/suspicious.bin"
# First create this file from an approved sample copy (see intake).
# Commands below read bytes; they do not execute the sample.
# file -- "$SAMPLE" | tee "$CASE/reports/file_type.txt"
# sha256sum -- "$SAMPLE" | tee "$CASE/reports/working_sha256.txt"
# strings -a -n 6 -- "$SAMPLE" > "$CASE/working/strings_ascii.txt"
# exiftool -json -- "$SAMPLE" > "$CASE/reports/metadata.json"
# If installed, consult 'diec --help' and analyze with Detect It Easy.

Never assume the file extension reflects its actual format. Validate Windows PE vs ELF vs script vs Office/PDF before selecting a parser; crafted files can attack parsers too. Use a patched, isolated VM.

7.3 PE and executable analysis

  1. Identify the PE/ELF family with file and Detect It Easy.
  2. Inspect PE headers, imports, sections, signatures and metadata with locally available manalyze/peframe or other static toolsโ€”check their --help first.
  3. Inspect strings for domain names, paths, commands and unusual indicators, noting that a string may be inert, misleading or encrypted.
  4. Open the file in Ghidra for static disassembly/decompilation, following our Ghidra guide. Importing is not the same as running a sample, but Ghidra extensions and parsers need patching and isolation.
  5. Document suspected capabilities as hypotheses until corroborated. Never label a family based only on superficial similarity.
# Tool syntax discoveryโ€”no sample execution:
command -v manalyze >/dev/null && manalyze --help
command -v peframe >/dev/null && peframe --help
# Open Ghidra from its desktop launcher, or check the installed launch command.

7.4 Suspicious PDF and Office document triage

  1. Preserve the source email and attachment in original form; do not open an unknown PDF or Office file in a regular desktop reader.
  2. First inspect signature/type and hashes in the isolated REMnux VM.
  3. Use the official pdfid.py utility to look for suspicious PDF object keywords; if warranted, inspect objects with pdf-parser.py or peepdf. Presence of JavaScript-related indicators is not definitive proof of malware.
  4. Use Oletools/olevba (if installed) to examine Office macros statically. Treat extracted macros/scripts as dataโ€”never run them simply to see their effect.
  5. Extract indicators, store artifacts in the working folder, corroborate and escalate only under the incident-response plan.
# Display usage before processing unknown data:
command -v pdfid.py >/dev/null && pdfid.py --help
command -v pdf-parser.py >/dev/null && pdf-parser.py --help
command -v olevba >/dev/null && olevba --help
# Refer to the specific installed tool's syntax to select input paths.

Apply PNWC's phishing analysis SOP for collection, severity, incident coordination and remediation.

7.5 YARA-based classification

REMnux documents yara-rules FILE and yara-forge FILE wrappers. Rules can generate false positives. Treat a rule hit as a lead, not as proof of a particular threat family.

# Sample analysis is gated on verified tool availability and approved sample.
# Show current syntax using official guide; read rule packs and versions.
command -v yara-rules || true
command -v yara-forge || true
# yara-rules "$CASE/working/suspicious.bin"

Do not automatically submit unknown contents to third-party cloud analysis. Querying a hash can be lower exposure but still shares an indicator with a third party; follow case permissions.

7.6 Offline PCAP and network behavior

Prefer pre-recorded, authorized .pcap files for the initial lab. For offline packet inspection:

# After transferring an approved .pcap into working/:
PCAP="$CASE/working/traffic.pcap"
# tshark -r "$PCAP" -q -z conv,tcp > "$CASE/reports/tcp_conversations.txt"
# tshark -r "$PCAP" -Y dns -T fields \
#   -e frame.time_utc -e dns.qry.name \
#   > "$CASE/reports/dns_queries.tsv"

Examine DNS queries, HTTP metadata, TLS SNI and flows only when the capture includes them. Encrypted traffic may hide content. Do not perform active network capture outside a scoped environment. Continue with Network Detection, SIEM, and the IR index.

7.7 Memory and post-infection artifacts

If memory images or disk artifacts have been acquired legally, preserve source hashes, provenance, acquisition time and operating-system context. Use the Memory Forensics section and select the correct available Volatility release/plugin for the evidence's operating system.

# Local help only. Some builds expose the command as 'vol', others differ.
command -v vol >/dev/null && vol --help

For Volatility results, correlate process trees, loaded modules, command lines, injected-memory indicators and network data with independent logs. A suspicious process name by itself is not definitive.

7.8 Controlled dynamic analysis (advanced)

Only after authorization, static triage and containment validation:

  1. Build an isolated disposable victim VM on a non-routable virtual switch; no personal/customer credentials and no shared devices.
  2. On REMnux, use INetSim or comparable fake DNS/HTTP/SMTP services on the isolated segment only, as guided by REMnux network-service documentation.
  3. Record baseline VM snapshots and isolated traffic collection settings before any execution.
  4. Execute approved samples only inside the disposable victim VM, not on the analyst host, with human supervision and a stop procedure.
  5. Stop services, preserve permitted PCAP/log artifacts, hash them, and discard/revert the victim VM. Keep the analysis host offline afterward.

REMnux does not make malware safe merely by being a specialized distro. Dynamic testing has realistic risks of VM escape, accidental exfiltration and lateral movement. Start with offline samples and canned PCAPs when learning.

8. Evidence, IOCs and reporting

8.1 Integrity manifest

# Hash the ORIGINAL evidence directory only; store the manifest elsewhere.
(cd "$CASE/originals" && find . -type f -print0 | LC_ALL=C sort -z | \
  xargs -0 -r sha256sum) > "$CASE/reports/originals_sha256.txt"

# Later check against the same directory:
(cd "$CASE/originals" && sha256sum -c ../reports/originals_sha256.txt)

Use restricted, encrypted storage and approved backups. A SHA-256 manifest helps verify file integrity but does not by itself establish chain of custody or admissibility. Document every transfer, handling step and change.

8.2 Normalized observations

Each finding should contain:

  • Source artifact, SHA-256, UTC time, analyst, tool/version and command or GUI procedure.
  • Observed fields (header, import, string, object, PCAP packet) separated from inferred behavior.
  • IOC value/type and supporting evidence: domain, URL, hash, IP, file path, registry path, mutex, YARA hit, etc., only where evidenced.
  • Confidence, false-positive caveats, overlap with benign software, any contradicting data.
  • Privacy implications and a safe remediation or detection recommendation.

8.3 Report deliverable

CASE-2026-001/
โ”œโ”€โ”€ originals/       # Original evidence, immutable by policy
โ”œโ”€โ”€ working/         # Copies, extracted streams, decoded output, PCAPs
โ”œโ”€โ”€ logs/            # Tool versions, UTC timestamps, scope, custody
โ””โ”€โ”€ reports/
    โ”œโ”€โ”€ sample_sha256.txt
    โ”œโ”€โ”€ originals_sha256.txt
    โ”œโ”€โ”€ triage-notes.md
    โ”œโ”€โ”€ iocs.csv
    โ””โ”€โ”€ final-report.md

Map confirmed indicators to firewall/DNS/EDR/SIEM detection only after accounting for IP reallocation, legitimate shared services and potential false positives. Complete the IR playbook to coordinate containment and remediation; malware analysis by itself does not clean the endpoint.

9. Troubleshooting

Symptom Recommended response
Arm64 tool missing Check architecture-specific tool support; some amd64/Wine-dependent tools are unavailable.
VM imported but cannot boot Match arch + firmware: amd64 Proxmox uses SeaBIOS in current instructions; arm64 uses OVMF/EFI without Secure Boot.
VM starts with no network It may be intentional isolation. Only attach trusted connectivity in an explicit update window; never bridge sample-running VMs.
Default account still accepts malware Change password; restrict host/console access.
remnux install fails Run remnux results, inspect documented logs in a safe manner, use official support channels.
Static tool missing or wrong syntax Use command -v and --help, consult the REMnux tool directory, record versions and check arm64 caveats.
Unknown file appears to crash a parser Stop processing, isolate/restore VM, update parser in a safe window, and document exception.
Detection labels conflict Report uncertainty; verify provenance, hashes, rules and multiple independent sources.

10. References and integration

Official project documentation

PNWC cross-references


Maintained by Pacific Northwest Computers. Reviewed against current official REMnux documentation on 2026-10-26. Not executed against live malware; validate all tool versions, VM images, hashes and hypervisor behavior before production use.


๐Ÿ“„ Source: ReverseEngineering/remnux-malware-analysis-guide.md | โœ๏ธ Suggest an edit | โฌ…๏ธ Back to Reverse Engineering

Clone this wiki locally