Earlier quoted context omitted.
> on the other hand, the previous supply chain attack was found by automated tech. Are you sure about this? Would love to see which ones.
The chalk/debug one https://www.aikido.dev/blog/npm-debug-and-chalk-packages-com... I believe socket also found it this way just a bit later. The dev later said that Charlie notifying him probably shaved off some very important time for the remediation. So in this case 2 different companies found it using automated tech before anyone else
Shai-Hulud malware attack: Tinycolor and over 40 NPM packages compromised
991–1000 of 1001 posts
Re: Shai-Hulud malware attack: Tinycolor and over 40 NPM packages compromised
#992Earlier quoted context omitted.
> on the other hand, the previous supply chain attack was found by automated tech. Are you sure about this? Would love to see which ones.
The chalk/debug one https://www.aikido.dev/blog/npm-debug-and-chalk-packages-com... I believe socket also found it this way just a bit later. The dev later said that Charlie notifying him probably shaved off some very important time for the remediation. So in this case 2 different companies found it using automated tech before anyone else
There's no reason why Microsoft/npm can't do what we're doing, or any of the other handful to dozen companies that do similar things to us, to protect the supply chain.
Re: Shai-Hulud malware attack: Tinycolor and over 40 NPM packages compromised
#993Earlier quoted context omitted.
I don’t recall hearing about constant supply chain attacks with CPAN
Because it's never been considered an interesting target, compared to npm's reach?
Re: Shai-Hulud malware attack: Tinycolor and over 40 NPM packages compromised
#994This happens because there's no auditing of new packages or versions. The distro's maintainer and the developer is the same person. The general solution is to do what Debian does. Keep a stable distro where new packages aren't added and versions change rarely (security updates and bugfixes only, no new functionality). This is what most people use. Keep a testing/unstable distro where new packages and new versions can…
Finding the balance of that seems to me like it'd be incredibly difficult.
Re: Shai-Hulud malware attack: Tinycolor and over 40 NPM packages compromised
#995This happens because there's no auditing of new packages or versions. The distro's maintainer and the developer is the same person. The general solution is to do what Debian does. Keep a stable distro where new packages aren't added and versions change rarely (security updates and bugfixes only, no new functionality). This is what most people use. Keep a testing/unstable distro where new packages and new versions can…
This is a culture issue with developers who find it OK to have hundreds of (transitive) dependencies, and then follow processes that, for all intents and purposes, blindly auto update them, thereby giving hundreds of third-parties access to their build (or worse) execution environments. Adding friction to the sharing of code doesn't absolve developers from their decision to blindly trust a ridiculous amount of third-…
Doesn't this ultimately go all the way up to the top?
You have 2 devs: one who mostly writes their own code, only uses packages that are audited etc; the other uses packages willy nilly. Who do you think will be hired? Who do you think will be able to match the pace of development that management and executives demand?
Re: Shai-Hulud malware attack: Tinycolor and over 40 NPM packages compromised
#996I try to stay as far from web development as possible in my programming career (kernel/drivers and most recently reverse engineering) so maybe I'm ill-informed here but this npm thing seems to be uniquely terrible at security and i cannot fathom why the entire web seems to be automatically downloading updates from it and pushing them into production with no oversight. I've always worked at companies where we use thir…
Re: Shai-Hulud malware attack: Tinycolor and over 40 NPM packages compromised
#997Earlier quoted context omitted.
I can tell a lot about a dev by the fact that they single out npm/js for this supply chain issue.
Just more engineering leaning than you. Actual engineers have to analyze their supply chains, and so makes sense they would be baffled by NPM dependency trees that utterly normal projects grow into in the JavaScript ecosystem.
Most of my career Node.JS has paid the bills and I'm very grateful to fate for that; but I have also worked in C/asm/etc for embedded firmware etc. Implying that the JS ecosystem is only comprised of terrible devs is classic gatekeeping holier than thou type shit.
Re: Shai-Hulud malware attack: Tinycolor and over 40 NPM packages compromised
#998Earlier quoted context omitted.
Is the difference between the number of dev dependencies for eg. VueJs (a JavaScript library for marshalling Json Ajax responses into UI) and Htmx (a JavaScript library for marshalling html Ajax responses into UI) meaningful? There is a difference, but it's not an order of magnitude and neither is a true island. Granted, deciding not to use JS on the server is reasonable in the context of this article, but for the cl…
Except that htmx's recommended usage is as a single injected directly into your HTML page, not as an npm dependency. So unless you are an htmx contributor you are not going to be installing the dev dependencies.
Re: Shai-Hulud malware attack: Tinycolor and over 40 NPM packages compromised
#999Earlier quoted context omitted.
Lucky you. I keep coming back to it because jobs and even for desktop apps a native webview beats everything else. We fcked up with js, big time and its with us forever now
A webview doesn't beat anything for desktop apps. It is the worst option available.
A go desktop app rendered with OpenGL: 39MB starting size
So its smaller than Gpu rendered desktop app and I get to use CSS for styling which is very powerful