3 ms·

This doesn't really have anything to do with npm.

• vitamark 5mo ago
  anything except that it's malware installed via npm
  • Retr0id 5mo ago
    As you can see here, they've already switched it out for a different command, likely due to incident responders over-indexing on npm as an IOC. https://news.ycombinator.com/item?id=48503258 https://news.ycombinator.com/item?id=48503258
• notabotiswear 5mo ago
  From the Arch mailing list [0] >The result is a rather long list of ~408 packages all doing npm install atomic-lockfile something something [0] https://lists.archlinux.org/archives/list/aur-general@lists.archlinux.org/message/ALAZHW5PJJUJTT5ICIHDXB6AKSICZ6MA/ https://lists.archlinux.org/archives/list/aur-general@lists....
  • Retr0id 5mo ago
    They could've pip installed, curl|sh'd or anything else, it's not relevant to the underlying issue.
    • notabotiswear 5mo ago
      Perhaps there were other vectors, but npm was the one used here. And yes, this is an AUR issue, but npm being used to host and dissiminate malware is also [a chronic] one, even if separate.