WeSearch

Megalodon chums the waters in 5.5K+ GitHub repo poisonings

Jessica Lyons· ·4 min read · 0 reactions · 0 comments · 37 views
Megalodon chums the waters in 5.5K+ GitHub repo poisonings
TL;DR · WeSearch summary

A new malware campaign named Megalodon has compromised over 5,500 GitHub repositories by pushing malicious commits. This attack, which follows previous incidents like TeamPCP, targets CI/CD pipelines to steal sensitive credentials from cloud services. Experts warn that the ongoing wave of supply chain attacks poses significant risks to developers and companies using GitHub.

Key facts
How this story was covered

4 outlets in our directory ran this story, first to last over 41 hours. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.

Centre · 3
About this source

The Register publishes from United Kingdom and files mainly under tech. We currently carry 389 of its stories.

Original article
The Register · Jessica Lyons
Read full at The Register →

Story provenance

Source · retrieval · rights · ranking — open for full record
inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisherThe Register
Canonical URLhttps://www.theregister.com/security/2026/05/22/megalodon-chums-the-waters-in-55k-github-repo-poisonings/5245342
Publication timeFri, 22 May 2026 20:57:14 +0200
Retrieval time2026-05-22T19:07:02.752Z
Last seen2026-05-22T19:07:02.752Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Clusternes7P2FOwtJC · 4 stories
Cluster logicGrouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing May the item be indexed (stored, ranked, made findable)? Allowed
Snippet May a short excerpt of the publisher's text be shown? Allowed
AI summary May WeSearch generate its own short summary of the article? Limited
Retrieval / RAG May the content be exposed for third-party retrieval-augmented generation? Not asserted
Model training May the content be used to train AI models? Not asserted
Commercial reuse May the content be reused commercially? Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Opening excerpt (first ~120 words) tap to expand

(function() { let windowUrl = window.location.href; windowUrl = windowUrl.substring(windowUrl.indexOf('?') + 1); let messageElement = document.querySelector('.shareableMessage'); if (windowUrl && windowUrl.includes('code') && windowUrl.includes('expires')) { messageElement.style.display = 'block'; } })(); Security Megalodon chums the waters in 5.5K+ GitHub repo poisonings Will Jason Statham save us? Jessica Lyons Jessica Lyons Published fri 22 May 2026 // 19:57 UTC 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.Similar to the earlier TeamPCP attacks that poisoned about 3,800 GitHub repositories, this new campaign has so far infected 5,561 repos with CI/CD…

Excerpt limited to ~120 words for fair-use compliance. The full article is at The Register.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from The Register