Which versions of simplewave are malicious?

The following npm versions of simplewave are flagged malicious: 0.0.2. Treat any of these as compromised.

How do I remediate simplewave if I installed it?

simplewave is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed simplewave — how do I know if it already compromised me?

If simplewave was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is simplewave part of a known attack campaign?

Yes — simplewave is associated with the IN-MAL-2026-021566 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find simplewave across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for simplewave (version 0.0.2).

Malicious package

simplewavenpm

Advisory published Oct 22, 2026Updated Oct 22, 2026

simplewave is a confirmed malicious npm package (MAL-2026-18187) that steals credentials and exfiltrates sensitive data (malicious version 0.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in simplewave (npm)

MAL-2026-18187

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall simplewave

What this malware does

[email protected] declares a postinstall script in package.json that runs an inline Node command performing an HTTP GET to a subdomain of oast.fun with the installer's os.hostname() embedded as the leftmost DNS label. oast.fun is the public Interactsh out-of-band interaction server, used to receive exfiltrated data via DNS/HTTP callbacks. The beacon fires unconditionally on npm install, with no caller consent or configuration. The shipped index.js is a trivial stub providing no advertised functionality, so the manifest-level beacon is the package's entire effect. The host identifier of every machine that installs the package is delivered to a third-party OOB collector controlled by whoever provisioned the oast.fun subdomain token.

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

d984cf27dec602e96199a4361b485f0a7c79e2134977a355d42ddb46edd606d0

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for simplewave (version 0.0.2).
If you installed it — respond
simplewave is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If simplewave was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. simplewave on npm has been identified as a malicious package (version 0.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-021566

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks simplewave-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database