In the fictional universe of William Gibson's Sprawl trilogy, it is legal and normal for defenders to go kinetic on cyberattackers. How long until it is simply easier for governments and big business in the countries victimised by these criminal groups, to find the path of least resistance and go after them personally?
Mini Shai-Hulud Strikes Again: 314 npm Packages Compromised
61–70 of 329 posts
Re: Mini Shai-Hulud Strikes Again: 314 npm Packages Compromised
#62Another supply chain attack found and blocked in a day. Everyone regularly using npm to install new packages should be using npm's min-release-age setting to avoid package versions that are newer than a few days old to avoid most attacks in practice like this. You can set it to two days with `npm config set min-release-age=2` for example. https://cooldowns.dev/ has info about equivalent settings in other dependency m…
Re: Mini Shai-Hulud Strikes Again: 314 npm Packages Compromised
#63One solution I haven’t seen recommended much is to have a Claude instruction/skill that explicitly audits the diff of every upgrade, and force this manual audit as part of your upgrade workflow. This seems like it would work pretty reliably.
Re: Mini Shai-Hulud Strikes Again: 314 npm Packages Compromised
#64Re: Mini Shai-Hulud Strikes Again: 314 npm Packages Compromised
#65— https://itnext.io/no-way-to-prevent-this-says-only-developme...>
Re: Mini Shai-Hulud Strikes Again: 314 npm Packages Compromised
#66> Docker Container Escape > The payload checks for the Docker socket and, if present, attempts container escape through three sequential methods: So even if you're running devcontainers / VMs, these worms are already trying to escape. Make sure you're running a rootless VM engine (e.g. podman instead of docker) !
Why not run a proper virtual machine?
Re: Mini Shai-Hulud Strikes Again: 314 npm Packages Compromised
#67I spent a week with claude and codex re-implementing several packages which had dependency trees deeper than I would like.
Most of these packages are trivial to clone.
"But now you're not getting the upstream fixes" they will say.
"So what?" I reply
Re: Mini Shai-Hulud Strikes Again: 314 npm Packages Compromised
#68At this point I would very much like to get off Mr Bones' Wild Ride but I fear this is going to continue to happen because, from my own exploration at least, a large number of commercial detection strategies are directed at the repo/device/developer level when loading/using a package. This seems analogous to how we tackle email spam and general malware. It means that there is almost always a target valuable enough fo…
Wondering about Mr Bones' Wild Ride and suspecting it might be a reference to the 1991 movie Nothing But Trouble I took a look, and found I had remembered it wrong. The roller coaster in that movie was called Mr Bonestripper, https://www.youtube.com/watch?v=NEZEgd8GjJc . Instead it comes from Roller Coaster Tycoon 2, https://knowyourmeme.com/memes/mr-bones-wild-ride . As for the comparison with spam, there we kind of…
Re: Mini Shai-Hulud Strikes Again: 314 npm Packages Compromised
#69‘No way to prevent this’, Says Only Development Community Where This Regularly Happens — https://itnext.io/no-way-to-prevent-this-says-only-developme... >
Re: Mini Shai-Hulud Strikes Again: 314 npm Packages Compromised
#70Vendor your dependencies, clone or port them where needed, and freeze them. Most good packages these days do not have a deep dependency tree, and we should stop using the ones that do. I spent a week with claude and codex re-implementing several packages which had dependency trees deeper than I would like. Most of these packages are trivial to clone. "But now you're not getting the upstream fixes" they will say. "So…