What does the mlc-llm-nightly-cu123 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-llm-nightly-cu123 are malicious?

The following PyPI versions of mlc-llm-nightly-cu123 are flagged malicious: 9.9.9. Treat any of these as compromised.

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

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

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

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

Malicious package

mlc-llm-nightly-cu123PyPI

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

MAL-2025-1983

Immediate action

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

pip uninstall mlc-llm-nightly-cu123

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

1 flagged

9.9.9

Indicators of compromise (SHA-256)

c09da026c5998414ae1ced8ce734499d1dc89c5ff9e021755c9a9b85e9c989b3

c0fda091f5a44ec89e930d372a725909e28f2963a619d92f79951fd45b24c0ed

99d49619be0a9e2bcedb22bd4ea489b5cb31a56558e763a78fd09a6f948f2d9e

9105764dce3e0d70ff74829ac22ac99f7e3dbf80f13e2b88200d19a63d5f5568

54f140bbeafd740974d5233688d8a679b39ff01050980ba6aea1185b8111998c

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

Campaign

RLMA-2025-012242025-01-mlc-ai-nightlyRLUA-2026-00529

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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