Amazon has officially attributed the September 2025 hijack of the popular npm packages debug and chalk to North Korea’s Sapphire Sleet hacking group. The finding, announced by the tech giant on 30 July, reclassifies an incident previously seen as an opportunistic cryptocurrency theft into a state-sponsored supply-chain attack.
The breach centered on the widely used debug and chalk packages, along with at least 16 others. Together, these packages boasted more than two billion weekly downloads. Attackers compromised a maintainer through a phishing lure using a lookalike npm domain, enabling them to push a malicious update containing a wallet-draining script. For nearly ten months, the episode remained publicly documented only as a crypto-focused intrusion; earlier analyses from Aikido and Wiz detailed the technical mechanics but did not assign formal attribution.
The compromise did not rely on a flaw in the packages themselves. Instead, operators targeted the human element, successfully deceiving a maintainer to gain control. Once inside, the malicious code was published under legitimate package names, giving it immediate access to countless development environments and production systems that pull automatic updates. While the observed payload targeted cryptocurrency, the level of access achieved could have been leveraged for persistent backdoors or further network infiltration.
The incident underscores long-standing warnings that a small number of foundational open-source packages act as critical infrastructure. The compromise of a handful of maintainers can cascade through the global JavaScript ecosystem in a matter of hours. Automated scanning and dependency pinning, while useful, are insufficient safeguards against the weakness of human account security.
In response, pressure is mounting for package registries to implement stronger protections for maintainers of high-impact projects. Recommended measures include mandatory, phishing-resistant multi-factor authentication (MFA), stricter verification of publisher domains to block lookalike sites, and real-time monitoring for anomalous version releases. The Amazon attribution is expected to accelerate the rollout of these safeguards.
The involvement of a state-sponsored group significantly alters the threat model. North Korean clusters like Sapphire Sleet have increasingly targeted open-source repositories as both a funding source and a vector for longer-term access. What begins as a cryptocurrency stealer could, with the same foothold, evolve into a platform for espionage or sabotage. Faster, collaborative attribution between cloud providers, security researchers, and open-source stewards will be vital to distinguishing criminal activity from geopolitical operations in time to contain damage.
For developers and organizations, the lesson is clear: treat every transitive dependency as a potential trust boundary. Enforce lockfiles, monitor for unexpected package updates, and advocate for better security tooling and funding for maintainers of critical libraries. The 2025 hijack went unattributed for nearly a year; Amazon’s findings close that gap and starkly illustrate how a single phished credential can threaten the broader software supply chain.
亞馬遜已正式將2025年9月對熱門npm套件debug及chalk的劫持事件，歸因於北韓的Sapphire Sleet黑客組織。這家科技巨頭於7月30日公布的發現，將此事件從原先視為 opportunistic 的加密貨幣竊取行為，重新定性為一場國家資助的供應鏈攻擊。
此次入侵主要針對廣泛使用的debug和chalk套件，以及至少另外16個套件。這些套件合計每週下載量超過二十億次。攻擊者透過一個偽造的npm網域進行釣魚誘騙，成功入侵了一名套件維護者，從而得以推送一個包含耗盡錢包腳本的惡意更新。近十個月來，此事在公開記錄中僅被描述為針對加密貨幣的入侵事件；Aikido和Wiz等公司的早期分析雖詳述了技術機制，但未正式歸因。
此次入侵並非利用套件本身的漏洞。相反，操作者鎖定人的因素，成功欺騙維護者以獲取控制權。一旦進入系統，惡意代碼便以合法套件名稱發布，使其立即存取無數拉取自動更新的開發環境及生產系統。儘管觀察到的有效載荷針對加密貨幣，但其取得的存取權限本可用於建立持久性後門或進一步滲透網絡。
此事件凸顯了長期存在的警告：少數基礎性開源套件充當關鍵基礎設施。少數幾位維護者遭入侵，可能在數小時內透過全球JavaScript生態系統產生連鎖反應。自動化掃描及依賴版本鎖定固然有用，但針對人類帳戶安全的弱點而言，這些保護措施並不足夠。
作為回應，要求套件儲存庫為高影響力專案的維護者實施更強保護措施的呼聲日益高漲。建議措施包括強制使用防釣魚的多因素認證（MFA）、更嚴格地驗證發布者網域以阻擋仿冒網站，以及即時監控異常的版本發布。預計亞馬遜的歸因將加速這些保障措施的推出。
一個國家資助團體的參與，顯著改變了威脅模型。像Sapphire Sleet這樣的北韓組織，已越來越頻繁地將開源程式庫作為資金來源及長期存取的向量。最初是加密貨幣竊取工具，可能藉由同樣的立足點，演變成間諜或破壞活動的平台。雲端供應商、安全研究人員及開源管理員之間更快、更協作的歸因，將對於區分犯罪活動與地緣政治行動至關重要，以便及時遏制損害。
對開發者和組織而言，教訓是明確的：將每個間接依賴視為潛在的信任邊界。強制使用鎖定檔、監控意外的套件更新，並倡導為關鍵程式庫的維護者提供更好的安全工具及資金。2025年的劫持事件近一年未被歸因；亞馬遜的發現填補了這一空白，並鮮明地闡明了一個被釣魚的憑證如何能威脅到整個軟件供應鏈。