Live data from Hacker News

Mini Shai-Hulud Strikes Again: 314 npm Packages Compromised

safedep.io

161–170 of 329 posts

Re: Mini Shai-Hulud Strikes Again: 314 npm Packages Compromised

#161
post #65

‘No way to prevent this’, Says Only Development Community Where This Regularly Happens ­— https://itnext.io/no-way-to-prevent-this-says-only-developme... >

after running the original version of this into the ground we can run this one into the ground too

Re: Mini Shai-Hulud Strikes Again: 314 npm Packages Compromised

#162
post #106
post #91

I can't wait for npm/github to do literally anything at all to mitigate these attacks. Literally anything. Have we considered a basic WAF-style block on some postinstall script strings? LLM-assisted code scanning on publish? Is there anyone home? No I suspect not.

Third parties can detect compromised packages. It’s ridiculous Microsoft doesn’t.

Why would a corporate company actually demonstrate responsibility and ethicality in its use of the open source commons from which it extracts every last penny and dollar?

Edit: a more suitable strategy is to do the minimal necessary actions for appearance purposes only, as its how to focus and optimize on its interest for revenue for its shareholders.

Re: Mini Shai-Hulud Strikes Again: 314 npm Packages Compromised

#163

What would be the required budget to host an alternative registry? I'm surprised any GAFAM still hasn't stepped-in and started building their alternative, at least for NPM to up its game in order not to become completely irrelevant.

at amazon, they maintain a private internal registry of packages with approved licenses and audits. this has been in place for several years. i assume other big corps enforce similar policies

Re: Mini Shai-Hulud Strikes Again: 314 npm Packages Compromised

#164
post #65

‘No way to prevent this’, Says Only Development Community Where This Regularly Happens ­— https://itnext.io/no-way-to-prevent-this-says-only-developme... >

Language exclusive package managers like this are nightmares for security, but npm simply does things so poorly I feel like they wanted something insecure.

What about language exclusivity makes a package manager a security nightmare?

Re: Mini Shai-Hulud Strikes Again: 314 npm Packages Compromised

#165
post #164

Earlier quoted context omitted.

Language exclusive package managers like this are nightmares for security, but npm simply does things so poorly I feel like they wanted something insecure.

What about language exclusivity makes a package manager a security nightmare?

Now I have to wonder if someone is targeting Homebrew too, thanks

Re: Mini Shai-Hulud Strikes Again: 314 npm Packages Compromised

#167

> 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?

The joys of running podman/docker on macOS: you can't help but run it in a hypervisor.

Re: Mini Shai-Hulud Strikes Again: 314 npm Packages Compromised

#168

> In regards to the whole ecosystem: TC39 should take a look into adding a better standard library to JS itself, which would reduce the amount of one-liner packages. I concur, the best part of working with Deno way back was its standard library [0] and overall complete dev environment. It is just so damn obvious that a runtime comes with an integrated test runner and assertion library. 0 - https://docs.deno.com/runti…

I'm not sure any of the packages here would be part of a "better standard library".

Do any language standard libraries have a "3 hours ago" formatter? Thats what timeago.js does

Maybe slice.js, which just does python-style indexing with negative numbers. TC39 already made array.at() and array.slice() handle negative numbers.

Re: Mini Shai-Hulud Strikes Again: 314 npm Packages Compromised

#169
post #65

‘No way to prevent this’, Says Only Development Community Where This Regularly Happens ­— https://itnext.io/no-way-to-prevent-this-says-only-developme... >

The "No way to prevent this" analogies seem to me to work better for Memory Safety because, as with Gun Safety, the simple fact is that everybody knows how to solve the problem, but one group insists it's impossible. There is crowing from the "Actually copy-paste is better" people when this happens, but when it's their turn they just jam their fingers in their ears. The memory safety and gun safety problems are the a…

>The "No way to prevent this" analogies seem to me to work better for Memory Safety because, as with Gun Safety, the simple fact is that everybody knows how to solve the problem, but one group insists it's impossible.

I'm not following. Whats the 2nd Amendment equivalent for memory safety? The amount of C/C++ in production or something?

Re: Mini Shai-Hulud Strikes Again: 314 npm Packages Compromised

#170
post #163

What would be the required budget to host an alternative registry? I'm surprised any GAFAM still hasn't stepped-in and started building their alternative, at least for NPM to up its game in order not to become completely irrelevant.

at amazon, they maintain a private internal registry of packages with approved licenses and audits. this has been in place for several years. i assume other big corps enforce similar policies

If your company not running an internal proxy at minimum you're stupid - you have no audit function for what libraries are being pulled.
Post reply on HN