MalwarePublished 9 Jun 2026Updated 9 Jul 2026

@doaction/example (npm) · Malicious Code

Affects @doaction/exampleSource GCVE Database

Malicious package : remove @doaction/example and rotate any secrets on hosts that installed it.

Data as of 10 Jul 2026, 09:52 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-5371

What to do

Remove @doaction/example 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/example	Affected =99.99.99 =9.9.9	Fixed in–

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

Description

The npm package @doaction/example versions 9.9.9 and 99.99.99 contain malicious code. The package's preinstall script delegates execution to a shared dependency whose behavior is unknown and potentially harmful. Installation of this package may lead to full system compromise, requiring immediate secret and key rotation. Removal of the package alone may not eliminate all malicious components.

Impact

Systems with this package installed or running are considered fully compromised. Attackers may have gained full control, risking exposure of all stored secrets and keys. Immediate secret rotation from a secure environment is required. Removal of the package does not guarantee elimination of all malicious artifacts.

Defensive guidance

Immediate removal of the @doaction/example package versions 9.9.9 and 99.99.99 is recommended. All secrets and keys on affected systems should be rotated immediately from a secure, uncompromised environment. Due to potential persistent compromise, consider full system remediation or rebuild. Review and audit internal package namespaces to prevent dependency confusion attacks.

Summary

@doaction/example is a scoped npm package with versions 9.9.9 and 99.99.99 identified as malicious. Its package.json includes a preinstall script that calls code from a shared dependency (@doaction/shared) whose actual behavior is not included in the tarball and remains unverified. The package's versioning and namespace suggest a possible dependency confusion attack targeting internal namespaces. According to the source ghsa-malware, any system with this package installed should be considered fully compromised, and all secrets must be rotated. The package should be removed, but full remediation is uncertain due to potential persistent malicious code.

References

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Jul 2026, 09:52 UTC

Technical details

References

Community reviews