Grafana says hackers hit its GitHub environment, demand ransom to prevent codebase release — but it's refusing to pay

https://www.techradar.com/author/sead-fadilpai· May 18, 2026 · 1:05 PM UTC ·10 min read · 0 reactions · 0 comments · 42 views

#cybersecurity #hacking #grafana #ransomware #github

TL;DR · WeSearch summary

Grafana has reported a security breach in its GitHub environment, where hackers accessed its codebase using a stolen token. The company confirmed that no customer data was compromised and has taken steps to enhance security measures. Despite the attackers demanding a ransom, Grafana has chosen not to engage with them and is cooperating with the FBI.

Key facts

▪Grafana's GitHub environment was compromised by hackers using a stolen access token.
▪The company confirmed that no customer data or systems were affected by the breach.
▪The attackers, identified as CoinbaseCartel, attempted to extort Grafana for the stolen codebase.

How this story was covered

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

Centre · 1

▪ Grafana says hackers have accessed its GitHub environment and demanded a ransom to prevent the release of its codebase; Grafana refused to pay (The Hacker News) — Techmeme

About this source

TechRadar publishes from United Kingdom and files mainly under tech. We currently carry 1,506 of its stories.

All TechRadar coverage →

Original article

TechRadar · https://www.techradar.com/author/sead-fadilpai

Read full at TechRadar →

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 publisher	TechRadar
Canonical URL	https://www.techradar.com/pro/security/grafana-says-hackers-hit-its-github-environment-demand-ransom-to-prevent-codebase-release-but-its-refusing-to-pay
Publication time	Mon, 18 May 2026 13:05:00 +0000
Retrieval time	2026-05-18T13:09:56.462Z
Last seen	2026-05-18T13:09:56.462Z
Headline source	Publisher (no WeSearch rewrite)
Excerpt source	publisher body
Excerpt method	First ~120 words (~800 chars) of extracted publisher body, fair-use limited.
Summary	WeSearch · cerebras-chat (WeSearch summarizer)
Summary source text	contentText
Citation coverage	Summary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Cluster	ZeBt7mPRA4Lg · 2 stories
Cluster logic	Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reason	Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visit	Yes — 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.

Open original publisher → Source rights JSON → Machine-readable provenance → Rights framework → WESEARCH-STORY-PROVENANCE-V1

Opening excerpt (first ~120 words) tap to expand

Pro Security Grafana says hackers hit its GitHub environment, demand ransom to prevent codebase release — but it's refusing to pay News By Sead Fadilpašić published 18 May 2026 CoinbaseCartel somehow obtained an access token When you purchase through links on our site, we may earn an affiliate commission. Here’s how it works. (Image credit: Avast) Copy link Facebook X Whatsapp Reddit Pinterest Flipboard Threads Email Share this article 0 Join the conversation Follow us Add us as a preferred source on Google Newsletter Subscribe to our newsletter Grafana confirms its GitHub environment was accessed with a stolen token and its codebase exfiltratedMaintainers stressed no customer data or systems were impacted and security measures were reinforcedA group called CoinbaseCartel claimed…

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

Anonymous · no account needed

Discussion

0 comments