Which versions of bprintoor are malicious?

The following PyPI versions of bprintoor are flagged malicious: 0.2.2, 0.2.3, 0.2.4, 0.2.5, 0.2.6, 0.2.7, 0.2.8, 0.2.9, 0.2.10, 0.2.11. Treat any of these as compromised.

How do I remediate bprintoor if I installed it?

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

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

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

Malicious package

bprintoorPyPI

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

MAL-2025-191694

Immediate action

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

pip uninstall bprintoor

What this malware does

Infostealer with multiple possibilities, but not auto-activating on installation. There are already multiple attempts to publish it, with different innocent-looking names.

The campaign contains the with Infostealer itself and packages that include it as dependency and triggered.

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

Campaign: 2025-02-multis

Reasons (based on the campaign):

infostealer
The malicious code is intentionally included in a dependency of the package

Malicious versions

10 flagged

0.2.20.2.30.2.40.2.50.2.60.2.70.2.80.2.90.2.100.2.11

Indicators of compromise (SHA-256)

1b3d6d389dcf9f6fed53c6a5f6b3936f95ba68ee3a7a545398457f23401c23a4

ca03f86b909883f380bfa18a115d0a840f2195938d5b154f62b69e991865a496

03e18022b0fcfc12a37ea0dc15ef43b1996aea28c413c67c51a238241b8c165b

8315c11855d439dddd9db818a30836517668f328d5790734c9e3ed997448c298

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

Campaign

2025-02-multis

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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