node-ipc
peacenotwar
node-ipc | peacenotwar | |
---|---|---|
76 | 33 | |
42 | 155 | |
- | - | |
2.3 | 7.0 | |
8 months ago | over 1 year ago | |
JavaScript | JavaScript | |
MIT License | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
node-ipc
-
gotta admit, gadgetbridge is awesome!
It should be noted that when developers have the ability to upload packages themselves, there is no guarantee that what the user gets corresponds to the source code that is available. The malware in node-ipc is suspiciously absent from the published source repository which has the latest release in 2021. If you were pulling directly from the source code you would not have seen this. This is an issue with npm, not libre software or "open source."
- How far it's fallen. Bring back my dog.
- Any updates on Rust, and node ipc?
- Anonymous Takes Anti-Putin Battle to Russian People with Printer Attack to Disrupt Kremlin's Propaganda
- Embedded Malicious Code in node-ipc
- Commentary on the Node-IPC incident and open source supply chains
-
The authors of node-ipc have pushed malware in an update, which wipes your disk if you happen to have Russian or Belorussian IP address. This affects some large projects like Vue CLI where it is a dependency.
Direct link to the github discussion: https://github.com/RIAEvangelist/node-ipc/issues/233 (many comments have been removed)
-
Sabotage: Code added to popular NPM package wiped files in Russia and Belarus
Actually, to my knowledge, I was the very first person to discover the malware contained in the commit range of 847047cf7f81ab08352038b2204f0e7633449580 -> 6e344066a0464814a27fbd7ca8422f473956a803
-
On the Weaponisation of Open Source
From the article:
> I don’t think this can be classed as open source anymore:
> The definition of an Open Source License is quite clear:
> 5. No Discrimination Against Persons or Groups The license must not discriminate against any person or group of persons.
> I don’t really want to have to read through each of my dependencies and transitive dependencies licences to determine whether I am agreeing to discriminatory terms by using a library.
I think the author of the article has misunderstood the definition, thus reached the wrong conclusion.
The non-discrimination rule applies only to accessibility and nothing else. Simply put, you provide the same code/product to everybody, including Satan Claus and Mr Putin under the same set of condition and permissions. Adding/removing malicious code does not change the fact that the code is by definition open sourced.
All and all, this is not a license problem.
Now, talk about node-ipc, which just got attacked by mobs (see https://github.com/RIAEvangelist/node-ipc/issues?q=is%3Aissu...).
If an open source project is a scam, then it's a scamware. If an open source project is malicious, then it's a malware.
Personally, as a normal human being, it is hard to keep a peace of mind after watching how the Russians fired multiple heavy rounds to kill the elderly couple who just traveling peacefully in a car down the road near a hospital. It is even harder to keep a peace of mind after watching a video recorded by a son showing how the Russians shoot and killed his father who sits in the driver's seat right beside him. I fully understand and respect the anger.
However, I do agree that people need to be more mature on this even during this difficult time. Turn your project into a malware only hurts your own reputation and people who trusted you. Once the trust is gone, it might never recover. There are many ways to actually hurt those who contributed the invasion. Be constructive and accurate, or at very least don't be destructive.
- Open Source Maintainer Sabotages Code to Wipe Russian, Belarusian Computers
peacenotwar
-
Open Source Hacktivism, Open Source Gains Traction in the Enterprise, and More: Open Source Matters
Today, with an ongoing war between Russia and Ukraine, some open source maintainers have taken it upon themselves to protest the war via changes to their code that express anti-war rhetoric via messages that display when the software is run. However, one maintainer in particular took it to the next level. Brandon Nozaki Miller, published a library on GitHub named peacenotwar that simply printed an anti-war message to the computer it was run on. This package is harmless on its own, but things got interesting when he included this package as a dependency in the node-ipc module he maintains. Users who downloaded the latest version of node-ipc to a machine in Russia would be subject to complete data destruction. Miller defended the act by claiming that this is all documented publicly and that users who don’t want this installed on their machine should lock their dependencies to older versions.
-
node-ipc go brrrr
apparently an NGO working in belarus got affected
-
American NGO using node-ipc lost 30k files detailing war crimes
From that reddit thread, here is the github issue the paste originated from.
https://github.com/RIAEvangelist/peacenotwar/issues/45
-
Human Rights Organization in Ukraine was the victim of a malware attack by an "activist" targeting Russian and Belorusian IPs
the repo where this issue was posted simply created a .txt file on the user's machine, doesn't wipe anything: https://github.com/RIAEvangelist/peacenotwar/issues/45
-
Open Source Maintainer Sabotages Code to Wipe Russian, Belarusian Computers
This headline is fucking yikes, the node package that they're talking about is fully open source and does nothing but make a text file in 3 locations. It does nothing remotely close to "wiping" computers, lmfao.
-
BIG sabotage: Famous npm package (node-ipc) deletes files to protest Ukraine war
His actions destroyed over 30,000 messages & files detailing war crimes committed by Russian in Ukraine belonging an American NGO that monitors human rights infringements in eastern Europe. Cool protest, bro.
-
Un paquet npm compromis par l'auteur efface les fichiers sur les ordinateurs russes et biélorusses lors de l'installation, pour protester contre l'invasion de l'Ukraine par la Russie
Première victime collatérale
-
Developers of node-ipc edited the software so that anyone with a russian or belarusian IP would get their drive scrubbed clean of data, drama ensues.
Links to drama: https://github.com/RIAEvangelist/peacenotwar/issues, https://github.com/RIAEvangelist/node-ipc/issues
-
My entire PC got wiped Do not download
The package uses https://github.com/RIAEvangelist/peacenotwar to deliver the message.
But I don't understand why/how it would wipe the PC. Unless I missed something, the code from the package does not delete anything.
> This code serves as a non-destructive example of why controlling your node modules is important. It also serves as a non-violent protest against Russia's aggression that threatens the world right now.
Nah, the author knew it's would be controversial. The first sentence is there as an excuse.
- Node-ipc supply chain attack: peacenotwar
What are some alternatives?
vue-cli - 🛠️ webpack-based tooling for Vue.js Development
es5-ext - ECMAScript extensions (with respect to upcoming ECMAScript features)
Flow.Launcher - :mag: Quick file search & app launcher for Windows with community-made plugins
protestware-list
create-vue - 🛠️ The recommended way to start a Vite-powered Vue project
cargo-crev - A cryptographically verifiable code review system for the cargo (Rust) package manager.
node-ipc-dependencies-list - List of all dependencies affected by node-ipc malicious commit
npm
worldle
tiny-http - Low level HTTP server library in Rust