Microsoft’s open-source packages hit again by stealthy credential theft attacks

A fresh wave of supply-chain attacks has struck Microsoft’s open-source ecosystem, this time targeting cryptographically verified packages with advanced credential-stealing malware. The incident marks the second major breach in weeks, raising fresh concerns about the security of AI-assisted software development.

Another supply-chain breach exposes developers to credential theft

Late last week, researchers identified 73 open-source packages from Microsoft’s repositories as compromised. The malicious code was designed to activate when developers opened the packages in AI-powered coding environments. Automated security systems on GitHub swiftly flagged the packages as malicious, but the platform’s response fell short of clear warnings to users.

Rather than labeling the packages as malicious and alerting affected developers, GitHub—a Microsoft-owned platform—chose to disable the packages for violating its terms of service. The platform’s automated response left developers in the dark about potential risks to their systems, prompting Microsoft to issue a delayed acknowledgment.

Microsoft’s delayed response raises security concerns

It wasn’t until Monday—days after the initial detection—that Microsoft confirmed the breach. In an email to stakeholders, the company stated, “We have temporarily removed some repositories as we investigate potential malicious content.” The delayed acknowledgment left developers without immediate guidance on how to assess or mitigate potential compromises.

Security researchers and developers criticized the lack of transparency, noting that the incident underscores the growing risks of AI-assisted coding. The stealthy nature of the attack highlights how attackers are increasingly exploiting trusted ecosystems to deploy malware with minimal detection.

What developers should do next

Developers who used AI coding assistants with these packages should assume their systems may be compromised. Security experts recommend:

• - Scanning systems for unusual activity or unauthorized access.
• - Rotating credentials and API keys immediately.
• - Reviewing logs for signs of anomalous behavior in development environments.
• - Contacting GitHub support for further guidance on affected repositories.

The incident serves as a stark reminder of the evolving threat landscape for open-source software. As AI tools become more integrated into development workflows, the attack surface for supply-chain breaches continues to expand, demanding heightened vigilance from both developers and platform providers.