GitHub keeps removing malware-laced repositories, but thousands remain.
  • Jeena@jemmy.jeena.netEnglish
    171·
    9 months ago

    I planned to selfhost my own code repos forever, this gives me one more little push, but let’s see if I move it to my server.

    • surewhynotlem@lemmy.worldEnglish
      31·
      9 months ago

      To try and take over other people’s ci/cd pipelines and inject malware into otherwise legitimate application binaries.

    • phillaholic@lemm.eeEnglish
      10·
      9 months ago

      LastPass hack happened due to a developer logging I. On their home PV which had an outdated and vulnerable version of Plex installed. Swap outdated for “maliciously forked” and now attackers have legit code that can run for months before they use what they’ve injected to take over.

  • jwt@programming.devEnglish
    4·
    9 months ago

    I wonder how that seven layer obfuscation works in practice. the gif in the article shows an encrypted string being decrypted (with the decryption key right there in plain sight?) and executed, and I get they try to hide it by right aligning it with ~1000 spaces, but wouldn’t that still be super obvious in a git commit diff?

  • Hal-5700X@lemmy.worldEnglish
    230·
    9 months ago

    Don’t use forks of repositories. Why don’t GitHub restrict forking. What will solve the problem.