Is simplewave malicious?
Yes. Protet confirmed 1 version of simplewave as malicious
First confirmed on 2026-10-22.
Affected versions
| Version | Confirmed | Protet record |
|---|---|---|
| 0.0.2 | 2026-10-22 | PROTET-NPM-2026-15 |
What it does
The package runs a one-line Node.js command from its postinstall script. The command sends an HTTP GET request to a host name made of the machine's host name followed by a fixed random label under oast.fun, a public out-of-band interaction service, so the machine's host name reaches the operator through the DNS and HTTP lookup. It does nothing else. The package has no legitimate function: it belongs to a dependency-confusion beacon campaign.
Impact: the operator learns which machines install the package and their host names.
Remediation: remove the package from all projects and lockfiles and review the hosts that installed it.
Indicators
Domainsoast.fun
Other reports
- Also reported in OSV as MAL-2026-18187
What to do if you installed it
- Remove the package from every project that uses it, directly or through another dependency.
- Pin a clean version if you need the package: one that is not listed above and that you have checked yourself, or replace the package. A version missing from this page is not cleared.
- Check your lockfiles (
package-lock.json,yarn.lock,pnpm-lock.yaml) for the affected versions, including as a transitive dependency, and in CI caches. - Rotate credentials that were reachable from any machine or build that installed it: npm and GitHub tokens, cloud keys, SSH keys, and secrets in environment variables or CI settings.
Status history
- 2026-10-22: 0.0.2 named by Protet Intel