top of page
perceptive_background_267k.jpg

Amazon links Debug, Chalk NPM supply-chain attacks to North Korean hackers

Published:

30 July 2026 at 18:13:24

Alert date:

30 July 2026 at 19:06:06

Source:

bleepingcomputer.com

Click to open the original link from this advisory

Supply Chain & Dependencies, Ransomware & Malware

Amazon has attributed multiple high-profile supply chain attacks targeting the npm ecosystem to North Korean state-sponsored hackers. The attacks involved the compromise of widely-used npm packages including Debug and Chalk, which are downloaded millions of times weekly. By injecting malicious code into these packages, the threat actors aimed to compromise the vast number of developers and systems that depend on them. This campaign is consistent with previously observed North Korean tactics of targeting software supply chains for financial gain or espionage. The attribution was made by Amazon security researchers who identified infrastructure and behavioral patterns linked to known North Korean threat groups such as Lazarus Group.

Technical details

Amazon attributed multiple npm supply chain attacks to the North Korean threat actor Sapphire Sleet (also known as BlueNoroff and Stardust Chollima). The campaign began in March 2025 with the trojanization of the 'typo-crypto' package, used as a testing ground. In September 2025, the widely used 'debug' and 'chalk' packages were compromised, affecting an estimated 10% of cloud environments within two hours. In March 2026, the 'axios' package (100M+ weekly downloads) was targeted. Attackers gained access by socially engineering package maintainers and publishing malicious updates automatically distributed to users. Key TTPs include: splitting malicious functionality across multiple benign-looking packages; spending months building trust before introducing malicious code; decoupling malicious behavior from package contents via external scripts or remote servers; using strong encryption and multi-stage payloads with runtime or remotely fetched keys; environment-aware payloads that delay execution unless real developer or production environments are detected; and exploiting 'slopsquatting' by registering package names hallucinated by AI coding assistants. AI tools were used to generate code, documentation, and fake maintainer identities. Attribution is medium-confidence based on shared TTPs, C2 infrastructure, and operational similarities. Financial motivation is suspected.

Mitigation steps:

1. Audit all npm dependencies for recently published updates to widely used packages, especially debug, chalk, axios, and typo-crypto. 2. Monitor for unexpected outbound connections to unknown C2 infrastructure from Node.js applications. 3. Implement software composition analysis (SCA) tools to detect malicious or tampered packages in your supply chain. 4. Enable package integrity checks and lockfile enforcement (package-lock.json or yarn.lock) to prevent unexpected package updates. 5. Be cautious of AI-suggested package names (slopsquatting) — verify package existence and legitimacy before installation. 6. Require multi-factor authentication for npm maintainer accounts and monitor for unauthorized account access. 7. Use runtime security monitoring to detect environment-aware or delayed-execution payloads. 8. Collaborate with OpenSSF and follow advisories from Amazon and other security partners regarding compromised packages. 9. Review and restrict the use of postinstall scripts in npm packages. 10. Participate in or monitor the Akrites initiative for updates on AI-enabled supply chain attack protections.

Affected products:

typo-crypto (npm package)
debug (npm package)
chalk (npm package)
axios (npm package
100M+ weekly downloads)

Related links:

Related CVE's:

Related threat actors:

IOC's:

This article was created with the assistance of AI technology by Perceptive.

© 2025 by Perceptive Security. All rights reserved.

email: info@perceptivesecurity.com

Disclaimer: Deze website toont informatie afkomstig van externe bronnen. Perceptive aanvaardt geen verantwoordelijkheid voor de inhoud, juistheid of volledigheid van deze informatie.

bottom of page