Which versions of bbllaacckkwwoollff6ad8f752 are malicious?

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

How do I remediate bbllaacckkwwoollff6ad8f752 if I installed it?

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

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

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

Malicious package

bbllaacckkwwoollff6ad8f752PyPI

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

MAL-2025-3433

Immediate action

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

pip uninstall bbllaacckkwwoollff6ad8f752

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

2 flagged

0.10.2

Indicators of compromise (SHA-256)

72e980b84ba0111bc57e8e35b03f96d070fbde5a53269d37a5b1c882b72fa4f0

bdf7126792a545d18d203fe68b591281199352da9d1ad033874610731c1187f7

e1532a9577dc6edfd513dfbb1f189bc4cd08297e76c1f93bb2bf25ceaa210618

2b769543b9f9334486333199ed4553df7dce7b143a6f7d18a0182253891c40c6

0c8e7c8a388b6004c9885200a90d6e92d97521286dfce3319430f0f8d158710d

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

Campaign

RLMA-2025-024922025-03-blackwolfRLUA-2026-00139

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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