Which versions of bbllaacckkwwoollff6ad8f751 are malicious?

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

How do I remediate bbllaacckkwwoollff6ad8f751 if I installed it?

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

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

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

Malicious package

bbllaacckkwwoollff6ad8f751PyPI

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

MAL-2025-3432

Immediate action

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

pip uninstall bbllaacckkwwoollff6ad8f751

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)

febc7a27b3039a70f970dd07b8d215c3ae5ca734d0903ef8a0635d2c51690437

7dc62e2598cbfb6155a788432914de576f573fdcc9f035848687416e630c61e1

e88e848094db2d7414ceaf71a5a332701df9a17b145c137f0f5df76503847f90

56f44be45f7fe4a2fd0011e117ad515b7cb88ae0c4289a097bcf23cba470c723

6667729590c09deb746dfecd660694ce7f0e3127e70b5e42cb0f1a8a04f85aaa

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

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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