Malicious code in @doaction/example (npm)
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.
AI Analysis
Technical 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.
Potential 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.
Mitigation Recommendations
No official patch or fix is available. 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.
Malicious code in @doaction/example (npm)
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.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
@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.
Potential 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.
Mitigation Recommendations
No official patch or fix is available. 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.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-5371
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-w4g4-r5qj-rj58"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a50ba7168715ace435800e6
Added to database: 07/10/2026, 09:25:05 UTC
Last enriched: 07/10/2026, 09:52:55 UTC
Last updated: 07/31/2026, 11:55:25 UTC
Views: 25
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.