Which versions of mlc-llm-nightly are malicious?

The following PyPI versions of mlc-llm-nightly are flagged malicious: 99.99.99, 99.99.100, 99.99.101, 99.99.102, 99.99.103, 99.99.105. Treat any of these as compromised.

How do I remediate mlc-llm-nightly if I installed it?

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

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

Yes — mlc-llm-nightly is associated with the RLMA-2024-08523, GENERIC-questionable-pentest, RLUA-2026-00528 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 mlc-llm-nightly 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 mlc-llm-nightly (6 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mlc-llm-nightly across your stack and pipelines.

Malicious package

mlc-llm-nightlyPyPI

Malicious code in mlc-llm-nightly (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-10046

Immediate action

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

pip uninstall mlc-llm-nightly

What this malware does

Generic campaign for all (likely) research / pentests, where the amount or art of collected data raises questions about the privacy, security and ethical side.

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

Campaign: GENERIC-questionable-pentest

Reasons (based on the campaign):

exfiltration-env-variables
exfiltration-generic
The package overrides the install command in setup.py to execute malicious code during installation.
typosquatting

Malicious versions

6 flagged

99.99.9999.99.10099.99.10199.99.10299.99.10399.99.105

Indicators of compromise (SHA-256)

b9afd964611a469cd6fe62f9684544eb34337fedd29bc97df5110e0f7829fd2b

f82afa0378a3a21d3f12574493e94e921aec9113684cc1654a533ce1f7aa716f

bdf6d47b319cb60e32a6f2942beaa54bfe6ccc01bb72a8337f062746d49ace38

0bb339dee4aefeb8ea2f6f6f6e92413a44fd5f90aeb7d585dd022dc80842ac7b

d5c158c4a82030d84bdd96e2a21a385c3a44e3df52e5db3417eb42a33a33cb4f

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

Campaign

RLMA-2024-08523GENERIC-questionable-pentestRLUA-2026-00528

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks mlc-llm-nightly-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