Which versions of ccs-react-lib are malicious?

The following npm versions of ccs-react-lib are flagged malicious: 1.0.0, 2.0.0, 7.7.7, 7.7.8. Treat any of these as compromised.

How do I remediate ccs-react-lib if I installed it?

Remove ccs-react-lib from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed ccs-react-lib — how do I know if it already compromised me?

If ccs-react-lib 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.

Is ccs-react-lib part of a known attack campaign?

Yes — ccs-react-lib is associated with the RLMA-2024-10489, GHSA-4w4g-jxg8-g7j7, RLUA-2025-06081 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find ccs-react-lib across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ccs-react-lib (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ccs-react-lib across your stack and pipelines.

Malicious package

ccs-react-libnpm

ccs-react-lib is a confirmed malicious npm package (MAL-2024-11326) that executes malicious code on install (malicious versions 1.0.0, 2.0.0, 7.7.7…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ccs-react-lib (npm)

MAL-2024-11326

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall ccs-react-lib

What this malware does

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

4 flagged

1.0.02.0.07.7.77.7.8

Indicators of compromise (SHA-256)

2eb6e9f68cb8482c1309441a185a6aa90cc74397f210ee29061717f956f8491c

a19b5e1d7248b1e5a66bcf5c2ae1bae25a94e6948728331d29c1a363881e05b5

00988c71f73a5471c09a96bfd4fed482726890e19b40663ed0bbe9d8b87f10b2

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ccs-react-lib (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ccs-react-lib across your stack and pipelines.
If you installed it — respond
Remove ccs-react-lib from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If ccs-react-lib 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 ccs-react-lib 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

No. ccs-react-lib on npm has been identified as a malicious package (versions 1.0.0, 2.0.0, 7.7.7, 7.7.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-10489GHSA-4w4g-jxg8-g7j7RLUA-2025-06081

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks ccs-react-lib-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database