Which versions of cffi-curl are malicious?

The following PyPI versions of cffi-curl are flagged malicious: 0.13.0. Treat any of these as compromised.

How do I remediate cffi-curl if I installed it?

cffi-curl 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 cffi-curl — how do I know if it already compromised me?

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

Yes — cffi-curl is associated with the RLMA-2025-04752, 2025-08-cffi-curl, RLUA-2026-00183 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 cffi-curl 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 cffi-curl (version 0.13.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cffi-curl across your stack and pipelines.

Malicious package

cffi-curlPyPI

Malicious code in cffi-curl (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-47752

Immediate action

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

pip uninstall cffi-curl

What this malware does

Malicious clone of a legitimate package "curl-cffi". When importing the module, it runs an obfuscated PowerShell command

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

Campaign: 2025-08-cffi-curl

Reasons (based on the campaign):

typosquatting
obfuscation
malware
clones-real-package

Malicious versions

1 flagged

0.13.0

Indicators of compromise (SHA-256)

b5a05745087bdbd7fd40c331c27dbefcadebdb63972390b2c99d677b42604270

1e9ea65819468728fa86fb297e98f30cc327fc8e9b224f90b2847a2d89bf9525

1bdc2d55f462ed9009995743e5bc50ed10641cffa24d5b16606e3a479fffae10

fbc1c68f5a2291eea2fd6b72cf7a50c7b4c19b3e7797cb7b4d204c5d85d58ad1

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 cffi-curl (version 0.13.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cffi-curl across your stack and pipelines.
If you installed it — respond
cffi-curl 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 cffi-curl 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 cffi-curl 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. cffi-curl on PyPI has been identified as a malicious package (version 0.13.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-047522025-08-cffi-curlRLUA-2026-00183

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks cffi-curl-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