Microsoft takes GitHub repos private after PyPI hijack; Wiz traces the publish to a compromised release-pipeline credential
Microsoft made some GitHub repositories private, including agent-framework and onnxruntime, while it investigates the Nov. 17 hijack of its agent-framework package — and Wiz says the attacker appears to have used a compromised certificate and private key for Microsoft's internal release pipeline.
📊 Scorecard: our Bearish call on $MSFT is scored from $484.52, the last close before it ran. Its first result comes after the next close.

The News
Microsoft has taken the unusual step of making some of its public GitHub repositories private while it investigates the Nov. 17 hijack of its agent-framework package on PyPI, the main download site for Python software packages. The affected repositories include microsoft/agent-framework and microsoft/onnxruntime. A Microsoft spokesperson said: "We have made some repositories private while we investigate malicious content. Our priority is to protect customers and the broader ecosystem." The onnxruntime repositories have returned 404 errors — the web's way of saying a page is not found — since the evening of Nov. 17. The PyPI, NuGet and npm packages themselves are unaffected.
Separately, Wiz, a cloud security company, published an updated analysis on Nov. 18 with a theory about how the hijack happened. Wiz says the attacker appears to have compromised a client certificate and private key for Microsoft's Engineering System Release Pipeline, known as ESRP — the internal service Microsoft uses to sign and publish packages. A certificate and private key are the digital credentials that prove a publisher is who it claims to be; whoever holds them can publish software that looks officially signed. Wiz says a first publish attempt from Amazon's AWS cloud was rejected by ESRP's IP filtering, which only allows publishing from approved network addresses, but a second attempt from Microsoft-owned IP space succeeded. How the credentials were obtained is not yet known.
Wiz also gave a rare window into how far the malicious package spread. It could read 50 webhook requests — automatic notifications sent to the attacker's exfiltration endpoint, the server where stolen data was collected — because the free tier of the service the attacker used caps at 100 requests. Four came from the attacker's own machines, 29 from sandboxes and scanners — isolated test environments used by security researchers — and 17 were victim-data cases representing three distinct instances of victim data actually delivered. No installation counts for the two malicious versions, 1.26.1 and 1.26.2, have been published. This post covers Microsoft's Nov. 20 response and Wiz's updated findings; the Nov. 20 post covered the hijack itself.
The scariest part is not the hijacked package — it is that the attacker's key may have come from the pipeline that signs Microsoft's own software.
Why It Matters
The ESRP theory, if correct, is more worrying than a simple package hijack. A hijacked package is a single bad download; a compromised signing pipeline is a broken trust mechanism. Developers install packages from PyPI because they trust that a package signed by Microsoft actually came from Microsoft. If an attacker can publish through Microsoft's own release pipeline, that trust is undermined at the source, and every package that pipeline has signed becomes a question mark rather than a certainty.
The evidence is also genuinely contested, which is why this story is not a simple one. Wiz's ESRP compromise assessment is contradicted in part by JFrog's earlier evidence that the malicious package was a repackaging job — a rebuilt copy of the real package with malicious code added — rather than a pipeline-signed release. Both accounts are reported here without reconciling them, because the truth is not yet established. Microsoft has not published a root cause, so neither theory is confirmed by the company itself.
The small number of confirmed victim cases is the one reassuring detail. Three distinct instances of victim data actually delivered is a long way from a mass compromise, and the 29 sandbox and scanner requests suggest the security community found the malicious package quickly and studied it in isolated environments. But without installation counts for the two malicious versions, nobody can say how many developers actually installed them before they were pulled.
Analyst's Take
Our call is Bearish. Microsoft taking its own repositories private is a visible sign of how seriously it treats this incident, and the Wiz analysis raises a question — whether the company's own signing pipeline was compromised — that Microsoft has not yet answered. For a company whose developer tools are used across the industry, a supply-chain incident like this is a trust problem, not just a technical one.
What to watch next is Microsoft's root-cause statement, whenever it comes. If it confirms the ESRP compromise, expect a broader review of how release-pipeline credentials are protected, and possibly a rotation of signing keys that could affect other Microsoft packages. If it confirms JFrog's repackaging theory instead, the fix is narrower — but the company will still have to explain how a repackaged version reached PyPI under its name.
For developers, the practical lesson is already clear: pin package versions, check what you install, and treat even official-looking packages with a healthy dose of suspicion when a hijack is in the news. Reader poll: Do you check package versions before installing — yes or no? Vote: Always, Sometimes, Never.
Are you bullish or bearish on this story?
By The Numbers
FAQ
What is PyPI?
PyPI, the Python Package Index, is the main download site for Python software packages. When a developer types a command to install a library, it usually comes from PyPI. Because so much software depends on it, a malicious package there can spread quickly to thousands of projects.
What is a client certificate and private key?
A client certificate and private key are digital credentials that prove an identity — in this case, that a publisher is authorised to release software through Microsoft's pipeline. Whoever holds the private key can sign and publish software that looks like it officially came from Microsoft. Losing control of one is like losing the master key to a building.
What is a release pipeline?
A release pipeline is the automated system a company uses to build, test, sign and publish its software. Microsoft's Engineering System Release Pipeline, or ESRP, is the internal service that signs and publishes its packages. If an attacker gets into the pipeline, they can potentially publish malicious software under the company's trusted name.
What is a webhook?
A webhook is an automatic notification one system sends to another when something happens — for example, a server telling an app that a download just occurred. In this case, the attacker's data-collection server received webhook notifications when the malicious package was installed, which is how Wiz could count how many victims there were.
👁
Source: The Hacker News