Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Cyborg)
  • No Skin
Collapse
Brand Logo

CIRCLE WITH A DOT

  1. Home
  2. Uncategorized
  3. https://safedep.io/megalodon-mass-github-repo-backdooring-ci-workflows/

https://safedep.io/megalodon-mass-github-repo-backdooring-ci-workflows/

Scheduled Pinned Locked Moved Uncategorized
20 Posts 8 Posters 2 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • cr0w@infosec.exchangeC cr0w@infosec.exchange

    @nyanbinary The API is giving me weird shit too. Shit that doesn't match my search query.

    nyanbinary@infosec.exchangeN This user is from outside of this forum
    nyanbinary@infosec.exchangeN This user is from outside of this forum
    nyanbinary@infosec.exchange
    wrote last edited by
    #11

    @cR0w do we have an IFIN thread for this? Just to know where I'll dump the results & code

    cr0w@infosec.exchangeC 1 Reply Last reply
    0
    • nyanbinary@infosec.exchangeN nyanbinary@infosec.exchange

      @cR0w do we have an IFIN thread for this? Just to know where I'll dump the results & code

      cr0w@infosec.exchangeC This user is from outside of this forum
      cr0w@infosec.exchangeC This user is from outside of this forum
      cr0w@infosec.exchange
      wrote last edited by
      #12

      @nyanbinary Not sure. I'm still dicking around with the search.

      nyanbinary@infosec.exchangeN cr0w@infosec.exchangeC 2 Replies Last reply
      0
      • cr0w@infosec.exchangeC cr0w@infosec.exchange

        @nyanbinary Not sure. I'm still dicking around with the search.

        nyanbinary@infosec.exchangeN This user is from outside of this forum
        nyanbinary@infosec.exchangeN This user is from outside of this forum
        nyanbinary@infosec.exchange
        wrote last edited by
        #13

        @cR0w lmao, just hit a 502 🙃

        cr0w@infosec.exchangeC 1 Reply Last reply
        0
        • nyanbinary@infosec.exchangeN nyanbinary@infosec.exchange

          @cR0w lmao, just hit a 502 🙃

          cr0w@infosec.exchangeC This user is from outside of this forum
          cr0w@infosec.exchangeC This user is from outside of this forum
          cr0w@infosec.exchange
          wrote last edited by
          #14

          @nyanbinary With less than 85% uptime, you're bound to hit some errors. 😆

          cr0w@infosec.exchangeC 1 Reply Last reply
          0
          • cr0w@infosec.exchangeC cr0w@infosec.exchange

            @nyanbinary With less than 85% uptime, you're bound to hit some errors. 😆

            cr0w@infosec.exchangeC This user is from outside of this forum
            cr0w@infosec.exchangeC This user is from outside of this forum
            cr0w@infosec.exchange
            wrote last edited by
            #15

            @nyanbinary I can start an IFIN thread if you haven't already.

            1 Reply Last reply
            0
            • cr0w@infosec.exchangeC cr0w@infosec.exchange

              @nyanbinary Not sure. I'm still dicking around with the search.

              cr0w@infosec.exchangeC This user is from outside of this forum
              cr0w@infosec.exchangeC This user is from outside of this forum
              cr0w@infosec.exchange
              wrote last edited by
              #16

              @nyanbinary https://discourse.ifin.network/t/megalodon-more-malicious-commits-on-github/487

              1 Reply Last reply
              0
              • azuaron@cyberpunk.lolA azuaron@cyberpunk.lol

                @cR0w "...but nobody reviews workflow files in npm packages."

                Ex-fucking-scuse me? That's an insane thing to not review.

                eschwartz@fosstodon.orgE This user is from outside of this forum
                eschwartz@fosstodon.orgE This user is from outside of this forum
                eschwartz@fosstodon.org
                wrote last edited by
                #17

                @Azuaron @cR0w I believe that that has gotten cause and effect reversed.

                It is "but nobody who makes npm packages reviews workflow files (or reviews anything else)".

                Or reworded, "people who don't review workflow files become npm developers". (There are, naturally, always exceptional cases.)

                🙂

                1 Reply Last reply
                0
                • cr0w@infosec.exchangeC cr0w@infosec.exchange

                  Some interesting info in a couple repos by @j0hnnyxm4s

                  Link Preview Image
                  Security: Repository tampered via my compromised credential — cleanup required (megalodon campaign) · Issue #44 · chicagolandmesh/chicagolandmesh.org

                  TL;DR: My account johnnyxmas was the target of a supply-chain credential-theft campaign. On 2026-05-18, the attacker used my compromised credential — which had push access to this repo as a collaborator — to push a malicious commit and r...

                  favicon

                  GitHub (github.com)

                  Link Preview Image
                  Security: Repository tampered via my compromised credential — cleanup required (megalodon campaign) · Issue #36 · Xyl2k/TSA-Travel-Sentry-master-keys

                  TL;DR: My account johnnyxmas was the target of a supply-chain credential-theft campaign. On 2026-05-18, the attacker used my compromised credential — which had push access to this repo as a collaborator — to push a malicious commit and r...

                  favicon

                  GitHub (github.com)

                  j0hnnyxm4s@infosec.exchangeJ This user is from outside of this forum
                  j0hnnyxm4s@infosec.exchangeJ This user is from outside of this forum
                  j0hnnyxm4s@infosec.exchange
                  wrote last edited by
                  #18

                  @cR0w yeah man that supply chain is a bitch. Npm update stole a PAT and went to town. Luckily it only matters if you’re dumb enough to store keys in your repo. Tried to be as descriptive as possible.

                  1 Reply Last reply
                  0
                  • huronbikes@cyberplace.socialH huronbikes@cyberplace.social

                    @Azuaron @cR0w I get what you are saying. There's a systemic issue with NPM and a normal-seeming project will have hundreds or thousands of transitive dependencies, and the system does little to provide any automated means of verification.

                    epic_null@infosec.exchangeE This user is from outside of this forum
                    epic_null@infosec.exchangeE This user is from outside of this forum
                    epic_null@infosec.exchange
                    wrote last edited by
                    #19

                    @huronbikes @Azuaron @cR0w That in itself seems insufficient. NPM takes dependencies in a way that makes it so a version update might not even be expected by the developer. (Yes, saving the package lock helps with this, but still.)

                    1 Reply Last reply
                    0
                    • cr0w@infosec.exchangeC cr0w@infosec.exchange

                      Link Preview Image
                      Megalodon: Mass GitHub Repo Backdooring via CI Workflows

                      Over 5,700 malicious commits were pushed to GitHub repositories on May 18, 2026, replacing GitHub Actions workflows with base64-encoded secret exfiltration payloads. The "megalodon" campaign targeted repos including Tiledesk (9 repos), Black-Iron-Project (8 repos), and hundreds of others. @tiledesk/tiledesk-server versions 2.18.6-2.18.12 on npm carry the backdoor. C2: 216.126.225.129:8443.

                      favicon

                      SafeDep - Real-time Open Source Software Supply Chain Security (safedep.io)

                      Anyone searching GitHub yet for these commits? It would be nice to see a full list of impacted projects.

                      5,700+ commits in six hours, 5,561 repositories, one payload: replace a GitHub Actions workflow with a dormant secret exfiltration backdoor. The workflow_dispatch trigger design means these backdoors sit silent until activated, creating no visible CI runs.

                      Tiledesk shows how repository compromise cascades to package registries. Seven npm versions carried the backdoor because the maintainer published from a poisoned repo. Application code: untouched. Only the workflow file changed. Code review would catch this, but nobody reviews workflow files in npm packages.

                      If your repository received a commit from build-system@noreply.dev or ci-bot@automated.dev on May 18, 2026: revert it, audit your workflow files, and rotate any secrets available to GitHub Actions runners. Check your Actions tab for unexpected workflow_dispatch runs. If you use OIDC federation for cloud deployments, review cloud audit logs for token requests from unknown workflow runs.

                      If you depend on @tiledesk/tiledesk-server: pin to version 2.18.5 or earlier until the repository is remediated. The malicious commit remains on the master branch as of this writing.

                      j0hnnyxm4s@infosec.exchangeJ This user is from outside of this forum
                      j0hnnyxm4s@infosec.exchangeJ This user is from outside of this forum
                      j0hnnyxm4s@infosec.exchange
                      wrote last edited by
                      #20

                      @cR0w It’s old news and not going away. Nobody is treating npm as what it has always been: the biggest malware repo since GitHub.

                      https://go.halcyon.ai/rs/401-WCH-435/images/Halcyon%20Cloudzy%20C2P%20Report.pdf?version=0

                      1 Reply Last reply
                      1
                      0
                      • R relay@relay.infosec.exchange shared this topic
                      Reply
                      • Reply as topic
                      Log in to reply
                      • Oldest to Newest
                      • Newest to Oldest
                      • Most Votes


                      • Login

                      • Login or register to search.
                      • First post
                        Last post
                      0
                      • Categories
                      • Recent
                      • Tags
                      • Popular
                      • World
                      • Users
                      • Groups