How a Npm Package Attack Breached Developer Security
61A recent supply chain attack targeting SAP-related npm packages has raised serious concerns about the security of developer tools and build processes used by large enterprises. The attack, called “mini Shai-Hulud,” compromised several packages used in SAP’s JavaScript and cloud app development ecosystem. Malicious versions of these packages were published in April, containing code that could steal sensitive developer credentials and cloud access tokens.
The Scope of the Attack
The affected packages included mbt@1.2.48 and several from the @cap-js namespace, such as @cap-js/db-service, @cap-js/postgres, and @cap-js/sqlite. Researchers discovered that the malicious versions had been published on April 29 and were later replaced by clean versions. The malware encrypted the stolen data and uploaded it to public GitHub repositories created from the victims’ own accounts. It also used stolen tokens to add malicious workflows to repositories and publish poisoned package updates.
Investigations revealed that the attackers exploited a vulnerability in npm’s OIDC trusted publishing setup for the affected @cap-js packages. For the mbt package, the compromise is believed to involve a static npm token. The attackers also tried to maintain persistence by modifying developer workstations and AI-assisted coding tools like Visual Studio Code and Claude Code. This attack highlights how developer environments and automated coding tools are becoming key targets in supply chain security threats.
Implications for Security Leaders
This incident shows how quickly compromised dependencies can spread beyond the initial build process. It underscores the fact that developer environments, while central to software delivery, often lack the same level of governance and oversight as production systems. A single compromised developer account or token can give attackers access to the entire supply chain, enabling them to inject malicious code into packages that downstream teams might unknowingly install.
Security experts warn that this kind of attack makes developer workstations and CI/CD pipelines prime targets. If attackers gain control over a developer’s identity, they can push malicious updates or steal secrets. The attack also raises concerns about visibility—many organizations still struggle to monitor what happens inside their development tools and repositories. While some companies plan to deploy AI-based security measures to detect such threats, many are still in the planning phases and have yet to operationalize these defenses.
Overall, the mini Shai-Hulud attack demonstrates the need for stronger controls and monitoring across all stages of software development. It also highlights the importance of securing developer credentials and reviewing third-party dependencies regularly. As attacks become more sophisticated, organizations must treat developer environments as critical security points, not just the final production systems.
What do you think?
It is nice to know your opinion. Leave a comment.