Executive Summary
In April 2026, a sophisticated supply chain attack, dubbed 'Mini Shai-Hulud,' targeted SAP's npm packages, compromising four key components: @cap-js/db-service@2.10.1, @cap-js/postgres@2.2.2, @cap-js/sqlite@2.2.2, and mbt@1.2.48. Attackers injected malicious preinstall scripts into these packages, which, upon installation, executed a multi-stage payload designed to harvest sensitive developer credentials, including GitHub tokens, cloud service keys, and AI tool configurations. The stolen data was exfiltrated to attacker-controlled GitHub repositories, complicating detection and mitigation efforts. (endorlabs.com)
This incident underscores the escalating threat of supply chain attacks within the software development ecosystem. By compromising widely-used development tools, attackers can infiltrate numerous organizations, highlighting the critical need for enhanced security measures in dependency management and continuous monitoring of third-party components.
Why This Matters Now
The 'Mini Shai-Hulud' attack exemplifies the growing sophistication of supply chain threats, emphasizing the urgency for organizations to implement stringent security protocols for third-party dependencies and to remain vigilant against evolving attack vectors targeting development environments.
Attack Path Analysis
The attackers compromised SAP-related npm packages by exploiting a configuration gap, allowing them to publish malicious versions. Upon installation, these packages executed scripts to download and run malware, harvesting sensitive credentials and secrets. The malware then spread by injecting malicious workflows into other repositories, facilitating lateral movement. Stolen data was exfiltrated to public GitHub repositories under the victims' accounts. The attack culminated in unauthorized access to critical systems and data, leading to potential operational disruptions.
Kill Chain Progression
Initial Compromise
Description
Attackers exploited a configuration gap in npm's OIDC trusted publishing to publish malicious versions of SAP-related packages.
MITRE ATT&CK® Techniques
Compromise Software Dependencies and Development Tools
User Execution: Malicious Library
Unsecured Credentials: Credentials in Files
Application Layer Protocol: Web Protocols
Command and Scripting Interpreter: JavaScript
Indicator Removal: File Deletion
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
PCI DSS 4.0 – Ensure all system components and software are protected from known vulnerabilities
Control ID: 6.2
NYDFS 23 NYCRR 500 – Cybersecurity Policy
Control ID: 500.03
DORA – ICT Risk Management Framework
Control ID: Article 5
CISA ZTMM 2.0 – Supply Chain Risk Management
Control ID: 3.1
NIS2 Directive – Cybersecurity Risk Management Measures
Control ID: Article 21
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Computer Software/Engineering
SAP npm package poisoning directly compromises development environments, stealing credentials and injecting malicious code into software supply chains globally.
Information Technology/IT
Supply chain attacks targeting development tools expose IT infrastructure through stolen tokens, cloud secrets, and automated malware propagation mechanisms.
Financial Services
Social media fraud causing $2.1 billion losses and cryptocurrency laundering schemes directly impact financial institutions and regulatory compliance frameworks.
Health Care / Life Sciences
State-sponsored espionage targeting COVID-19 research organizations compromises critical medical data and violates HIPAA compliance requirements for patient protection.
Sources
- The Good, the Bad and the Ugly in Cybersecurity – Week 18https://www.sentinelone.com/blog/the-good-the-bad-and-the-ugly-in-cybersecurity-week-18-7/Verified
- SAP npm Packages Compromised by 'Mini Shai-Hulud' Credential-Stealing Malwarehttps://thehackernews.com/2026/04/sap-npm-packages-compromised-by-mini.htmlVerified
- Ongoing supply chain attacks worm into SAP npm packageshttps://www.theregister.com/2026/04/30/supply_chain_attacks_sap_npm_packages/Verified
- Supply chain attack against SAP npm packages facilitates credential thefthttps://www.scworld.com/brief/supply-chain-attack-against-sap-npm-packages-facilitates-credential-theftVerified
Frequently Asked Questions
Cloud Native Security Fabric Mitigations and ControlsCNSF
Aviatrix Zero Trust CNSF is pertinent to this incident as it could have limited the attacker's ability to move laterally and exfiltrate data by enforcing strict segmentation and controlled egress policies.
Control: Cloud Native Security Fabric (CNSF)
Mitigation: The attacker's ability to deploy malicious packages may have been constrained by enforcing strict identity-based access controls and continuous verification of publishing configurations.
Control: Zero Trust Segmentation
Mitigation: The malware's access to sensitive credentials and secrets could have been limited by enforcing strict segmentation policies, reducing the scope of unauthorized access.
Control: East-West Traffic Security
Mitigation: The malware's ability to propagate to other repositories may have been constrained by monitoring and controlling east-west traffic, reducing lateral movement.
Control: Multicloud Visibility & Control
Mitigation: The exfiltration of data to unauthorized repositories could have been limited by providing comprehensive visibility and control over multicloud environments.
Control: Egress Security & Policy Enforcement
Mitigation: The unauthorized exfiltration of sensitive data may have been constrained by enforcing strict egress policies, reducing data leakage.
The overall impact of the attack could have been reduced by limiting the attacker's ability to access critical systems and data through enforced segmentation and controlled access.
Impact at a Glance
Affected Business Functions
- Software Development
- Continuous Integration/Continuous Deployment (CI/CD) Pipelines
- Cloud Application Deployment
Estimated downtime: 7 days
Estimated loss: $500,000
Developer credentials, GitHub and npm tokens, cloud service secrets (AWS, Azure, GCP, Kubernetes), and browser-stored passwords.
Recommended Actions
Key Takeaways & Next Steps
- • Implement Zero Trust Segmentation to enforce least privilege access and prevent unauthorized lateral movement.
- • Enhance Threat Detection & Anomaly Response capabilities to identify and respond to malicious activities promptly.
- • Utilize Multicloud Visibility & Control to monitor and manage security policies across all cloud environments.
- • Apply Egress Security & Policy Enforcement to control outbound traffic and prevent data exfiltration.
- • Regularly update and patch software dependencies to mitigate vulnerabilities in the supply chain.



