Which versions of codeshouhu are malicious?

The following PyPI versions of codeshouhu are flagged malicious: 0.1.3, 0.1.4, 0.1.5, 0.1.6, 0.1.7, 0.1.8, 0.1.9, 0.2.0, 0.2.1, 0.2.2. Treat any of these as compromised.

How do I remediate codeshouhu if I installed it?

Remove codeshouhu from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed codeshouhu — how do I know if it already compromised me?

If codeshouhu 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.

How do I find codeshouhu across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for codeshouhu (10 malicious versions).

Malicious package

codeshouhuPyPI

Advisory published Mar 16, 2026Updated Mar 17, 2026

codeshouhu is a confirmed malicious PyPI package (MAL-2026-1488) that executes malicious code on install (malicious versions 0.1.3, 0.1.4, 0.1.5…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in codeshouhu (PyPI)

MAL-2026-1488

Immediate action

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

pip uninstall codeshouhu

What this malware does

This package runs a malicious payload when it is imported.

Malicious versions

10 flagged

0.1.30.1.40.1.50.1.60.1.70.1.80.1.90.2.00.2.10.2.2

Indicators of compromise (SHA-256)

4d37163d3341d79548bd0fd94d62539579ed5f7ba2e48c1810b8d4e20c964c1c

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for codeshouhu (10 malicious versions).
If you installed it — respond
Remove codeshouhu from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If codeshouhu 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

No. codeshouhu on PyPI has been identified as a malicious package (versions 0.1.3, 0.1.4, 0.1.5, 0.1.6, 0.1.7, 0.1.8, 0.1.9, 0.2.0, and 2 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Oracle using Macaron · finder

Detect & block this

O3 blocks codeshouhu-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database