Earlier quoted context omitted.
Look like they realized the ramification and suddenly changed their payload. Well, that won't help them since companies who uses this module will have their legal department barking. They cannot erase the damage they have done and try to get away of the ramification with version. Since this is distributed through GitHub, Microsoft legal possibly will be involved due to possible violation of cyber/hacking laws in vari…
I don't see any issue for the developers at all. It is their software to create and alter as they see fit. End users choose to use the package, it is not being installed on their machines without their knowledge.
NPM package compromised by author: erases files on RU / BY computers on install
141–150 of 188 posts
Re: NPM package compromised by author: erases files on RU / BY computers on install
#142Earlier quoted context omitted.
Upto a court to decide. Turns out he's in California which has laws against writing and distributing malicious code. He's looking at state level: if charged as a misdemeanor, the crime is punishable by: imprisonment in county jail for up to one year, and/or a maximum fine of $5,000.6 If charged as a felony, the offense is punishable by: imprisonment for up to three years, and/or a maximum fine of $10,000.7 Federal ch…
Whats up with the .6 and .7?
Re: NPM package compromised by author: erases files on RU / BY computers on install
#143Earlier quoted context omitted.
This is the sad thing about all of this. Many people are demonizing average Russian citizens for the actions of their government. When the US invaded Iraq in 2003, I was very much against it, but felt powerless to change the course of my government. (And the US government kept on doing what it felt like, no matter how unjust its actions.) While I was ashamed of my country's actions, I didn't think it would be fair fo…
Majority of average Russian citizens support their goverment actions against Ukraine. So in my book, they are also responsible.
Re: NPM package compromised by author: erases files on RU / BY computers on install
#144The blast radius is monstrously giant. We seem to be still very naive in the way we approach, use, and implement those type of system, with an assumption that maintainers are working in good-faith and reliable.
I don’t know how things should be, and I don’t like to think of contributors and maintainers as a threat, but we have enough examples now to know ignore that risk is a fundamental issue.
Re: NPM package compromised by author: erases files on RU / BY computers on install
#145Honestly a very harmful sort of "doing something about it". As if deleting someone's (presumably, normal people) files will make them more understanding of the difficulties in the ongoing conflict. Lying about it is also petty, as seen below. Malicious software is malicious regardless of any intentions and should be prosecuted as such. And if one really feels obliged to make their part as they wish, there's many exam…
Re: NPM package compromised by author: erases files on RU / BY computers on install
#146Earlier quoted context omitted.
Majority of average Russian citizens support their goverment actions against Ukraine. So in my book, they are also responsible.
> Majority of average Russian citizens support their goverment actions against Ukraine They do. Now, will installing malware on their computers make them change their mind and support Ukraine instead?
Re: NPM package compromised by author: erases files on RU / BY computers on install
#147Earlier quoted context omitted.
>If they want to publish their upstream as malware, okay. I think you'll find that argument will not be very persuasive to a judge if the case is that the author of the software knowingly adds code in after people have integrated it into their systems that on purpose damages those systems. Intention will often carry weight, and no claiming of rights and purity and see I wrote here you can't do anything to me! is goin…
If you sign a contract stating that you get 10k and in return I get to destroy your property. A judge is not very likely to enforce the payment but state that I should not destroy your property “because obviously thats not something you would like” The license grants you usage but you agree to no responsibility for damages. You can’t cherry pick half of it, that defies the entire point of a license. The fact that you…
Re: NPM package compromised by author: erases files on RU / BY computers on install
#148Honestly a very harmful sort of "doing something about it". As if deleting someone's (presumably, normal people) files will make them more understanding of the difficulties in the ongoing conflict. Lying about it is also petty, as seen below. Malicious software is malicious regardless of any intentions and should be prosecuted as such. And if one really feels obliged to make their part as they wish, there's many exam…
At this point any damage to the Russian economy translates to Ukranian lives saved.
You should re-evaluate your simplistic mindset
Re: NPM package compromised by author: erases files on RU / BY computers on install
#149Honestly a very harmful sort of "doing something about it". As if deleting someone's (presumably, normal people) files will make them more understanding of the difficulties in the ongoing conflict. Lying about it is also petty, as seen below. Malicious software is malicious regardless of any intentions and should be prosecuted as such. And if one really feels obliged to make their part as they wish, there's many exam…
At this point any damage to the Russian economy translates to Ukranian lives saved.
Re: NPM package compromised by author: erases files on RU / BY computers on install
#150Earlier quoted context omitted.
>This incident sets a dangerous precedent in breaking a chain of trust that today's software development heavily relies on Such precedents should be set, we shouldn't be relying on that chain of trust (as clearly demonstrated here). Updates should be vetted, signed, etc. Fetching stuff random people push to npm is a recipe for disaster.
How are regular developers going to vet the literally 1000s of Node.js dependencies they rely on? And who's signing these updates? The package owner? Well, he's the one adding malicious code so he can sign whatever he wants. I'll say it again, Node.js needs a proper standard library like Go that takes care of common needs most people have. It's been improving but it was a historical mistake to let microdependencies r…
Perhaps they shouldn't be relying on thousands of NPM packages. It's not difficult to write JS code that doesn't `npm install` the entire package ecosystem.