--- title: North Korea hit npm's most-downloaded packages, and... description: Amazon has attributed a series of npm supply-chain attacks to Sapphire Sleet (BlueNoroff), a North Korean state-sponsored threat actor. The targeted packages —... canonical: https://daily.dev/posts/north-korea-hit-npm-s-most-downloaded-packages-and-amazon-sat-on-it-long-enough-to-double-check-it--tsh0b9t3n twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: North Korea hit npm's most-downloaded packages, and Amazon sat on it long enough to double-check it wasn't ChatGPT | daily.dev og:description: Amazon has attributed a series of npm supply-chain attacks to Sapphire Sleet (BlueNoroff), a North Korean state-sponsored threat actor. The targeted packages —... og:url: https://daily.dev/posts/north-korea-hit-npm-s-most-downloaded-packages-and-amazon-sat-on-it-long-enough-to-double-check-it--tsh0b9t3n og:image: https://api.daily.dev/og/posts/TsH0b9T3n.png og:image:alt: North Korea hit npm's most-downloaded packages, and Amazon sat on it long enough to double-check it wasn't ChatGPT og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # North Korea hit npm's most-downloaded packages, and Amazon sat on it long enough to double-check it wasn't ChatGPT **[Trends](https://daily.dev/sources/trends)** · 2 min read · 1 upvotes · 1 comments ## Summary Amazon has attributed a series of npm supply-chain attacks to Sapphire Sleet (BlueNoroff), a North Korean state-sponsored threat actor. The targeted packages — debug, chalk, axios, and typo-crypto — include some of npm's most downloaded, with axios alone exceeding 100 million weekly downloads. The attack relied on months-long social engineering campaigns against package maintainers rather than technical exploits. Within two hours of malicious updates going live, an estimated 10% of cloud environments were affected. Amazon's report highlights new attacker tactics: splitting payloads across files to evade static analysis, environment-aware malware, and AI-assisted 'slopsquatting' targeting package names hallucinated by LLMs. Amazon is pledging $12.5M to the Akrites initiative and collaboration with OpenSSF, though the fundamental weakness — npm's reliance on maintainer trustworthiness — remains unresolved. ## Content Amazon's security team has formally attributed a 16-month npm supply chain campaign to Sapphire Sleet, the North Korean threat group also known as BlueNoroff. The targets weren't obscure packages: debug (2.6 billion weekly downloads), chalk, axios (100 million weekly downloads), and typo-crypto. The method was patient social engineering — attackers spent months building trust with maintainers before pushing malicious updates that downstream projects pulled in automatically. The scale of the damage is what's hard to shake. Wiz found roughly 1 in 10 cloud environments were hit by the debug and chalk compromise within a two-hour window. That's not a targeted attack. That's a flood. What's changed, and what makes this harder to defend against going forward, is AI. The group is now using generative AI to write cleaner malware — less obviously suspicious, harder to flag with static analysis. They're also splitting malicious logic across multiple packages so no single package looks dangerous in isolation. One conference talk covering the broader supply chain threat landscape noted that attackers are hiding payloads using Unicode steganography, and that a self-propagating worm called Shahalude managed to steal secrets, flip private repos public, and arm a ransomware dead-man switch before anyone noticed. The CVE system isn't keeping up. There's a three-month average lag before vulnerabilities get published, and 67% apparently never get disclosed at all — quietly patched, no record. "Shadow patching" is the term, and it means your dependency scanner is working from an incomplete picture. Amazon is responding with community intelligence sharing, OpenSSF collaboration, and a $12.5M investment in something called the Akrites initiative. Corey Quinn's take on the announcement: Amazon had to "triple check that it wasn't in fact OpenAI failing to properly supervise its models" before attributing it to North Korea. Pointed, but the underlying concern is real — AI-generated malicious code is getting harder to distinguish from the legitimate kind. Practical mitigations getting attention: enforce a 48-hour minimum package age before pulling upgrades, use hybrid static analysis and LLM scanning tools like OpenGrip, and check out the open-source Aikido SafeChain tool. None of these are silver bullets when the attack surface is 25 transitive dependencies per direct install. ## Community take How the wider developer community reacted, aggregated from 1 discussion and 34 comments across hackernews (as of 2026-08-05). **TL;DR:** The community is largely skeptical of npm/GitHub's new security measures, debating whether the 72-hour cooldown is too short and questioning whether these are meaningful solutions to a deeper ecosystem problem. **Sentiment:** 15% positive · 40% mixed · 45% skeptical **The case for** - Trusted publishing improves security by requiring an attacker to trigger a specific workflow on GitHub, leaving a traceable footprint. - Cooldowns are cheap to deploy and give scanners more time to detect malicious packages. - The npm security team can often remove poisoned releases independently of the maintainer. **The pushback** - 72 hours is seen by many as too short — people travel, get sick, or are away over weekends, and attackers deliberately strike on Fridays. - A cooldown is considered a low-tech band-aid when GitHub has access to sophisticated static analysis tools it could use instead. - npm is singled out as uniquely prone to these supply-chain issues compared to other language ecosystems. **By community** - hackernews (skeptical): Commenters are broadly critical of the 72-hour window and view the cooldown as an underwhelming response to a systemic npm security problem. **Hottest debate:** Whether 72 hours is a reasonable cooldown duration or dangerously too short given real-world maintainer availability. **Open questions** - What data-driven method should be used to pick the optimal cooldown duration? - Why isn't GitHub leveraging its code analysis capabilities for more sophisticated supply-chain protection instead of a simple time delay? - Does trusted publishing actually prevent attacks if the CI workflow itself is compromised? **Highlights** > There is a big difference between 3 days when someone may be sick or traveling and not looking and 30 which aligns better with 99% of scenarios this may be an issue with. 3 days is absurd. Even password apps with kill switches will default to 7 days. Cyber attacks will frequently happen on a Friday just for this scenario, they anticipate no ones looking over the weekend. > — [datakan on hackernews · 1 comments](https://news.ycombinator.com/item?id=49099173) > Github owns NPM. Github has unprecedented access to code analysis tools. Github can run static analysis on nearly everything. Introducing a cooldown period seems like the lowest tech solution to a technological problem I have seen in a longwhile. > — [summarybot on hackernews · 2 comments](https://news.ycombinator.com/item?id=49099169) > Trusted Publishing pins the publish to the workflow. The next step is to isolate "run untrusted code (`npm build`)" from "publish" in your workflows. Now you have two properties - the publish can only happen from one place and the publish is isolated from untrusted code execution. > — [insanitybit on hackernews](https://news.ycombinator.com/item?id=49100869) > And 365 days probably aligns with 100% of scenarios. It doesn't mean it's a good idea, because the longer the delay is the more downsides you also get. Blocking a maintainer from pushing updates for a full month after changing their e-mail would be obviously absurd. So Github would have to add a way of enabling maintainers to super-uper-duper confirm the change and cut the delay short. Which is likely not currently possible, hence starting with a shorter delay. > — [tredre3 on hackernews](https://news.ycombinator.com/item?id=49099514) **Source threads** - [hackernews](https://news.ycombinator.com/item?id=49096427) · 33 points · 34 comments ## Community discussion Top comments from developers on daily.dev. **@seyoungcho** · 0 upvotes > The country where the nation itself hacks other countries. The worst country ever ## Similar posts on daily.dev - [North Korean Hackers Suspected in Supply Chain Attack on Popular Axios Project](https://daily.dev/posts/north-korean-hackers-suspected-in-supply-chain-attack-on-popular-axios-project-zqfdplgvt) · DevOps.com · 1 upvotes · 0 comments --- Tags: [#security](https://daily.dev/tags/security), [#javascript](https://daily.dev/tags/javascript), [#npm](https://daily.dev/tags/npm) [View this post on daily.dev](https://daily.dev/posts/north-korea-hit-npm-s-most-downloaded-packages-and-amazon-sat-on-it-long-enough-to-double-check-it--tsh0b9t3n) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"North Korea hit npm's most-downloaded packages, and Amazon sat on it long enough to double-check it wasn't ChatGPT","url":"https://daily.dev/posts/north-korea-hit-npm-s-most-downloaded-packages-and-amazon-sat-on-it-long-enough-to-double-check-it--tsh0b9t3n","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/north-korea-hit-npm-s-most-downloaded-packages-and-amazon-sat-on-it-long-enough-to-double-check-it--tsh0b9t3n"},"datePublished":"2026-07-30T20:36:27.122Z","dateModified":"2026-08-05T12:03:45.862Z","description":"Amazon has attributed a series of npm supply-chain attacks to Sapphire Sleet (BlueNoroff), a North Korean state-sponsored threat actor. The targeted packages —...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/b6100a77b69e07c7bb557c29b03e69b7?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/b6100a77b69e07c7bb557c29b03e69b7?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Trends","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Trends","logo":"https://media.daily.dev/image/upload/s--ZfSp3asX--/f_auto,q_auto/v1780996004/logos/trends?_a=BAMAMiWQ0","url":"https://daily.dev/sources/trends"},"commentCount":1,"discussionUrl":"https://daily.dev/posts/north-korea-hit-npm-s-most-downloaded-packages-and-amazon-sat-on-it-long-enough-to-double-check-it--tsh0b9t3n","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":1}],"keywords":"security,javascript,npm","timeRequired":"PT2M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Trends","item":"https://daily.dev/sources/trends"},{"@type":"ListItem","position":3,"name":"North Korea hit npm's most-downloaded packages, and Amazon sat on it long enough to double-check it wasn't ChatGPT"}]} {"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/north-korea-hit-npm-s-most-downloaded-packages-and-amazon-sat-on-it-long-enough-to-double-check-it--tsh0b9t3n","comment":[{"@type":"Comment","text":"The country where the nation itself hacks other countries. The worst country ever","datePublished":"2026-07-31T02:36:40.584Z","url":"https://daily.dev/posts/TsH0b9T3n#c-y3143ww23","author":{"@type":"Person","name":"SeyoungCho","url":"https://daily.dev/seyoungcho","image":"https://media.daily.dev/image/upload/s---QniJFEK--/f_auto/v1724901542/avatars/avatar_O3ucZSadxc0iLADSOH3rX"}}]} ```