GhostMap Rootkit Lets IronWorm Evade Linux Security Tools

Cybersecurity researchers have uncovered a new technique that allows the IronWorm malware to hide on Linux systems using a rootkit called GhostMap. The rootkit leverages Linux’s eBPF subsystem to conceal processes, files, and network sockets from common inspection tools. Even when certain entries disappear from tools like ps or /proc/net/tcp, they may still be accessible through alternate interfaces like ss, due to the rootkit’s selective filtering.

How GhostMap Conceals IronWorm’s Activity

IronWorm is a Rust-based malware strain spread via malware-laced software packages. Once executed with root access, IronWorm installs itself into the /var/lib directory and sets up persistence through systemd, which then triggers the loading of GhostMap. The rootkit uses multiple eBPF programs—13 identified in one test—and accompanying data maps to enforce low-level filtering. These filters selectively omit targeted entries from directory listings and network files without physically removing them from memory.

In experiments, security testers observed that processes controlled by IronWorm, while omitted from typical listings using ps or /proc, were still reachable via their full /proc/PID paths. Similarly, a local collector socket vanished from reading /proc/net/tcp but remained visible through ss. Another indicator involved files dropped from directory listings via minimal modifications—sometimes only one byte—to bypass detection.

Links Between IronWorm and Atomic Arch Campaigns

Further examination revealed almost identical GhostMap components in another malware campaign known as Atomic Arch, which abused compromised Arch User Repository build scripts. Although overlaps in rootkit code and eBPF map names suggest shared techniques or toolkit reuse, no definitive evidence connects both campaigns to the same attacker.

To count as a detection success rather than simple visibility, Aqua Security tested several defenses. Tracee—an open-source runtime security tool—recognized three eBPF programs with write permissions on application memory during attachment, and noted all 48 directory-reader calls made in the test environment. But that visibility does not equate to prevention of malicious actions, only exposure after the fact.

How to Detect Compromise and Indicators to Watch For

Investigators are advised to cross-check process listings with known /proc/PID paths and execution histories. Hidden services in systemd, unexpected eBPF attachments, and the preservation of metadata such as extended attributes on executables are also crucial signs. Strong indicators include several specific SHA-256 hashes linked to IronWorm artifacts, including the npm package [email protected], as well as payloads in the Atomic Arch campaign.

Targets affected include compromised Linux hosts where IronWorm or Atomic Arch payloads have been delivered—primarily through supply chain attacks embedded in software dependencies and repositories.

This development reflects a growing trend of malware using legitimate kernel mechanisms for stealth. With rootkits like GhostMap, attackers are going beyond traditional evasion: they’re manipulating visibility at the kernel level without altering observable system behavior externally.

Analytical Take: The use of eBPF by IronWorm via GhostMap marks a sophisticated escalation in Linux malware stealth capabilities. Security tools designed for visibility, not intervention, remain vulnerable to such concealment strategies. Defenders must adapt by integrating kernel-level monitoring, verifying execution paths, and securing supply chains. Vigilance over software dependencies, unexpected root-privileged components, and system metadata could be the difference between detection and full compromise.