bbllaacckkwwoollff-6ad8f762-1a91-45d7-a9c5-356bd858356aPyPI
Advisory published Updated
bbllaacckkwwoollff-6ad8f762-1a91-45d7-a9c5-356bd858356a is a confirmed malicious PyPI package (MAL-2025-3431) that steals credentials and exfiltrates sensitive data (malicious versions 0.1, 0.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bbllaacckkwwoollff-6ad8f762-1a91-45d7-a9c5-356bd858356a (PyPI)
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
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for bbllaacckkwwoollff-6ad8f762-1a91-45d7-a9c5-356bd858356a (2 malicious versions).
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.
Did it already run?
If bbllaacckkwwoollff-6ad8f762-1a91-45d7-a9c5-356bd858356a was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
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.