Which versions of f2d5cfdc642c3d4 are malicious?

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

How do I remediate f2d5cfdc642c3d4 if I installed it?

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

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

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

Malicious package

f2d5cfdc642c3d4PyPI

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

MAL-2025-3446

Immediate action

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

pip uninstall f2d5cfdc642c3d4

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)

8de879cbae7f0c0d8d0504f70d5ce0a881019224078f5143785fac95431acb66

8e32f7952fd1b2e712867d8494652135b525a77488b58a51d52b7c8952921e03

7996c4b5f5093de9bc2646228bce15683af10ede7957a934c5afa67346f1149d

ff7c6638c08cc79cad71c2fa5e47654b5b93dfdc34eb1a12fbf9dad94d373266

8638411b35b6c028a307373e1b7ab69536e920e4c76db5228d49b9721f25ce2c

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 f2d5cfdc642c3d4 (version 0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging f2d5cfdc642c3d4 across your stack and pipelines.
If you installed it — respond
f2d5cfdc642c3d4 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 f2d5cfdc642c3d4 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 f2d5cfdc642c3d4 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. f2d5cfdc642c3d4 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-025072025-03-blackwolfRLUA-2026-00308

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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