Topic starter
18/08/2026 2:56 pm
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.
Editorial analysis by NHI Mgmt Group, based on content published by StepSecurity: “Shai-Hulud: Here We Go Again. Mass npm Supply Chain Attack Hits the AntV Ecosystem”.
By the numbers:
- Over 2,200 public GitHub repositories had already been created using exfiltrated tokens.
- The attack unfolded in two coordinated waves on May 19, 2026, with all malicious packages published within a compressed window.
Key questions
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: What are the signs that a build token has been abused after exposure?
A: Unexpected repository creation, abnormal package publication, workflow edits, and outbound connections tied to runner hosts are strong indicators.
Practitioner guidance
- Isolate package installation from secret-bearing workflows Run third-party dependency installs in build stages that do not hold cloud tokens, publishing rights, or long-lived vault credentials.
- Reduce CI token scope to the minimum publish path Remove repository creation, package publishing, and cross-repo permissions from CI/CD tokens unless a specific job requires them.
- Inspect runner memory exposure paths Review which workflows can access process memory, privileged shells, or debug tooling that can reveal masked secrets during execution.
Bottom line: Mini Shai-Hulud shows that npm supply chain compromise can move directly from package execution to CI/CD secret theft and token reuse.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
18/08/2026 3:38 pm
Secrets in CI/CD are no longer just leaked, they are operationalised: once a workflow token can create repositories or publish packages, the secret has become infrastructure, not merely access. That changes governance from rotation-only thinking to lifecycle and blast-radius control. The control failure here is assuming that compromise ends at disclosure when, in practice, the stolen token becomes a reusable production capability.
A few things that frame the scale:
- 96% of organisations store secrets outside of secrets managers in vulnerable locations including code, config files, and CI/CD tools, according to the Ultimate Guide to NHIs.
- Breaches involving third parties rose to 48% of all breaches, a 60% increase on the previous year, according to Verizon's 2026 Data Breach Investigations Report.
A question worth separating out:
Q: How should teams govern secrets in infrastructure as code pipelines?
A: Teams should keep secrets out of code and move them into a dedicated runtime secrets service, then enforce policy that prevents repository storage and console exposure. The goal is to make credential lifecycle controls independent from the IaC repository, so revocation, rotation, and access review can happen without editing infrastructure templates.
👉 Read our full editorial: Mini Shai-Hulud shows how npm worms turn CI/CD secrets into infrastructure