Which versions of binproto are malicious?

The following PyPI versions of binproto are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate binproto if I installed it?

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

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

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

Malicious package

binprotoPyPI

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

MAL-2026-4810

Immediate action

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

pip uninstall binproto

What this malware does

When using the provided functionality, the code silently downloads and executes a malicious executable.

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

Campaign: 2026-05-binproto

Reasons (based on the campaign):

obfuscation
Downloads and executes a remote executable.
action-hidden-in-lib-usage
malware

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

72de81f36a15d75d302ca94b378c3e5025b6d0cb2d24360d06527130ed053ebd

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

Campaign

2026-05-binproto

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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