npm · Malicious package advisory
Malwareccl-component-resources
MAL-2024-1959
Malicious code in ccl-component-resources (npm)
Details
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (a3aab5a60bbc55422ada7e8937985342cfee30ddac8e35dab2c0d03eb3d12d23) [email protected] is a dependency-confusion package: name targets a likely-internal package, semver is set to 99.0.0 to win resolution against private registries, and index.js is an empty stub (`module.exports = {}`). package.json declares a `preinstall` lifecycle hook that runs `node pingback.js`. pingback.js reads `os.hostname()` and POSTs a JSON payload (`{hn,...package name, timestamp}`) to https://c.adityasec.com/hJWEvPPiaUrSeF-9_F8XSw on every `npm install`. Any installer whose private dependency resolution mistakenly pulls this public package will leak the host identifier of the affected dev or CI machine to an external server. The package self-describes as an 'authorized PoC,' but the beacon fires unconditionally for every installer regardless of authorization, and the destination is attacker-controlled from the installer's perspective. ## Source: ghsa-malware (52457ecea7368bd344af743e12379cfe57ee096bd0a3490246f1cf2d74cb5d4f) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Compromised versions (3)
- 1.0.732
- 99.0.0
- 99.1.0
Any computer that installed or ran a compromised version should be considered fully compromised. Rotate every secret on that machine from a clean environment.