HomeIntelligenceBrief
BREACH BRIEF🟠 High ThreatIntel

Supply Chain Attack Compromises SAP‑Related npm Packages, Harvesting Developer Credentials

Researchers have identified a supply‑chain campaign that injected credential‑stealing malware into SAP‑related npm packages. The malicious versions were downloaded by developers worldwide, creating a potential exposure of stored tokens and API keys. TPRM teams must verify dependencies and rotate compromised credentials.

LiveThreat™ Intelligence · 📅 April 29, 2026· 📰 thehackernews.com
🟠
Severity
High
TI
Type
ThreatIntel
🎯
Confidence
High
🏢
Affected
2 sector(s)
Actions
4 recommended
📰
Source
thehackernews.com

Supply Chain Attack Compromises SAP‑Related npm Packages, Harvesting Developer Credentials

What Happened — A coordinated supply‑chain campaign dubbed “mini Shai‑Hulud” injected credential‑stealing malware into several npm packages that are part of SAP’s JavaScript SDKs and cloud‑application tooling. The malicious versions were published to the public npm registry and downloaded by developers worldwide, allowing attackers to capture stored credentials and tokens.

Why It Matters for TPRM

  • Third‑party code libraries can become a covert conduit for credential theft, exposing downstream customers.
  • SAP‑related components are widely used in enterprise ERP, finance, and supply‑chain applications, amplifying risk across multiple sectors.
  • The attack demonstrates the need for continuous monitoring of open‑source dependencies in vendor‑managed environments.

Who Is Affected — Enterprises that integrate SAP JavaScript SDKs, cloud‑native SAP services, or any applications that depend on the compromised npm packages (across finance, manufacturing, professional services, and SaaS providers).

Recommended Actions

  • Inventory all projects that consume SAP‑related npm packages and verify their versions.
  • Replace compromised packages with clean, verified releases or alternative libraries.
  • Enforce strict SCA (Software Composition Analysis) and integrity‑checking pipelines for all third‑party dependencies.
  • Rotate any credentials or tokens that may have been exposed and monitor for anomalous activity.

Technical Notes — The attack leveraged a third‑party dependency vector, publishing malicious code under legitimate package names. No public CVE was issued, but the malware performed credential harvesting (e.g., npm tokens, API keys) and exfiltrated them to attacker‑controlled endpoints. Source: The Hacker News

📰 Original Source
https://thehackernews.com/2026/04/sap-npm-packages-compromised-by-mini.html

This LiveThreat Intelligence Brief is an independent analysis. Read the original reporting at the link above.

Monitor Your Vendor Risk with LiveThreat™

Get automated breach alerts, security scorecards, and intelligence briefs when your vendors are compromised.