What does the mlc-ai-nightly malware do?

Installing the package exfiltrates information about the host, including environmental variables. Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers. Campaign: 2025-01-mlc-ai-nightly 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. - The package overrides the install command in setup.py to execute malicious code during installation. - exfiltration-env-variables - dependency-confusion

Which versions of mlc-ai-nightly are malicious?

The following PyPI versions of mlc-ai-nightly are flagged malicious: 0.0.1, 9.9.9, 9.9.99. Treat any of these as compromised.

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

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

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

Yes — mlc-ai-nightly is associated with the RLMA-2025-01221, 2025-01-mlc-ai-nightly, RLUA-2026-00525, RLUA-2026-02074 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-ai-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-ai-nightly (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mlc-ai-nightly across your stack and pipelines.

Malicious package

mlc-ai-nightlyPyPI

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

MAL-2025-1980

Immediate action

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

pip uninstall mlc-ai-nightly

What this malware does

Installing the package exfiltrates information about the host, including environmental variables.

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

Campaign: 2025-01-mlc-ai-nightly

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.
The package overrides the install command in setup.py to execute malicious code during installation.
exfiltration-env-variables
dependency-confusion

Malicious versions

3 flagged

0.0.19.9.99.9.99

Indicators of compromise (SHA-256)

f2f2448a6e809b5652703a01b26ffa3f9bbb65e24c7787af16dec2b2202b1014

41a95be29005f697d7d9b8e181b8c826ef6f44d7236ccf86e7625a94730ff564

7f1b0b9f87631941501e2d04d9eab7f1cd7232f770812e3373b736f9e682dc2a

6f224462b0e3f2708463ba91241645578b5beb72fc7e1f515257a5917e1a079e

93f5f04580275ab2a5ab52810dde2cb1ab98c16a2905b5e43ae603c2dc135ee6

26a521f54774288cebbfc79b2ec113bafd07429f3b494c35536d457cebb5ba49

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

Campaign

RLMA-2025-012212025-01-mlc-ai-nightlyRLUA-2026-00525RLUA-2026-02074

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks mlc-ai-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