@doaction/examplenpm
Advisory published Updated
@doaction/example is a confirmed malicious npm package (MAL-2026-5371) that executes malicious code on install (malicious versions 9.9.9, 99.99.99). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @doaction/example (npm)
What this malware does
@doaction/[email protected] is a scoped npm package whose package.json self-describes as 'Example package with Datadog environment telemetry for internal testing' and pins @doaction/shared at ^99.99.99. On install, scripts/preinstall.js delegates execution to @doaction/shared/bin/preinstall.js via require('@doaction/shared/bin/preinstall.js'). The shared dependency's preinstall code is not present in this tarball and its actual behavior cannot be confirmed from the contents shipped here. The library API reportExampleEnv (src/index.js) is opt-in: callers must explicitly supply a Datadog API key and invoke the function, and the documented whitelist is limited to EXAMPLE_MODE and EXAMPLE_DEBUG. The installer-facing risk depends entirely on what @doaction/shared's preinstall and collectEnv actually do — those bytes need to be reviewed before a final disposition. The 99.99.99 version pattern combined with the scoped name is also consistent with a dependency-confusion shape against an internal @doaction namespace, which warrants human assessment.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Search your lockfiles and build artifacts for @doaction/example (2 malicious versions).
If you installed it — respond
Remove @doaction/example from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If @doaction/example 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @doaction/example-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.