Which versions of morosint are malicious?

The following PyPI versions of morosint are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate morosint if I installed it?

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

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

Yes — morosint is associated with the 2025-11-morosint 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 morosint across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for morosint (version 0.0.1).

Malicious package

morosintPyPI

Advisory published Nov 12, 2025Updated Dec 3, 2025

morosint is a confirmed malicious PyPI package (MAL-2025-191795) that steals credentials and exfiltrates sensitive data (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in morosint (PyPI)

MAL-2025-191795

Immediate action

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

pip uninstall morosint

What this malware does

Importing the module starts exfiltrating Discord tokens

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

Campaign: 2025-11-morosint

Reasons (based on the campaign):

exfiltration-browser-data
exfiltration-credentials

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

0ea2b4d8a9da73a4027151f88b37267ed5b44d14b635c6e78f95172effe47129

2118ab70535d0272c108e5a454745ae83d10cd3421d5989984ab961b348367b5

Detection & response playbook

Credential / info stealer

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

Campaign

2025-11-morosint

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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