Malware in @caspianph/second-npm-package
Malware was discovered in the npm package @caspianph/second-npm-package. Systems with this package installed are considered fully compromised and require immediate remediation.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- @caspianph/second-npm-package
A malicious npm package, @caspianph/second-npm-package, was identified and published to the npm registry. The package contains malware that grants full control of affected systems to an outside entity.\n\nAny computer with this package installed or running should be considered fully compromised. The malware may persist even after package removal due to the level of system access it obtained.\n\nImmediate action is required: all secrets and keys stored on affected computers should be rotated from a different, uncompromised system. The package should be removed, though complete remediation may require additional forensic investigation and system hardening.
Indicators of compromise
- Packages
- @caspianph/second-npm-package
Remediation
- Immediately rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Remove the @caspianph/second-npm-package package from all affected systems
- Conduct forensic analysis to identify any additional malicious software installed by the package
- Review system logs and network connections for signs of unauthorized access or data exfiltration
- Consider full system reimaging if the package was installed on production or sensitive systems
- Audit npm package dependencies across your organization to identify other potentially compromised packages
Sources
- GitHub Advisory GHSA-qmxg-fj5j-hjx8 · GitHub Advisory Database
Cite this entry
"Malware in @caspianph/second-npm-package." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 13, 2026; last updated August 13, 2026. https://supplychainattack.org/incident/malware-in-caspianph-second-npm-package-63uhx7
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- activecritical
Malware in banana-stand
The npm package banana-stand contains malware that grants full system compromise to an outside entity. Any computer with this package installed or running should be considered fully compromised.
npmCompromised package - containedcritical
Malware in @siwatfa/yorn
Malware was discovered in the npm package @siwatfa/yorn. 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 - resolvedcritical
Malicious code in epic-common-node (npm)
The npm package epic-common-node was found to contain malicious code. The package has been identified and reported through GitHub Security Advisory GHSA-m36g-mhjr-ww2c.
npmCompromised package - activecritical
Malware in rendezvous-js
The npm package rendezvous-js contains malware that grants full control of affected systems. Any computer with this package installed or running should be considered fully compromised.
npmCompromised package