Mini Shai-Hulud in npm: what CI/CD secrets abuse means for teams

TL;DR: The Mini Shai-Hulud npm worm is compromising AntV ecosystem packages, stealing CI/CD secrets from GitHub Actions runners, and using stolen tokens to create thousands of public repositories as exfiltration dead-drops, according to StepSecurity. The pattern shows that secrets exposure, runner memory access, and post-exfiltration token abuse now form a single supply chain kill chain, not separate problems.

NHIMG editorial — based on content published by StepSecurity covering the Mini Shai-Hulud npm supply chain attack: Shai-Hulud: Here We Go Again. Mass npm Supply Chain Attack Hits the AntV Ecosystem

By the numbers:

• 64% of valid secrets leaked in 2022 are still valid and exploitable today, proving that detection alone is not enough without automated revocation.

Questions worth separating out

Q: What breaks when a malicious npm package can read CI/CD runner memory?

A: When a malicious package can read runner memory, secret masking no longer protects credentials because plaintext tokens are already present in process space.

Q: Why do CI/CD secrets create such a large blast radius in supply chain attacks?

A: CI/CD secrets are often shared across build, publish, and cloud tasks, so one exposed token can touch many systems at once.

Q: How do security teams know whether device revocation is actually working?

A: They should test the full authorisation path, not just the revoke request.

Practitioner guidance

• Block package-install execution on CI runners Prevent untrusted npm install hooks from running in build environments where runner memory contains cloud, GitHub, or vault credentials.
• Scope publishing tokens to the narrowest possible action Remove repository-creation and workflow-modification rights from CI/CD tokens unless they are explicitly required.
• Revoke and rotate on first compromise signal Treat a confirmed malicious package install as an identity event, not just an endpoint event.

What's in the full analysis

StepSecurity's full blog covers the operational detail this post intentionally leaves for the source:

• Process-by-process attack timeline showing how the malicious npm payload read runner memory and harvested secrets
• Package-by-package exposure list and version mapping for the affected AntV ecosystem releases
• Defensive product details for Harden-Runner, Secure Registry, and Dev Machine Guard in real-world workflows
• Indicators of compromise and response steps for teams validating whether their environments were touched

👉 Read StepSecurity's analysis of the Mini Shai-Hulud npm supply chain attack →

Mini Shai-Hulud in npm: what CI/CD secrets abuse means for teams?

Explore further

View Full Forum →  |  NHI Foundation Course →