{"id":599171,"date":"2026-05-23T03:54:10","date_gmt":"2026-05-23T03:54:10","guid":{"rendered":"https:\/\/www.newsbeep.com\/uk\/599171\/"},"modified":"2026-05-23T03:54:10","modified_gmt":"2026-05-23T03:54:10","slug":"megalodon-chums-the-waters-in-5-5k-github-repo-poisonings","status":"publish","type":"post","link":"https:\/\/www.newsbeep.com\/uk\/599171\/","title":{"rendered":"Megalodon chums the waters in 5.5K+ GitHub repo poisonings"},"content":{"rendered":"<p class=\"kicker \" style=\"\">Security<\/p>\n<p class=\"subtitle \" style=\"\">Will\u00a0Jason Statham save us?<\/p>\n<p>A malware-spreading scumbag swimming through GitHub pushed malicious commits to more than 5,500 repositories on Monday as part of an automated campaign called Megalodon.<\/p>\n<p>Similar to the earlier <a href=\"https:\/\/www.theregister.com\/devops\/2026\/05\/20\/github-says-internal-repos-exfiltrated-after-poisoned-vs-code-extension-attack\/5243206\" rel=\"nofollow noopener\" target=\"_blank\">TeamPCP attacks<\/a> that poisoned about 3,800 GitHub repositories, this new campaign has so far infected 5,561 repos with CI\/CD credential-stealing malware, according to SafeDep researchers, who uncovered the predatory commits and published a <a href=\"https:\/\/safedep.io\/megalodon-mass-github-repo-backdooring-ci-workflows\/#full-list-of-compromised-github-repositories\" rel=\"nofollow noopener\" target=\"_blank\">full list of the compromised repositories<\/a>.<\/p>\n<p>If a repository owner merges the commit, the malware executes inside their CI\/CD pipeline and propagates further, Ox Security lead researcher Moshe Siman Tov Bustan <a href=\"https:\/\/www.ox.security\/blog\/megalodon-cicd-malware-github\/\" rel=\"nofollow noopener\" target=\"_blank\">said<\/a> in a Thursday blog post.<\/p>\n<p>Megalodon steals AWS secret keys and Google Cloud access tokens. It also queries AWS, Google Cloud Platform, and Azure metadata for instance role credentials, reads SSH private keys, Docker and Kubernetes configurations, Vault tokens, Terraform credentials, and scans source code for more than 30 secret regex patterns. Then it exfiltrates GitHub tokens, including secrets used to authenticate with cloud providers, thus allowing attackers to impersonate developers\u2019 cloud identities, along with Bitbucket tokens.<\/p>\n<p>In other words: consider ALL of your CI\/CD variables pwned.<\/p>\n<p>&#8220;We\u2019ve entered a new supply chain attack era, and TeamPCP compromising GitHub was only the beginning,\u201d Bustan told The Register. \u201cWhat\u2019s coming next is an endless wave, a tsunami of cyber attacks on developers worldwide.\u201d<\/p>\n<p>Plus, he added, hacking GitHub \u201ccompromises the security of every company with a private repository hosted on the platform.\u201d<\/p>\n<p>            Malicious code is still reaching their servers, and nothing is stopping it before it does<\/p>\n<p>This new wave of supply chain attacks hitting developers\u2019 environments won\u2019t stop until \u201ccompanies like npm and GitHub take serious action against the spread of malicious code on their servers,\u201d Bustan said.<\/p>\n<p>He noted npm\u2019s statement on X saying it \u201cinvalidated npm granular access tokens with write access that bypass 2FA\u201d to prevent additional supply-chain attacks like <a href=\"https:\/\/www.theregister.com\/cyber-crime\/2026\/05\/18\/shai-hulud-copycat-hits-another-npm-package\/5242180\" rel=\"nofollow noopener\" target=\"_blank\">Mini Shai Hulud<\/a>.<\/p>\n<p>\u201cThat could help a little with account hijacking, but it doesn\u2019t solve the actual problem,\u201d Bustan said. \u201cMalicious code is still reaching their servers, and nothing is stopping it before it does.\u201d<\/p>\n<p>npm \u2026 but not TeamPCP<\/p>\n<p>SafeDep spotted Megalodon hidden inside a legitimate package: <a href=\"https:\/\/www.tiledesk.com\/\" rel=\"nofollow noopener\" target=\"_blank\">Tiledesk<\/a>, an open source live chat and chatbot platform. The attacker backdoored versions 2.18.6 (May 19) through 2.18.12 (May 21), and the same npm maintainer published the last clean version, 2.18.5, before unknowingly publishing these newer compromised versions.\u00a0<\/p>\n<p>\u201cThe attacker never touched the npm account,\u201d the open source supply-chain security startup researchers <a href=\"https:\/\/safedep.io\/megalodon-mass-github-repo-backdooring-ci-workflows\/\" rel=\"nofollow noopener\" target=\"_blank\">said<\/a>. \u201cThey compromised the <a href=\"https:\/\/github.com\/Tiledesk\/tiledesk-server\" rel=\"nofollow noopener\" target=\"_blank\">GitHub repository<\/a>, and the maintainer published from the poisoned source without realizing it.\u201d<\/p>\n<p>While publishing <a href=\"https:\/\/www.theregister.com\/security\/2026\/03\/31\/top-npm-package-backdoored-to-drop-dirty-rat-on-dev-machines\/5219910\" rel=\"nofollow noopener\" target=\"_blank\">malicious packages on npm<\/a> is a <a href=\"https:\/\/www.theregister.com\/cyber-crime\/2026\/05\/18\/shai-hulud-copycat-hits-another-npm-package\/5242180\" rel=\"nofollow noopener\" target=\"_blank\">TeamPCP signature move<\/a>, Bustan said there\u2019s no threat-intel or code-analysis evidence that connects Megalodon to the crew behind the <a href=\"https:\/\/www.theregister.com\/security\/2026\/03\/24\/litellm-infected-with-credential-stealing-code-via-trivy\/5223422\" rel=\"nofollow noopener\" target=\"_blank\">Trivy<\/a>, <a href=\"https:\/\/www.theregister.com\/devops\/2026\/05\/11\/checkmarx-tackles-another-teampcp-intrusion-as-jenkins-plugin-sabotaged\/5237780\" rel=\"nofollow noopener\" target=\"_blank\">Checkmarx<\/a>, and other <a href=\"https:\/\/www.theregister.com\/security\/2026\/05\/15\/openai-caught-in-tanstack-npm-supply-chain-chaos-after-employee-devices-compromised\/5241019\" rel=\"nofollow noopener\" target=\"_blank\">recent supply-chain attacks<\/a>. \u201cOur best guess now is that it&#8217;s a different threat actor copying their behavior and style, but not much of the code itself,\u201d he told us.<\/p>\n<p>And despite <a href=\"https:\/\/www.theregister.com\/security\/2026\/05\/13\/malware-crew-teampcp-open-sources-its-shai-hulud-worm-on-github\/5239319\" rel=\"nofollow noopener\" target=\"_blank\">TeamPCP open sourcing<\/a> its Shai-Hulud worm and announcing a supply-chain attack competition on BreachForums, Ox doesn\u2019t believe Megalodon is a contest entry.<\/p>\n<p>\u201cWe have indications that they are not participating in the TeamPCP contest due to the contest having a specific rule to add a public encryption key that the actor behind the malware could match with his private key to prove his involvement,\u201d Bustan said.<\/p>\n<p>Who is built-bot?<\/p>\n<p>SafeDep\u2019s threat hunters traced the malicious commit (<a href=\"https:\/\/github.com\/Tiledesk\/tiledesk-server\/commit\/acac5a9854650c4ae2883c4740bf87d34120c038\" rel=\"nofollow noopener\" target=\"_blank\">acac5a9<\/a>) to an author \u201cbuild-bot,\u201d connected to the email address build-system[@]noreply.dev with the message \u201cci: add build optimization step.\u201d<\/p>\n<p>The author name and noreply email mimic automated CI commits, and there\u2019s no GitHub account linked to the author and committer user fields. \u201cSomeone pushed the commit to master with no PR and no merge commit, using a compromised PAT or deploy key,\u201d according to the researchers.\u00a0<\/p>\n<p>They searched GitHub for other commits authored by the same email address and found 2,878 results, plus a second email, ci-bot@automated.dev, with an additional 2,841 commits. All landed May 18 during a six-hour window (11:36 to 17:48 UTC) and targeted 5,561 repositories.<\/p>\n<p>This includes nine compromised Tiledesk repositories: tiledesk-server, tiledesk-dashboard, tiledesk-telegram-connector, tiledesk-llm, tiledesk-docker-proxy, tiledesk-community-app, tiledesk-campaign-dashboard, tiledesk-helpcenter-template, and tiledesk-ai. Others include Black-Iron-Project with eight compromised repos, WISE-Community, and hundreds of smaller repositories. \u00ae<\/p>\n","protected":false},"excerpt":{"rendered":"Security Will\u00a0Jason Statham save us? A malware-spreading scumbag swimming through GitHub pushed malicious commits to more than 5,500&hellip;\n","protected":false},"author":2,"featured_media":599172,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[84,59,56,54,55],"class_list":["post-599171","post","type-post","status-publish","format-standard","has-post-thumbnail","category-business","tag-business","tag-gb","tag-uk","tag-united-kingdom","tag-unitedkingdom"],"_links":{"self":[{"href":"https:\/\/www.newsbeep.com\/uk\/wp-json\/wp\/v2\/posts\/599171","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.newsbeep.com\/uk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.newsbeep.com\/uk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.newsbeep.com\/uk\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.newsbeep.com\/uk\/wp-json\/wp\/v2\/comments?post=599171"}],"version-history":[{"count":0,"href":"https:\/\/www.newsbeep.com\/uk\/wp-json\/wp\/v2\/posts\/599171\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.newsbeep.com\/uk\/wp-json\/wp\/v2\/media\/599172"}],"wp:attachment":[{"href":"https:\/\/www.newsbeep.com\/uk\/wp-json\/wp\/v2\/media?parent=599171"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.newsbeep.com\/uk\/wp-json\/wp\/v2\/categories?post=599171"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.newsbeep.com\/uk\/wp-json\/wp\/v2\/tags?post=599171"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}