Which versions of bbllaacckkwwoollff6ad8f753 are malicious?

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

How do I remediate bbllaacckkwwoollff6ad8f753 if I installed it?

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

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

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

Malicious package

bbllaacckkwwoollff6ad8f753PyPI

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

MAL-2025-3434

Immediate action

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

pip uninstall bbllaacckkwwoollff6ad8f753

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)

062bd372a936ab285231dbe3ff1244c1b1100ef7d338288350dd1952a35b2023

d7a9f63d22f84c56a43ac7bcd4d6ded7f2bf36a17f0ea0307b211cc7eedd2990

6d4b59c0779917e138aea3b1a424593ca84b58fa16a0cd75ba8a4c7523f92c87

28be32f14e54bf1f6e2278cedee5d1249ffbf10b0a4358771cd36e6b3ad1b9b7

eddb143900979d2ffe025e1d582c0ead31e5d362781489418b90eb9315a648f6

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

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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