u/endor_robert

Supply-chain alert: Tensorlake npm package hit by the Shai-Hulud worm.

​

Supply-chain alert: Tensorlake npm package hit by the Shai-Hulud worm. The popular Tensorlake SDK (part of a project with 1,000+ GitHub stars) shipped a poisoned release - version 0.5.144 - infected with the self-propagating Shai-Hulud worm.

The malicious version was published through the project's legitimate GitHub Actions release pipeline, complete with valid SLSA provenance. The attacker poisoned main first, then let the trusted pipeline do the rest.

This is a well-known Shai-Hulud pattern which a single, simple YARA rule flags in milliseconds. In fact a basic rule matched it on the first pass in our own pipeline. If npm, Inc. GitHub ran even a basic YARA scan on packages before publishing, most of these campaigns would be stopped before a single developer is infected. As Al speeds up how fast we ship, we're pulling in dependencies faster than anyone can audit them. Registries like npm sit at the chokepoint, and a basic malware-signature gate at publish time is the lowest bar we should expect.

0.5.144 has been removed from npm and version 0.5.143 is clean. If you installed 0.5.144, rotate every credential reachable from that machine, now.

reddit.com
u/endor_robert — 7 days ago
▲ 31 r/npm+1 crossposts

Avoiding the next NPM worm.

I'm sure many of you will have seen the latest keyv / cachable compromise and worm-spread, now affecting over 350 packages. This isn't the first, and it won't be the last. The affected packages will steal and exfiltrate any secrets/credentials they can find, which is probably not what you want to happen.

There are several commercial solutions to help protect against this, but if you just add to .npmrc in your repo root:

min-release-age=7d

(or some value you feel comfortable with)

It will block a lot of malware, which is usually discovered within a few hours.

endorlabs.com
u/endor_robert — 2 months ago