Malware in @doaction/examples
Malware was discovered in the npm package @doaction/examples. Systems with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different computer.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- @doaction/examples
The npm package @doaction/examples was found to contain malware. According to the GitHub Advisory (GHSA-3hg6-5qgp-v676), any computer that has this package installed or running should be considered fully compromised.
The advisory recommends that all secrets and keys stored on affected computers be rotated immediately from a different, uncompromised system. While the package should be removed, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the package installation, given that the outside entity may have gained full control of the system.
The package was published on npm and has been flagged as critical severity.
Indicators of compromise
- Packages
- @doaction/examples
Remediation
- Immediately rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Remove the @doaction/examples package from all affected systems
- Conduct a full security audit of any system that had this package installed
- Monitor affected systems for signs of unauthorized access or persistence mechanisms
- Consider rebuilding or reimaging systems that had this package installed, as removal alone may not eliminate all malicious artifacts
Sources
- GitHub Advisory GHSA-3hg6-5qgp-v676 · GitHub Advisory Database
Cite this entry
"Malware in @doaction/examples." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 9, 2026; last updated June 9, 2026. https://supplychainattack.org/incident/malware-in-doaction-examples-12yxdn
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in test2221 (npm)
The npm package test2221 version 2.2.4 was identified as malicious by the OpenSSF Package Analysis project. The package executes commands associated with malicious behavior.
npmCompromised package - containedcritical
Malware in n8n-nodes-trust-me-im-totally-safe
Malware was discovered in the npm package n8n-nodes-trust-me-im-totally-safe, resulting in full system compromise for any computer with the package installed or running. All secrets and keys on affected systems should be rotated immediately from a different computer.
npmCompromised package - activecritical
Malware in litespeed-cache
Malware discovered in the npm package litespeed-cache. The package grants full system compromise to attackers, requiring immediate removal and credential rotation from a clean system.
npmCompromised package - containedcritical
Malware in open-worker-cli
Malware was discovered in the npm package open-worker-cli. Systems with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different computer.
npmCompromised package