/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

Microsoft disabled 70+ of its repos on GitHub, including Azure-related tools like azure-functions-host, after hackers added credential-stealing malware to them

Microsoft has cut off access to dozens of its open source projects hosted on GitHub as it investigates how hackers apparently breached …

TechCrunch Zack Whittaker

Context & Ripple Effects

This incident follows earlier reports of Microsoft-linked GitHub exposure, including an AI research repository that exposed sensitive data and a broader finding that major vendors’ open-source projects leaked GitHub authentication tokens through Actions. It also sits alongside reporting that GitHub infrastructure is routinely abused to distribute malware.

The affected projects include Azure-related tooling, making repository integrity an operational issue for developers and organizations that consume Microsoft-maintained code. The reported credential theft aimed at users of AI coding agents adds a new exposure point beyond traditional source-code downloads.

First-order effects

  • Microsoft has taken affected projects offline while it investigates and removes malicious changes, interrupting normal access to code, releases, and updates for users of those repositories.
  • Developers that recently pulled code or automation from the affected repositories must treat their environments and credentials as potentially exposed and validate what they consumed.

Second-order effects

  • Teams relying on Microsoft-hosted open-source dependencies may pause upgrades or pin to verified versions, increasing the immediate burden of provenance checks and internal code review.
  • The event raises the cost of maintaining trusted publishing pipelines on GitHub for major vendors, particularly where repository access and automation can affect downstream developer credentials.

Third-order effects

  • If compromises of trusted project repositories continue to target AI-assisted development workflows, software supply-chain security will increasingly have to cover agent credentials, repository integrity, and automated dependency consumption together.
  • Repeated exposure incidents involving large vendors could accelerate a shift from implicit trust in official repositories toward stronger verification, signed releases, and more restrictive maintainer controls; the corpus does not establish which controls Microsoft will adopt.

The trend: This is part of the broader shift from protecting source code alone to securing the full developer-tooling supply chain, including AI-agent access and credentials.

Discussion

  • @malwrhunterteam @malwrhunterteam on x
    Totally legit “DocuSign” release in a GitHub (Microsoft owned service) repo: https://github[.]com/lonergigs-code/ DocuSign/releases/ -> DocusignSetup.exe - “Paula Foster” (Microsoft given cert) signed sample... -> bbytati25iy2.anondns[.]net -> 84.54.33[.]250 🤷‍♂️ [image]
  • @tyleraking.com Tyler King on bluesky
    GitHub keeps getting inundated by malicious credential-stealing Microsoft packages.  And then not really being honest with users about it.
  • @zackwhittaker.com Zack Whittaker on bluesky
    Microsoft told me it's notified a “small number of customers” who may have pulled password-stealing malware from several of its GitHub repos, while many affected repos are still down.  —  I've asked for a specific number.  Even a “small number” of Microsoft's many, many customers…
  • @jasonkoebler Jason Koebler on bluesky
    Microsoft shut down a bunch of its own code repositories after hackers pushed malware that would steal credentials from Claude Code or Gemini.  Really wild:  —  www.404media.co/microsoft-ha...
  • r/cybersecurity r on reddit
    For the 2nd time in weeks, Microsoft packages laced with credential stealer
  • r/pwnhub r on reddit
    For the 2nd time in weeks, Microsoft packages laced with credential stealer |  73 packages run self-replicating stealer as soon as they're opened by an AI agent.
  • Paul McCarty Paul McCarty on linkedin
    Looks like Microsoft has been compromised again!  All signs point to the Miasma worm (not confirmed), as evidenced by a probable reinfection of the durabletask repo/maintainer on GitHub. …
  • @josephcox Joseph Cox on bluesky
    New: Microsoft was compromised to deliver malware to users of AI coding agents like Claude and Gemini.  In response, Microsoft took the highly unusual step of shutting down dozens and dozens of its own GitHub repos.  The malware would steal login credentials from users  —  www.40…
  • r/AIDangers r on reddit
    Microsoft Hacked to Deliver Malware to Claude and Gemini Users
  • r/GeminiAI r on reddit
    Microsoft Hacked to Deliver Malware to Claude and Gemini Users
  • r/InterstellarKinetics r on reddit
    EXPOSED: For The Second Time In Weeks, Dozens Of Cryptographically Verified Microsoft Packages Were Secretly Poisoned With A Self-Replicating …
  • @nixCraft@mastodon.social @nixCraft@mastodon.social on mastodon
    Microsoft's open source tools were hacked to steal passwords of AI developers.  Microsoft has suspended access to dozens of its open source GitHub projects after hackers breached them to inject password-stealing malware.  The affected projects primarily include tools for Azure cl…
  • @kingdomfantasy6 @kingdomfantasy6 on bluesky
    Azure and Durable Task are the big ones.  I've seen red hat mentioned a couple places, but this source doesn't show it.  —  However, it does provide some steps if you or your org has pulled directly from any repos before the hack was discovered.