• NotSteve_@lemmy.ca
      link
      fedilink
      English
      arrow-up
      6
      arrow-down
      2
      ·
      19 days ago

      I don’t really see how it’s NPM at fault here. This was caused by a malicious actor taking control of an account and putting out bad packages on it. It could happen on any package repository for any language

      • davidgro@lemmy.world
        link
        fedilink
        English
        arrow-up
        6
        ·
        19 days ago

        My understanding is that for most package managers the signing keys are held by a smallish number of maintainers responsible for entire sections, who presumably keep those accounts pretty tightly secured. Not impossible to take over, but it’s a smaller attack surface.

        While for NPM as far as I know every uploader keeps their own account and there’s not even signing keys to lose control of.

        • hirihit640@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          3
          ·
          18 days ago

          I’ve heard quite a few PyPi and Cargo attacks though, but I bet the main reason why hear NPM so much is simply because NPM is the biggest, and thus the most valuable target

    • Fizz@lemmy.nz
      link
      fedilink
      English
      arrow-up
      5
      arrow-down
      2
      ·
      19 days ago

      I’m not familiar with npm but why is this always NPM? Is it a specific issue they have?

  • homes@piefed.world
    link
    fedilink
    English
    arrow-up
    11
    arrow-down
    1
    ·
    edit-2
    19 days ago

    One day, back in 1995, I could download every red hat package onto a series of 13 floppies.

    In fact, it was required if you wanted to install red hat. So was compiling them all onto your own computer.

    How far we’ve come