Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

bbllaacckkwwoollff-6ad8f762-1a91-45d7-a9c5-356bd858356aPyPI

Malicious code in bbllaacckkwwoollff-6ad8f762-1a91-45d7-a9c5-356bd858356a (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-3431
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
pip uninstall bbllaacckkwwoollff-6ad8f762-1a91-45d7-a9c5-356bd858356a

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)

7362714843387dffdd9aa97a38edfff2bf47756e8f92f69a2df0e713739a9852
ca71f8fd9d4d0839564f1a52e8a8353328f7b5d54077156c15f5cea8b4cb7fcd
4da60ab5fd2248194d9c485e99360f30cd77d89de065b6f30259328cfcadd2f2
f4215a2ca2f0b9eebd4210c0de1f850ec88b52feaba36ba4edaaed61f6c53ffa
d1eb232d31643c4b12409b48f9a00073531e721aee26b9fde12c7cee0bacffe6

Detection & response playbook

Credential / info stealer
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bbllaacckkwwoollff-6ad8f762-1a91-45d7-a9c5-356bd858356a (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bbllaacckkwwoollff-6ad8f762-1a91-45d7-a9c5-356bd858356a across your stack and pipelines.

  2. If you installed it — respond

    bbllaacckkwwoollff-6ad8f762-1a91-45d7-a9c5-356bd858356a 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.

  3. Did it already run?

    If bbllaacckkwwoollff-6ad8f762-1a91-45d7-a9c5-356bd858356a 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.

  4. How O3 protects you

    O3 blocks bbllaacckkwwoollff-6ad8f762-1a91-45d7-a9c5-356bd858356a 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. bbllaacckkwwoollff-6ad8f762-1a91-45d7-a9c5-356bd858356a 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-024902025-03-blackwolfRLUA-2026-00137

References

Credits

  • Kamil Mańkowski (kam193)
  • ReversingLabs · finder

Detect & block this

O3 blocks bbllaacckkwwoollff-6ad8f762-1a91-45d7-a9c5-356bd858356a-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

bbllaacckkwwoollff-6ad8f762-1a91-45d7-a9c5-356bd858356a (PyPI) malicious package — MAL-2025-3431 | O3 Security