What does the bloxypy malware do?

Attempting to use the module starts obfuscated code containing an infostealer Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers. Campaign: 2025-09-bloxypy Reasons (based on the campaign): - infostealer - obfuscation - action-hidden-in-lib-usage - infostealer:kiwi - exfiltration-browser-data This malicious package executes code obfuscated using Base64 encoding. It is designed to mimic the ro-py package.

Which versions of bloxypy are malicious?

The following PyPI versions of bloxypy are flagged malicious: 0.1.9. Treat any of these as compromised.

How do I remediate bloxypy if I installed it?

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

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

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

Malicious package

bloxypyPyPI

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

MAL-2025-47572

Immediate action

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

pip uninstall bloxypy

What this malware does

Attempting to use the module starts obfuscated code containing an infostealer

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

Campaign: 2025-09-bloxypy

Reasons (based on the campaign):

infostealer
obfuscation
action-hidden-in-lib-usage
infostealer:kiwi
exfiltration-browser-data

This malicious package executes code obfuscated using Base64 encoding. It is designed to mimic the ro-py package.

Malicious versions

1 flagged

0.1.9

Indicators of compromise (SHA-256)

981253c2b6b99e04aff2ddfde86c215b40d6da1340c24fa8f2e2d0f7f797d82e

88482bd19a6d9cf3e08a5112b6b49b78870af1793b959d85f7bb2ee174def5bc

ca1bb0aab09d6ef59ee1ff8485c8c2a6b565c1311246ed61d63c9757bd44ecdc

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

Campaign

2025-09-bloxypy

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
Oracle using Macaron · finder

Detect & block this

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