<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/a-single-pull-request-could-have-handed-attackers-the-keys-to-microsoft-s-software-supply-chain-nqepmavgc" -->

---
title: A single pull request could have handed attackers the...
description: A now-patched zero-click vulnerability in WinGet's moderation tooling could have let attackers steal a Microsoft moderator's full GitHub access token through a...
canonical: https://daily.dev/posts/a-single-pull-request-could-have-handed-attackers-the-keys-to-microsoft-s-software-supply-chain-nqepmavgc
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: A single pull request could have handed attackers the keys to Microsoft’s software supply chain | daily.dev
og:description: A now-patched zero-click vulnerability in WinGet's moderation tooling could have let attackers steal a Microsoft moderator's full GitHub access token through a...
og:url: https://daily.dev/posts/a-single-pull-request-could-have-handed-attackers-the-keys-to-microsoft-s-software-supply-chain-nqepmavgc
og:image: https://api.daily.dev/og/posts/NqEpMAVgc.png
og:image:alt: A single pull request could have handed attackers the keys to Microsoft’s software supply chain
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# A single pull request could have handed attackers the keys to Microsoft’s software supply chain

**[CSO Online](https://daily.dev/sources/csoonline)** · 6 min read · 0 upvotes · 0 comments

## Summary

A now-patched zero-click vulnerability in WinGet's moderation tooling could have let attackers steal a Microsoft moderator's full GitHub access token through a single pull request. Cycode found that a PowerShell triage helper attached the moderator's GitHub Personal Access Token to any outgoing HTTP request without checking who owned the destination. An attacker could point an installer URL at their own server, trigger a validation error, and have the token 'casually' handed over via a HEAD request. With it, an attacker could push backdoored installers to 14,000 exposed packages and access any other Microsoft repo the moderator could touch. Microsoft patched it by scoping token attachment to authorized GitHub endpoints like api.github.com.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://www.csoonline.com/article/4251117/a-single-pull-request-could-have-handed-attackers-the-keys-to-microsofts-software-supply-chain.html>

## Questions this post answers

### How could a pull request leak a Microsoft moderator's GitHub token in the WinGet repo?

A PowerShell triage helper used by WinGet moderators attached the moderator's GitHub Personal Access Token to any outgoing HTTP request without verifying the destination. An attacker could submit a pull request pointing an InstallerURL at their own server, trigger a validation error, and have the moderator's script send an authenticated HEAD request back to that server, exposing the token in the attacker's logs with no clicks or phishing needed.

_Teams auditing internal bots for credential leaks can track fixes like this one on daily.dev._

### What is the real scope of a leaked GitHub Personal Access Token (PAT) compared to a repository-scoped credential?

A leaked classic GitHub PAT is a full identity credential, not just a repository-scoped one, meaning an attacker can do anything the token's owner could do on GitHub. In the WinGet case this would have allowed pushing malicious manifests, approving pull requests, backdooring 14,000 exposed packages, and accessing or modifying every other repository and GitHub Actions workflow the moderator could reach.

_Developers weighing classic PATs against scoped, short-lived tokens can follow this trade-off discussion on daily.dev._

### How did Microsoft fix the WinGet PowerShell token-leak vulnerability?

Microsoft scoped the authentication mechanism so that a user's token is only attached when the request host is an authorized GitHub endpoint, such as api.github.com, github.com, or raw.githubusercontent.com. Notably, Microsoft's C# version of the same tool, located in the same directory, never had this flaw and already used safer authentication, highlighting that implementation details within one codebase can diverge in security posture.

_Engineers hardening internal automation against token leaks can follow patch details like this on daily.dev._

## Similar posts on daily.dev

- [VS Code zero-day lets hackers steal GitHub tokens in one click](https://daily.dev/posts/vs-code-zero-day-lets-hackers-steal-github-tokens-in-one-click-dg7cfn1yn) · BleepingComputer · 0 upvotes · 1 comments
- [GitHub.dev flaw lets attackers steal OAuth tokens in one click](https://daily.dev/posts/github-dev-flaw-lets-attackers-steal-oauth-tokens-in-one-click-tounneovz) · The Next Web · 0 upvotes · 0 comments
- [Hole in GitHub’s browser-based VSCode editor could lead to stolen token](https://daily.dev/posts/hole-in-github-s-browser-based-vscode-editor-could-lead-to-stolen-token-mfj7z99ko) · InfoWorld · 0 upvotes · 0 comments
- [1-Click GitHub Token Stealing via a VSCode Bug](https://daily.dev/posts/1-click-github-token-stealing-via-a-vscode-bug-bjvyhct2p) · Lobsters · 0 upvotes · 0 comments

---

Tags: [#security](https://daily.dev/tags/security), [#microsoft](https://daily.dev/tags/microsoft), [#github](https://daily.dev/tags/github), [#authentication](https://daily.dev/tags/authentication)

[View this post on daily.dev](https://daily.dev/posts/a-single-pull-request-could-have-handed-attackers-the-keys-to-microsoft-s-software-supply-chain-nqepmavgc)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"A single pull request could have handed attackers the keys to Microsoft’s software supply chain","url":"https://daily.dev/posts/a-single-pull-request-could-have-handed-attackers-the-keys-to-microsoft-s-software-supply-chain-nqepmavgc","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/a-single-pull-request-could-have-handed-attackers-the-keys-to-microsoft-s-software-supply-chain-nqepmavgc"},"datePublished":"2026-11-20T03:12:50.696Z","dateModified":"2026-11-20T03:33:29.285Z","description":"A now-patched zero-click vulnerability in WinGet's moderation tooling could have let attackers steal a Microsoft moderator's full GitHub access token through a...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/4f9147e3e2094663f8e2d6dd504b5500?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/4f9147e3e2094663f8e2d6dd504b5500?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"CSO Online","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"CSO Online","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/98667e4b5cac46cf9c470819c6cf71cd","url":"https://daily.dev/sources/csoonline"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/a-single-pull-request-could-have-handed-attackers-the-keys-to-microsoft-s-software-supply-chain-nqepmavgc","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"security,microsoft,github,authentication","timeRequired":"PT6M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"CSO Online","item":"https://daily.dev/sources/csoonline"},{"@type":"ListItem","position":3,"name":"A single pull request could have handed attackers the keys to Microsoft’s software supply chain"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/a-single-pull-request-could-have-handed-attackers-the-keys-to-microsoft-s-software-supply-chain-nqepmavgc#faq","mainEntity":[{"@type":"Question","name":"How could a pull request leak a Microsoft moderator's GitHub token in the WinGet repo?","acceptedAnswer":{"@type":"Answer","text":"A PowerShell triage helper used by WinGet moderators attached the moderator's GitHub Personal Access Token to any outgoing HTTP request without verifying the destination. An attacker could submit a pull request pointing an InstallerURL at their own server, trigger a validation error, and have the moderator's script send an authenticated HEAD request back to that server, exposing the token in the attacker's logs with no clicks or phishing needed. Teams auditing internal bots for credential leaks can track fixes like this one on daily.dev."}},{"@type":"Question","name":"What is the real scope of a leaked GitHub Personal Access Token (PAT) compared to a repository-scoped credential?","acceptedAnswer":{"@type":"Answer","text":"A leaked classic GitHub PAT is a full identity credential, not just a repository-scoped one, meaning an attacker can do anything the token's owner could do on GitHub. In the WinGet case this would have allowed pushing malicious manifests, approving pull requests, backdooring 14,000 exposed packages, and accessing or modifying every other repository and GitHub Actions workflow the moderator could reach. Developers weighing classic PATs against scoped, short-lived tokens can follow this trade-off discussion on daily.dev."}},{"@type":"Question","name":"How did Microsoft fix the WinGet PowerShell token-leak vulnerability?","acceptedAnswer":{"@type":"Answer","text":"Microsoft scoped the authentication mechanism so that a user's token is only attached when the request host is an authorized GitHub endpoint, such as api.github.com, github.com, or raw.githubusercontent.com. Notably, Microsoft's C# version of the same tool, located in the same directory, never had this flaw and already used safer authentication, highlighting that implementation details within one codebase can diverge in security posture. Engineers hardening internal automation against token leaks can follow patch details like this on daily.dev."}}]}
```

