Which versions of ort-moe are malicious?

The following PyPI versions of ort-moe are flagged malicious: 9.0.0. Treat any of these as compromised.

How do I remediate ort-moe if I installed it?

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

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

Yes — ort-moe is associated with the 2026-04-promptflow-runtime 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 ort-moe 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 ort-moe (version 9.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ort-moe across your stack and pipelines.

Malicious package

ort-moePyPI

Malicious code in ort-moe (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-3034

Immediate action

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

pip uninstall ort-moe

What this malware does

During import, package collects basic information about the system, performs deep fingerprinting, and reports the data to the remote target. The package description attempts to build a false impression that it's an official package. The name refers to either ONNYX runtime, or the Pytorch package never released to the PyPI: https://github.com/pytorch/ort/blob/89466e524b0abe3a134418a50beeb405e287cedc/ort_moe/setup.py#L11

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

Campaign: 2026-04-promptflow-runtime

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.
dependency-confusion
impersonation
The package contains code to detect if it is running in a sandbox environment.

Malicious versions

1 flagged

9.0.0

Indicators of compromise (SHA-256)

b07b0d9d87f411b1c481f50084190fdde34edfeb1c9b10368a23abba0ccbcbdc

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

Campaign

2026-04-promptflow-runtime

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks ort-moe-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