Which versions of onnxruntime-winml are malicious?

The following PyPI versions of onnxruntime-winml are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate onnxruntime-winml if I installed it?

Remove onnxruntime-winml from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed onnxruntime-winml — how do I know if it already compromised me?

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

Yes — onnxruntime-winml is associated with the 2025-09-unicore 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 onnxruntime-winml 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 onnxruntime-winml (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging onnxruntime-winml across your stack and pipelines.

Malicious package

onnxruntime-winmlPyPI

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

MAL-2025-191806

Immediate action

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

pip uninstall onnxruntime-winml

What this malware does

Package is just calling home and there is no other purpose

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: 2025-09-unicore

Reasons (based on the campaign):

other

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

8178646ec255c40e5ba22f0b484af0909c4ba3c42f025a98dd22956cadecec91

5566aa4ecc644b36e90902092563c05e1852d751381539398f2307ae1fbefae6

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for onnxruntime-winml (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging onnxruntime-winml across your stack and pipelines.
If you installed it — respond
Remove onnxruntime-winml from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If onnxruntime-winml 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 onnxruntime-winml 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. onnxruntime-winml on PyPI has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2025-09-unicore

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks onnxruntime-winml-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring