Which versions of monlith are malicious?

The following PyPI versions of monlith are flagged malicious: 912.6. Treat any of these as compromised.

How do I remediate monlith if I installed it?

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

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

Yes — monlith is associated with the RLMA-2024-11092, 2024-11-byted-dast, RLUA-2026-00534 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 monlith 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 monlith (version 912.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging monlith across your stack and pipelines.

Malicious package

monlithPyPI

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

MAL-2024-11636

Immediate action

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

pip uninstall monlith

What this malware does

A campaign of probably pentest packages flooding PYPI. Installing the package or importing the module triggers reporting basic info like hostname, path and the username to the package author. There is no other purpose of the package.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: 2024-11-byted-dast

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
typosquatting
dependency-confusion

Malicious versions

1 flagged

912.6

Indicators of compromise (SHA-256)

3a4d20ee57c01e19ff1a4ab923a28130103d8a688113848e5a31c269be9b2f57

a46558c88bcf3c1d606608726df8dfa1ccfcfc8333df06ec4b8493d852c713a0

c423d177eb7d657790fd0c5f11e9b9c477e1df45c19c5d798ba9ddec607129a9

b1491e83b8aaf84218c4716bc17c5fb183dfc7e11c179a7a3f6af9e4bf189a29

c2d8b93189578fb32246e183dd967db7fcbc956e8cf6d94a57033027d3fecb5f

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 monlith (version 912.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging monlith across your stack and pipelines.
If you installed it — respond
monlith 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 monlith 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 monlith 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. monlith on PyPI has been identified as a malicious package (version 912.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-110922024-11-byted-dastRLUA-2026-00534

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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