# NPM Supply chan attack - again

**URL:** <https://forum.babylonjs.com/t/npm-supply-chan-attack-again/61573>\
**Category:** Off topic\
**Tags:** npm, npmjs, security\
**Created:** [November 26, 2025, 2:04pm UTC](https://forum.babylonjs.com/t/npm-supply-chan-attack-again/61573 "2025-11-26T14:04:53Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![ntech](https://avatars.discourse-cdn.com/v4/letter/n/e0b2c6/32.png) [@ntech](https://forum.babylonjs.com/u/ntech)\
**Post date:** [November 26, 2025, 2:04pm UTC](https://forum.babylonjs.com/t/npm-supply-chan-attack-again/61573/1 "2025-11-26T14:04:53Z")

</div>

PSA: Careful with NPM today, Shai-Hulud is back and replicating itself across npm.

If you have shared secrets, or npm push access, refresh your tokens. If you’ve pushed to npm in the last day, recheck your dependencies.

Update: Here’s a couple of links to what’s going on with this and lists of what packages are affected:  
[shai-hulud-2-0-ongoing-supply-chain-attack](https://www.wiz.io/blog/shai-hulud-2-0-ongoing-supply-chain-attack)  
[shai-hulud-strikes-again-v2](https://socket.dev/blog/shai-hulud-strikes-again-v2)

Github CI/CD is the weak link here, outside of npm install scripts.

---

<div class="post-metadata">

**Author:** ![Deltakosh](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/deltakosh/32/26635_2.png) [@Deltakosh](https://forum.babylonjs.com/u/Deltakosh)\
**Post date:** [November 26, 2025, 3:41pm UTC](https://forum.babylonjs.com/t/npm-supply-chan-attack-again/61573/2 "2025-11-26T15:41:15Z")

</div>

Gosh..Thanks for the note!

---

<div class="post-metadata">

**Author:** ![ntech](https://avatars.discourse-cdn.com/v4/letter/n/e0b2c6/32.png) [@ntech](https://forum.babylonjs.com/u/ntech)\
**Post date:** [November 26, 2025, 4:11pm UTC](https://forum.babylonjs.com/t/npm-supply-chan-attack-again/61573/3 "2025-11-26T16:11:58Z")

</div>

NP. I have to keep up on it anyway - so when I see it I’ll msg if I’m around. Pretty important since we all use npm and it impacted over 12k packages and not small ones either.

---

<div class="post-metadata">

**Author:** ![ntech](https://avatars.discourse-cdn.com/v4/letter/n/e0b2c6/32.png) [@ntech](https://forum.babylonjs.com/u/ntech)\
**Post date:** [November 28, 2025, 1:25pm UTC](https://forum.babylonjs.com/t/npm-supply-chan-attack-again/61573/4 "2025-11-28T13:25:27Z")

</div>

Still an issue. I’ll update when I know it’s been cleared up.  
I would suggest that in the future to start eyeing deno as an alternative.

---

<div class="post-metadata">

**Author:** ![ntech](https://avatars.discourse-cdn.com/v4/letter/n/e0b2c6/32.png) [@ntech](https://forum.babylonjs.com/u/ntech)\
**Post date:** [December 10, 2025, 9:57pm UTC](https://forum.babylonjs.com/t/npm-supply-chan-attack-again/61573/5 "2025-12-10T21:57:26Z")

</div>

It only gets worse. Not 100% clear on the first, and now React + Next.js has a bad one. So, update your code and get the patches where possible. This is a shell vuln.

react CVE-2025-55182  
next.js CVE-2025-6478

This can affect any that are using React Server Components with App Routing. Including Vite. Make sure to update to latest and patch up.

> **[Cisco Security Advisory: Remote Code Execution Vulnerability in React and...](https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-react-flight-TYw32Ddb)**
>
> On December 3, 2025, the React team released a security advisory regarding a vulnerability, CVE-2025-55182, in the React server that could allow an unauthenticated, remote attacker to perform remote code execution on an affected device or system.
> For...

> **[Critical RSC Bugs in React and Next.js Allow Unauthenticated Remote Code...](https://thehackernews.com/2025/12/critical-rsc-bugs-in-react-and-nextjs.html)**
>
> Critical RSC flaws in React and Next.js enable unauthenticated remote code execution; users should update to patched versions now.

---

<div class="post-metadata">

**Author:** ![withADoveInOneHand](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/withadoveinonehand/32/1243_2.png) [@withADoveInOneHand](https://forum.babylonjs.com/u/withADoveInOneHand)\
**Post date:** [December 10, 2025, 10:05pm UTC](https://forum.babylonjs.com/t/npm-supply-chan-attack-again/61573/6 "2025-12-10T22:05:35Z")

</div>

shoutout to my gut for steering me clear of node ;p

---

<div class="post-metadata">

**Author:** ![ntech](https://avatars.discourse-cdn.com/v4/letter/n/e0b2c6/32.png) [@ntech](https://forum.babylonjs.com/u/ntech)\
**Post date:** [December 10, 2025, 10:11pm UTC](https://forum.babylonjs.com/t/npm-supply-chan-attack-again/61573/7 "2025-12-10T22:11:06Z")

</div>

It’s more of a community lunacy + laziness.. React’s issue, should never have happened. I mean they’re paid big bucks to tout themselves as super devs. They should’ve caught that they were allowing unvarnished access to page objects or worse with what they left open.
