Executive Summary
In November 2025, a major multi-ecosystem software supply chain attack was uncovered when the Shai-Hulud v2 campaign spread beyond the npm registry into Maven Central. Threat actors compromised over 830 npm packages and at least one Maven package (org.mvnpm:posthog-node:4.18.1), embedding malicious loaders and payloads that silently exfiltrated thousands of developer and organizational secrets. This attack leveraged highly automated techniques to inject stealthy code across registries, making mitigation and detection notably difficult. The campaign’s broad reach threatened applications, organizational infrastructure, and customers reliant on compromised components.
This incident highlights a rising trend where sophisticated threat actors exploit trusted open-source software ecosystems, dramatically increasing supply chain risk. Recent surges in attacks targeting developer supply chains have prompted urgent calls for enhanced controls, continuous monitoring, stronger segmentation, and stricter compliance with software integrity standards.
Why This Matters Now
The spread of Shai-Hulud v2 from npm to Maven demonstrates the widening scope and automation of supply chain attacks targeting core software infrastructure. With attackers compromising trusted open-source components across ecosystems, organizations face an urgent need to verify code integrity, monitor for lateral attacker movement, and enforce zero trust policies across development pipelines.
Attack Path Analysis
The Shai-Hulud v2 campaign began with the compromise of npm and Maven software supply chains, introducing malicious packages to downstream development pipelines. Attackers leveraged the injected code to establish a foothold in cloud environments and potentially escalate privileges by abusing service accounts or misconfigured permissions. From there, they likely moved laterally across workloads or containers within victim environments, using cloud-native protocols or APIs to expand access. The payloads initiated command and control by communicating with external infrastructure, maintaining a covert channel to receive attacker commands. Stolen credentials or secrets were exfiltrated over the network, often using encrypted or covert traffic to avoid detection. Ultimately, the attackers' access enabled data exposure, credential compromise, and potential disruption to CI/CD pipelines and production systems.
Kill Chain Progression
Initial Compromise
Description
Malicious npm and Maven packages with embedded loaders and payloads were introduced into victim environments via trusted software supply chain updates.
Related CVEs
CVE-2025-22230
CVSS 9.8A supply chain attack in npm and Maven ecosystems allows attackers to inject malicious code into packages, leading to unauthorized access and data exfiltration.
Affected Products:
PostHog posthog-node – 4.18.1
AsyncAPI asyncapi – *
Postman postman – *
Exploit Status:
exploited in the wildReferences:
MITRE ATT&CK® Techniques
Supply Chain Compromise: Compromise Software Supply Chain
Command and Scripting Interpreter: JavaScript
Server Software Component: Web Shell
Obfuscated Files or Information
Unsecured Credentials: Credentials In Files
Credentials from Password Stores: Credentials from Web Browsers
Exfiltration Over C2 Channel
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
PCI DSS 4.0 – Change Control Processes
Control ID: 6.4.3
NYDFS 23 NYCRR 500 – Cybersecurity Policy
Control ID: 500.03
DORA (Digital Operational Resilience Act) – ICT Risk Management Requirements
Control ID: Article 9
CISA Zero Trust Maturity Model 2.0 – Software Supply Chain Security
Control ID: Supply Chain Pillar
NIS2 Directive – Supply Chain Security
Control ID: Article 21(2)d
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Computer Software/Engineering
Supply chain attacks targeting npm and Maven repositories directly compromise software development pipelines, exposing source code and secrets across development workflows.
Information Technology/IT
IT infrastructure relying on compromised packages faces lateral movement risks, requiring zero trust segmentation and enhanced egress security policy enforcement capabilities.
Financial Services
Banking systems using affected packages risk data exfiltration and compliance violations, necessitating encrypted traffic controls and anomaly detection for regulatory adherence.
Health Care / Life Sciences
Healthcare organizations face HIPAA compliance breaches through compromised development dependencies, requiring multicloud visibility and Kubernetes security for patient data protection.
Sources
- Shai-Hulud v2 Spreads From npm to Maven, as Campaign Exposes Thousands of Secretshttps://thehackernews.com/2025/11/shai-hulud-v2-campaign-spreads-from-npm.htmlVerified
- Shai-Hulud, The Second Coming - Ongoing npm supply chain attackhttps://research.jfrog.com/post/shai-hulud-the-second-coming/Verified
- Shai-Hulud 2.0: Guidance for detecting, investigating, and defending against the supply chain attackhttps://www.microsoft.com/en-us/security/blog/2025/12/09/shai-hulud-2-0-guidance-for-detecting-investigating-and-defending-against-the-supply-chain-attack/Verified
Frequently Asked Questions
Cloud Native Security Fabric Mitigations and ControlsCNSF
Applying Zero Trust principles—including network and workload segmentation, egress filtering, and centralized threat visibility—would have limited the attacker’s ability to gain initial access, move laterally, establish C2, and exfiltrate secrets from cloud environments. CNSF capabilities mapped to supply chain exposures would detect anomalous behaviors, prevent unrestricted east-west movement, and block data leaks.
Control: Threat Detection & Anomaly Response
Mitigation: Early detection of anomalous activity post-package deployment.
Control: Zero Trust Segmentation
Mitigation: Limits access scope and blocks unauthorized privilege escalation.
Control: East-West Traffic Security
Mitigation: Prevents unauthorized east-west connections within cloud environments.
Control: Egress Security & Policy Enforcement
Mitigation: Blocks unauthorized outbound connections used for C2.
Control: Cloud Firewall (ACF)
Mitigation: Detects and blocks exfiltration attempts through firewall inspection.
Centralized monitoring uncovers propagation and residual attacker access.
Impact at a Glance
Affected Business Functions
- Software Development
- Continuous Integration/Continuous Deployment (CI/CD)
Estimated downtime: 7 days
Estimated loss: $5,000,000
The attack led to the exfiltration of sensitive data, including API keys, GitHub tokens, and cloud credentials, from over 28,000 repositories, exposing 11,858 unique secrets.
Recommended Actions
Key Takeaways & Next Steps
- • Enforce Zero Trust segmentation to contain supply chain-driven threats and restrict lateral movement between workloads.
- • Deploy egress security controls to block malicious outbound C2 and data exfiltration attempts.
- • Implement continuous network and behavioral monitoring for early detection of anomalous package or workload activity.
- • Use cloud-native firewalls and runtime policy enforcement to protect internal and external service boundaries.
- • Centralize incident response, logging, and policy visualization across multicloud and hybrid environments to minimize attacker dwell time.
