Which versions of blank-lib are malicious?

The following PyPI versions of blank-lib are flagged malicious: 0.0.8, 0.0.9, 0.1.0. Treat any of these as compromised.

How do I remediate blank-lib if I installed it?

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

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

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

Malicious package

blank-libPyPI

Malicious code in blank-lib (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-192364

Immediate action

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

pip uninstall blank-lib

What this malware does

This is an infostealer, based on Blank Grabber. It's used as dependency in other malicious packages

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2025-12-blank-lib

Reasons (based on the campaign):

infostealer
infostealer:blankgrabber
clones-real-package
The malicious code is intentionally included in a dependency of the package
exfiltration-credentials

Malicious versions

3 flagged

0.0.80.0.90.1.0

Indicators of compromise (SHA-256)

96f1bcd77950a6cd42af11d0d4fb4ba3d58349cfde6236027341c044e152bfeb

b0f1560379fabce56cf4ff03d12317400dd419a744927ff319fa4275f9e25367

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

Campaign

2025-12-blank-lib

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks blank-lib-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