Malware in @caspianph/first-npm-package
The npm package @caspianph/first-npm-package contained malware that provided full system compromise to attackers. Any computer with this package installed should be considered fully compromised and all secrets and keys rotated immediately.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed
- Ecosystems
- Attack vectors
- Affected entities
- @caspianph/first-npm-package
A malicious npm package, @caspianph/first-npm-package, was published to the npm registry containing malware capable of achieving full system compromise.\n\nAccording to the GitHub Advisory (GHSA-r6j8-4ffv-6mcj), any computer that has this package installed or running should be considered fully compromised. The malware grants outside entities full control of affected systems.\n\nImmediate remediation requires rotating all secrets and keys stored on affected computers from a different, uncompromised system. While the package should be removed, complete removal of all malicious software resulting from the installation cannot be guaranteed due to the level of system access the malware obtained.\n\nThe package has been identified and removed from the registry, marking this incident as resolved.
Indicators of compromise
- Packages
- @caspianph/first-npm-package
Remediation
- Immediately rotate all secrets, keys, and credentials stored on any computer that had this package installed, using a different uncompromised computer
- Remove the @caspianph/first-npm-package package from all systems
- Perform a full security audit and malware scan of any affected systems
- Consider the affected systems as potentially fully compromised and plan for complete reimaging if critical infrastructure
- Review access logs and monitor for any unauthorized activity on systems that had this package installed
Sources
- GitHub Advisory GHSA-r6j8-4ffv-6mcj · GitHub Advisory Database
Cite this entry
"Malware in @caspianph/first-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-first-npm-package-1628qv
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 rust-testing-utils (npm)
The npm package rust-testing-utils contained malicious code that impersonates the pino logger and executes remotely-fetched code with arbitrary privileges. The package spawns a child process that decodes a hardcoded URL, fetches attacker-controlled content, and executes it via Function constructor with full module-loading capability.
npmCompromised packageMalicious commit - containedcritical
Malicious code in stillm4ddpocs-demo-sprocket (npm)
The npm package stillm4ddpocs-demo-sprocket version 999.9.12 contains malicious code that exfiltrates system and project metadata via multiple channels (HTTPS, HTTP, and DNS) to a hardcoded callback host. The package uses a high version number to exploit dependency-confusion attacks against organizations with internal packages of the same name.
npmCompromised packageDependency confusion - containedcritical
Malicious code in @syncraft-labs/react (npm)
The npm package @syncraft-labs/react contained obfuscated malicious code in its ESM distribution that implements the EtherHiding pattern, fetching and executing arbitrary code from an Ethereum smart contract via RPC endpoints. The tampering occurred post-build in the dist/index.js artifact.
npmCompromised package - containedcritical
Malware in hydration-dim-kit
Malware was discovered in the npm package hydration-dim-kit. Any computer with this package installed or running should be considered fully compromised. All secrets and keys must be rotated immediately from a different computer.
npmCompromised package