Hackers injected credential-stealing malware into Microsoft’s open supply GitHub repositories, focusing on builders utilizing AI coding instruments and exposing the rising risk of open-source supply-chain assaults.
Hackers have compromised a number of Microsoft open-source initiatives hosted on GitHub, injecting malicious code designed to steal passwords and delicate credentials from builders utilizing AI coding instruments.
The assault focused builders working with environments equivalent to Claude Code, Gemini CLI and VS Code. Researchers warned that credentials might be harvested when compromised instruments had been opened inside these AI-assisted growth platforms.
In response, Microsoft disabled entry to dozens of affected GitHub repositories whereas investigating the incident. In accordance with GitHub notices, a minimum of 70 repositories had been taken offline, whereas Ars Technica reported that 73 Microsoft packages had been flagged as malicious. A number of repositories have since been restored, although others stay unavailable pending additional evaluate.
Most of the affected repositories had been linked to Microsoft Azure, AI developer tooling and open-source sources generally utilized in AI workflows. Safety agency Cloudsmith and malware-tracking group OpenSourceMalware had been among the many first to determine and flag the compromise.
Microsoft spokesperson Ben Hope mentioned the corporate had “briefly eliminated some repositories as we investigated potential malicious content material.” He added that “a few of these repos have been restored after evaluate, whereas others might stay offline whereas work continues.”
The incident highlights the rising danger of software program supply-chain assaults, through which trusted software program sources are compromised to contaminate downstream customers. Researchers famous that that is Microsoft’s second identified open-source repository compromise in latest weeks, following an earlier breach involving the Sturdy Process challenge, which OpenSourceMalware described as a potential “re-compromise.”
Microsoft has not disclosed what number of customers had been affected or what number of builders downloaded the compromised code.