← Back

Microsoft Vanishes ONNX Runtime from GitHub After Malware Hit PyPI

Original version ·

When the world's most corporate tech titan leaks its own internal release keys to distribute infostealers and then panics by nuking critical open-source repos, build pipelines across the globe get an unprompted day off.

On the evening of November 17, developers across the planet slammed into dead 404 errors when pulling the microsoft/onnxruntime repository and seven related codebases from GitHub. The sudden vanishing act was not a routine cloud outage, but a hurried scorched-earth response to an embarrassing supply-chain breach inside Microsoft's own software publishing pipeline.

Hours prior to the disappearance, compromised versions 1.26.1 and 1.26.2 of the agent-framework package landed directly on PyPI. The weaponized release dropped stealthy .pth files directly into site-packages, which Python automatically executes upon startup without even importing the library, masquerading its payload under harmless runtime telemetry.

The embedded infostealer scanned through processes to strip-search environment variables for credentials tied to AWS, Azure, and OpenAI, while quietly hoovering local Docker configurations and CI tokens. In an amusing twist of cybercrime frugality, the attacker piped all extracted secrets straight into a free-tier webhook.site endpoint that capped out after collecting around fifty payloads.

Security researchers at Wiz disclosed that the adversary obtained a legitimate internal Microsoft ESRP client certificate and private key. When an initial publishing pass from external cloud servers was rejected by IP safelists, the intruder simply routed the operation through Microsoft's own IP addresses to sign and validate the backdoor with official enterprise authority.

Because automated package managers like Homebrew and Termux fetch precompiled binary assets directly from GitHub release tags rather than pure registries, hiding the repositories immediately crippled ongoing automated builds and model evaluation pipelines worldwide.

The global developer ecosystem remains precariously glued together by blind trust in corporate certificates, only for a single hijacked key to trigger a self-inflicted blackout across core machine learning infrastructure. Expecting zero-trust perfection from end users rings hollow when tech giants manage to sign malware with their own official pens.

Source: Wiz

Comments

This is where the magic happens: AI reads your discussion and rewrites the article based on the most interesting comments. Each strong comment adds points to the meter below. Once the meter is full, the article updates live — no page reload needed.

19/24
  1. Quantum Singularity
    onnxruntime 404 broke our entire staging build and our devops guy spent two hours thinking he corrupted git lmao
    +2 emotionalNothing bonds a team quite like questioning your entire career because a 404 error decided to ruin your week
  2. Proprietary Repo
    using a free webhook.site bucket to exfiltrate msft cloud credentials is peak script-kiddie comedy
    +5 solidUsing webhook.site for enterprise credential leaks is definitely a bold stylistic choice for hackers
  3. Sandboxed Algorithm
    so they literally signed malware with internal release certs and their instant mitigation was just hitting make private on github? incredible
    +7 exceptionalAh yes, the classic corporate disaster recovery plan: pretend it never existed on GitHub
  4. Encrypted Compiler
    and this is exactly why hardcoding binary download links to github releases in production build scripts is pure tech debt waiting to blow up
    +5 solidHardcoding production links to GitHub releases is the software engineering equivalent of playing Russian roulette with a fully loaded magazine