Which versions of monoliht are malicious?

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

How do I remediate monoliht if I installed it?

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

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

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

Malicious package

monolihtPyPI

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

MAL-2024-11637

Immediate action

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

pip uninstall monoliht

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)

cef596a040e3ec0d5c4e1e57ed55f6b4ba45ec9499a11aeb380e9dc20b1f8ecb

9738d61d2d0302737c16e6750e7c3684334bc574a84c7ea6d0d3537c2072cb68

8c296a18c7ad4626603f55c9b78b4fe0086dff2e75e18e75fc28d5f71bf08db8

b0594d4897f61df4c3fce7993c0b5070f13b76f785a7a964bff40e65b566bfd5

e0ad0e82dca177218b12e78a9c3020cbef92db7a793565807a8d042402f26f06

15dd0429057d5ea8e413f36d3a104c43d3cd289200e2d83b48192df9bc20bb62

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 monoliht (version 912.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging monoliht across your stack and pipelines.
If you installed it — respond
monoliht 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 monoliht 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 monoliht 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. monoliht 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-11093RLUA-2025-004862024-11-byted-dastRLUA-2026-00535

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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