MalwarePublished 26 May 2026Updated 26 Jun 2026

wao (npm) · Malicious Code

Affects waoSource GCVE Database

Malicious package : remove wao and rotate any secrets on hosts that installed it.

Data as of 26 Jun 2026, 22:32 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-4711

What to do

Remove wao from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

Product	Affected	Fixed in
npmwao	Affected =0.41.2 =0.41.3 =0.41.4	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

The wao npm package versions 0.41.2, 0.41.3, and 0.41.4 contain a malicious preinstall lifecycle hook that executes a disguised native Linux ELF binary. This binary acts as a credential-harvesting implant with capabilities including eBPF and ptrace usage, outbound HTTPS exfiltration, and a secondary payload channel. The malware targets developer environments, stealing credentials for cloud providers, source control, package registries, AI tools, and cryptocurrency wallets. It also exhibits worm-like behavior by pushing malicious updates to repositories and publishing trojanized packages. The infection may result in full system compromise, and removing the package does not guarantee eradication of the malware.

Impact

Systems with the affected wao package versions installed are likely fully compromised. The malware harvests a wide range of sensitive credentials, including cloud, database, source control, package registry, AI tool, and cryptocurrency wallet credentials. It uses kernel rootkit techniques to evade detection and can propagate by pushing malicious updates to repositories and publishing trojanized packages. Secrets and keys stored on infected machines should be considered compromised and rotated immediately. Removing the package alone does not guarantee removal of all malicious components or persistence mechanisms.

Defensive guidance

Users should immediately remove the affected wao package versions (=0.41.2, =0.41.3, =0.41.4) from their systems. Due to the high likelihood of full system compromise, all secrets, credentials, and keys stored on the affected machines must be rotated from a separate, trusted environment. Comprehensive incident response and forensic analysis are recommended to identify and eradicate any persistent malware. Monitor for any suspicious activity related to repository updates or package publishing. Verify the integrity of developer environments before reinstalling any packages.

Summary

The wao npm package was compromised as part of the IronWorm campaign. Its package.json declares a preinstall script that executes a 976KB Linux ELF binary disguised as a TypeScript file (deps.ts). This binary is a Rust-built infostealer implant that harvests credentials related to cloud services, databases, source control, package registries, AI developer tools, and cryptocurrency wallets, including injecting malicious JavaScript into the Exodus wallet. It uses eBPF-based kernel rootkit techniques to hide its presence on Linux systems and exhibits worm-like propagation by stealing GitHub and NPM credentials to push malicious updates and publish trojanized packages. The 0.41.2 tarball also contains an undeclared large secondary payload (wao-0.41.1.tgz), enabling further malicious activity. This behavior results in full compromise of any system with the package installed or running.

References

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Jun 2026, 22:32 UTC

Technical details

References

Community reviews