For the 2nd time in weeks, Microsoft packages laced with credential stealer

· Source: AI - Ars Technica · Field: Technology & Digital — Cybersecurity & Data Privacy, Software Development & Engineering, Artificial Intelligence & Machine Learning · Depth: Advanced, short

Summary

Dozens of cryptographically verified open-source packages from Microsoft were compromised late last week, marking the second such supply-chain attack in as many months. A total of 73 packages were flagged as malicious on GitHub, containing advanced credential-stealing code. This malware, tracked as Miasma and linked to TeamPCP, is a clone of the Mini Shai-Hulud toolkit. It executes a 28 KB payload designed to harvest credentials from AWS, Azure, GCP, Kubernetes, password managers, and over 90 developer tool configurations, then spreads laterally through cloud infrastructures. The attack exploits the modern engineering ecosystem's trust model by using compromised developer credentials to publish malicious builds with valid SLSA provenance, making them appear legitimate. Miasma generates uniquely encrypted payloads, rendering traditional hash-based detection ineffective. The credential-stealing function activates when packages are opened in AI coding agents like Claude Code, Gemini CLI, Cursor, and VS Code.

Key takeaway

For MLOps Engineers or Security Engineers managing software supply chains, if your team used any of the 73 compromised Microsoft packages, you must immediately assume system compromise. Thoroughly investigate all developer machines and CI/CD runners that interacted with these packages, especially if opened in AI coding agents like Cursor or Gemini CLI. Prioritize rotating all potentially exposed credentials, as the attack bypasses traditional detection and exploits trust, making remediation complex.

Key insights

Supply chain attacks exploit trust models, not vulnerabilities, using compromised credentials to publish cryptographically verified malicious packages.

Principles

Method

Attackers compromise developer credentials to request legitimate GitHub OIDC tokens, publish malicious builds with valid SLSA provenance, and trigger credential theft via AI coding agents.

In practice

Topics

Best for: CTO, VP of Engineering/Data, Director of AI/ML, AI Security Engineer, Security Engineer, MLOps Engineer

Related on AIssential

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by AI - Ars Technica.