@doaction/examples (npm) · Malicious Code
Affects @doaction/examplesSource GCVE Database
Malicious package : remove @doaction/examples and rotate any secrets on hosts that installed it.
Data as of 10 Jul 2026, 09:52 UTC
Malicious package
Published to npm · OSV MAL-2026-5372
What to do
Remove @doaction/examples 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 |
|---|---|---|
| npm@doaction/examples | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
The @doaction/examples npm package version 99.99.99 (and also 9.9.9) contains malicious code executed during installation via a preinstall hook. This hook runs a script that loads telemetry code from a sibling package, which collects environment variables and sends them to a remote destination without user consent or opt-out. The package is labeled 'for internal testing' but is publicly available, enabling dependency confusion attacks where organizations expecting internal @doaction packages may inadvertently install this malicious public package. The presence of inconsistent script naming further obscures the malicious behavior. Systems with this package installed should be considered fully compromised, and all secrets and keys on those systems must be rotated immediately. Removing the package alone may not fully remediate the compromise.