ccl-component-resourcesnpm
ccl-component-resources is a confirmed malicious npm package (MAL-2024-1959) that opens a backdoor for remote access (malicious versions 1.0.732, 99.0.0, 99.1.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in ccl-component-resources (npm)
What this malware does
[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.
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ccl-component-resources (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ccl-component-resources across your stack and pipelines.
If you installed it — respond
ccl-component-resources establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If ccl-component-resources was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks ccl-component-resources before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- ReversingLabs · finder
Detect & block this
O3 blocks ccl-component-resources-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.