Malware in @caspianph/third-npm-package
Malware was discovered in the npm package @caspianph/third-npm-package. Installation or execution of this package results in full system compromise. All secrets and keys on affected systems should be rotated immediately from a clean machine.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- @caspianph/third-npm-package
A malicious npm package, @caspianph/third-npm-package, was identified and published to the npm registry. The package contains malware that grants full control of the host system to an outside entity upon installation or execution.
Any computer with this package installed or running should be considered fully compromised. All secrets, keys, and credentials stored on affected systems must be rotated immediately from a different, uncompromised computer.
While the package should be removed, complete remediation cannot be guaranteed due to the level of system access granted to the attacker. Additional forensic analysis and system hardening may be necessary to ensure all malicious artifacts are eliminated.
The advisory was published on 2026-08-13 via GitHub Security Advisory GHSA-g4m3-cq7f-6f85.
Indicators of compromise
- Packages
- @caspianph/third-npm-package
Remediation
- Immediately remove @caspianph/third-npm-package from all systems
- Rotate all secrets, keys, and credentials from a clean, uncompromised computer
- Perform forensic analysis on affected systems to identify any additional malicious artifacts
- Consider full system reimaging or replacement if the system handles sensitive data
- Monitor affected systems for signs of continued unauthorized access or data exfiltration
- Review audit logs and network traffic for indicators of compromise
Sources
- GitHub Advisory GHSA-g4m3-cq7f-6f85 · GitHub Advisory Database
Cite this entry
"Malware in @caspianph/third-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-third-npm-package-5314ga
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