Which versions of bbllaacckkwwoollff6ad8f762 are malicious?

The following PyPI versions of bbllaacckkwwoollff6ad8f762 are flagged malicious: 0.1, 0.2, 0.3. Treat any of these as compromised.

How do I remediate bbllaacckkwwoollff6ad8f762 if I installed it?

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

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

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

Malicious package

bbllaacckkwwoollff6ad8f762PyPI

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

MAL-2025-3435

Immediate action

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

pip uninstall bbllaacckkwwoollff6ad8f762

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

3 flagged

0.10.20.3

Indicators of compromise (SHA-256)

1a7ca5dd9246f809a111116ae7063c65b60926ec2bd67a7e9c8cd141084ea05a

a0c16b7657653def9f66b50e8d66c0edf6cbd46d2134e1f6762a419236d51e15

4d90faddd66012c6f6fadc95f0a0e846b70504ed6ea47a65576ef5c4067a4985

2ebe8d10a9c8f194337ad8c083971ab38c94aef91942c7c9e3cfafd602f2a289

3efc7c8b48c8361aaa7526270e1ad27546670b25b60ced6c5d920104ed7adabc

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

Campaign

RLMA-2025-024942025-03-blackwolfRLUA-2026-00141

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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