What does the cloudscrapersafe malware do?

During processing the user requests, the package looks for URLs related to checkouts using services: - credomatic.compassmerchantsolutions.com - checkout.baccredomatic.com and exfiltrates given credit card numbers, verification codes etc. Interestingly, it checks even 3DS responses. Clone of the legitimate "cloudscraper" package. Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers. Campaign: 2025-07-cloudscrapersafe Reasons (based on the campaign): - action-hidden-in-lib-usage - exfiltration-generic - clones-real-package

Which versions of cloudscrapersafe are malicious?

The following PyPI versions of cloudscrapersafe are flagged malicious: 3.0.0, 3.1.0, 3.1.1. Treat any of these as compromised.

How do I remediate cloudscrapersafe if I installed it?

cloudscrapersafe is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed cloudscrapersafe — how do I know if it already compromised me?

If cloudscrapersafe 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 cloudscrapersafe part of a known attack campaign?

Yes — cloudscrapersafe is associated with the RLMA-2025-03563, 2025-07-cloudscrapersafe, RLUA-2026-00196 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 cloudscrapersafe 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 cloudscrapersafe (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cloudscrapersafe across your stack and pipelines.

Malicious package

cloudscrapersafePyPI

Malicious code in cloudscrapersafe (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-6478

Immediate action

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

pip uninstall cloudscrapersafe

What this malware does

During processing the user requests, the package looks for URLs related to checkouts using services:

credomatic.compassmerchantsolutions.com
checkout.baccredomatic.com and exfiltrates given credit card numbers, verification codes etc. Interestingly, it checks even 3DS responses.

Clone of the legitimate "cloudscraper" package.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2025-07-cloudscrapersafe

Reasons (based on the campaign):

action-hidden-in-lib-usage
exfiltration-generic
clones-real-package

Malicious versions

3 flagged

3.0.03.1.03.1.1

Indicators of compromise (SHA-256)

aaa50ce8270e9aea79dd5e82e629190c5453fa565f609771d277746bf84de6e2

6944a90e2050c1774fddbb3e1bc7bac1c298245b9deef45fb50fd828a4050ed5

2420d6a750823b640af4d97d3a2a26383ce9e32d3ac266e4792675e8beb9b806

51d27c65c6f9d6dc0bf33a47219228da73ffd60b15808b0bf0b8a4bd027fb16c

8f9df6a19142786919843598f583185471e6b998b404faf0fa7316526da472eb

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for cloudscrapersafe (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cloudscrapersafe across your stack and pipelines.
If you installed it — respond
cloudscrapersafe is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If cloudscrapersafe 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 cloudscrapersafe 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. cloudscrapersafe on PyPI has been identified as a malicious package (versions 3.0.0, 3.1.0, 3.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-035632025-07-cloudscrapersafeRLUA-2026-00196

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks cloudscrapersafe-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring