Security

@antv npm Attack Hits CI/CD Secrets and Tokens

3 min read

Summary

Microsoft has disclosed an active supply chain attack involving compromised @antv npm packages that used malicious preinstall scripts to steal credentials from GitHub Actions and other CI/CD environments. The campaign matters because it spread through popular downstream dependencies, putting developer pipelines, cloud secrets, and software supply chains at risk.

Need help with Security?Talk to an Expert

Introduction

Microsoft has uncovered a significant npm supply chain attack affecting the @antv package ecosystem. Because these packages are widely used directly and transitively, the compromise can reach far beyond a single project and into CI/CD pipelines, cloud environments, and downstream software builds.

For IT and security teams, this is a reminder that package ecosystem compromises can quickly become credential theft and cloud access incidents.

What happened

A threat actor compromised an @antv maintainer account and published malicious package versions. The malicious code executed during npm install through a preinstall hook and targeted GitHub Actions runners on Linux.

Key technical findings

  • Malicious @antv packages propagated through dependency chains into widely used libraries such as echarts-for-react
  • The payload was heavily obfuscated and designed to evade analysis
  • It executed silently during package installation
  • It focused on CI/CD environments, especially GitHub Actions
  • It installed Bun if needed and launched a second-stage payload

Credentials and secrets targeted

Microsoft says the malware attempted to steal credentials from multiple platforms, including:

  • GitHub tokens and repository secrets
  • AWS credentials and Secrets Manager data
  • HashiCorp Vault tokens
  • npm tokens
  • Kubernetes service account secrets
  • 1Password CLI data

The payload also scraped GitHub Actions runner process memory to extract secrets directly, potentially bypassing normal secret masking protections.

Why this matters for administrators

This is more than a developer issue. If affected packages were installed in enterprise build systems, attackers may have gained access to:

  • Source code repositories
  • CI/CD secrets and pipelines
  • Cloud workloads and infrastructure
  • Package publishing credentials

Microsoft also notes the malware attempted privilege escalation, dual-channel exfiltration, and even SLSA provenance forgery, which undermines trust in software supply chain attestations.

What GitHub did

GitHub responded by:

  • Removing 640 malicious packages
  • Invalidating 61,274 npm granular access tokens with write permissions and 2FA bypass
  • Publishing advisories and issuing Dependabot and npm audit alerts

Administrators should act quickly:

  • Review dependency trees for direct or transitive use of affected @antv packages
  • Identify systems that installed or built these packages during the exposure window
  • Rotate GitHub, npm, AWS, Vault, Kubernetes, and other potentially exposed credentials
  • Audit GitHub Actions workflows, runner logs, and repository changes for suspicious activity
  • Check for unauthorized repos, commits, secrets access, or package publication events
  • Pin known-good package versions and strengthen dependency controls

Bottom line

The @antv compromise shows how a single npm maintainer account takeover can cascade into widespread CI/CD credential theft. Security and DevOps teams should treat any exposure as a potential pipeline and cloud credential incident, not just a package hygiene issue.

Need help with Security?

Our experts can help you implement and optimize your Microsoft solutions.

Talk to an Expert

Stay updated on Microsoft technologies

npmsupply chain securityGitHub ActionsCI/CDcredential theft

Related Posts

Security

Microsoft Sentinel Named a 2026 SIEM Leader

Microsoft has been named a Leader in the 2026 Gartner Magic Quadrant for SIEM, highlighting the continued momentum behind Microsoft Sentinel. The announcement also underscores Microsoft's push toward integrated, AI-powered security operations through deep Sentinel integration with the new Integrated Security Operations Center in Microsoft Defender.

Security

Microsoft Perception GA: Agentic Security at Ignite

Microsoft has made Microsoft Perception generally available, introducing an agentic security platform that coordinates red, blue, and green team agents through automated playbooks. Announced at Ignite 2026, the update also expands Defender and Sentinel capabilities to help security teams detect, investigate, and remediate AI-speed threats while keeping administrators in control.

Security

Device Code Phishing Risks for AI Coding Agents

Microsoft warns that device code phishing can be used against AI coding agents such as GitHub Copilot CLI, not just user mailboxes or cloud apps. In a controlled lab, a single approved device code sign-in could enable remote session steering, memory poisoning, synced session exposure, and private repository access depending on account permissions and enabled features.

Security

Microsoft 365 Outage Phishing Campaign Targets Users

Microsoft Threat Intelligence reported a high-volume phishing campaign that impersonates Microsoft 365 service-health notifications to trick users into clicking malicious links. The campaign matters because it uses outage-themed urgency and recipient-specific tracking to target multiple industries, increasing the risk of credential theft and follow-on account compromise.

Security

SCKit ScreenConnect Attack: MSPs Must Hunt Now

Microsoft Threat Intelligence confirmed a campaign abusing ConnectWise ScreenConnect to deploy unauthorized remote-access clients and the SCKit worm on MSP-managed endpoints. The activity can also target technician sessions, making this a high-priority incident for defenders because removing a rogue client alone does not eliminate persistence or invalidate exposed sessions.

Security

AI Agent Supply Chain Attacks Target Coding Tools

Microsoft Security researchers detailed two post-training supply chain attack paths that can backdoor coding and terminal agents: dataset poisoning and model poisoning. The findings matter because compromised agents can misuse tools, execute commands, and access sensitive environments even when prompts appear benign, reinforcing the need for stronger controls around training data, model provenance, and tool permissions.