Which versions of f2d5cfdc642c3d5 are malicious?

The following PyPI versions of f2d5cfdc642c3d5 are flagged malicious: 0.1. Treat any of these as compromised.

How do I remediate f2d5cfdc642c3d5 if I installed it?

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

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

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

Malicious package

f2d5cfdc642c3d5PyPI

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

MAL-2025-3447

Immediate action

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

pip uninstall f2d5cfdc642c3d5

What this malware does

During installation, the code either exfiltrate some information about the system or download and execute remote code

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

Campaign: 2025-03-blackwolf

Reasons (based on the campaign):

The package overrides the install command in setup.py to execute malicious code during installation.
exfiltration-generic
Downloads and executes a remote malicious script.

Malicious versions

1 flagged

0.1

Indicators of compromise (SHA-256)

f645528fa23641ae18cf1a2e07873cafe74ae88b652524c1911168a72ebf04fb

84d50efcef96cad0f456ad083ecc48f07f446d61a00bf1909452ba7f5b6b45f7

ea846c355b07f5a44c9e9add5eccd50fcf359359f6fdc49de3f7b696697b87c2

2d8868a590a92449624a40235441363c818707c66859b32ff2312f1e93965426

b0f01416ae0495b0ff886c299f4ba5c0edaeda690cccffb610b063789150dff5

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

Campaign

RLMA-2025-025082025-03-blackwolfRLUA-2026-00309

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks f2d5cfdc642c3d5-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