Which versions of morty-package are malicious?

The following PyPI versions of morty-package are flagged malicious: 0.0.0a1. Treat any of these as compromised.

How do I remediate morty-package if I installed it?

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

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

Yes — morty-package is associated with the 2026-01-pypi-package-explore 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 morty-package across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for morty-package (version 0.0.0a1).

Malicious package

morty-packagePyPI

Advisory published Jan 28, 2026Updated Jan 28, 2026

morty-package is a confirmed malicious PyPI package (MAL-2026-595) that steals credentials and exfiltrates sensitive data (malicious version 0.0.0a1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in morty-package (PyPI)

MAL-2026-595

Immediate action

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

pip uninstall morty-package

What this malware does

Package presents an extremely deep obfuscation of a code that is imported during installation. The exact behavior is unknown, but it includes loading encrypted code and interrupting debugging attempts

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

Campaign: 2026-01-pypi-package-explore

Reasons (based on the campaign):

obfuscation
other

Malicious versions

1 flagged

0.0.0a1

Indicators of compromise (SHA-256)

d87e4d2c5f3096d67a98e166e70ed6d4288c7d7554852e8d14bb60213f9a574b

Detection & response playbook

Credential / info stealer

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

Campaign

2026-01-pypi-package-explore

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks morty-package-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