Which versions of moooo are malicious?

The following PyPI versions of moooo are flagged malicious: 0.1.0, 0.1.1. Treat any of these as compromised.

How do I remediate moooo if I installed it?

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

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

Is moooo part of a known attack campaign?

Yes — moooo is associated with the 2026-04-moooo 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 moooo across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for moooo (2 malicious versions).

Malicious package

mooooPyPI

Advisory published Apr 14, 2026Updated Apr 14, 2026

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

Malicious code in moooo (PyPI)

MAL-2026-2666

Immediate action

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

pip uninstall moooo

What this malware does

When used, the package silently loads code with an infostealer focused on Discord data.

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

Campaign: 2026-04-moooo

Reasons (based on the campaign):

exfiltration-generic
exfiltration-credentials
infostealer
action-hidden-in-lib-usage

Malicious versions

2 flagged

0.1.00.1.1

Indicators of compromise (SHA-256)

110e4d99f41d1dd4567651dc21115f1793e5e2eab0e12d24ea5a433cdea87f1c

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for moooo (2 malicious versions).
If you installed it — respond
moooo 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 moooo 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. moooo on PyPI has been identified as a malicious package (versions 0.1.0, 0.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-04-moooo

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database