Grafana Labs admits all its codebase are belong to someone who popped its GitHub account
Grafana Labs has reported that an attacker accessed its GitHub repository and stole its codebase. The company has stated that no customer data was compromised and has decided not to pay a ransom demanded by the attacker. Grafana believes it has identified the source of the security breach and has taken steps to enhance its security measures.
- ▪An attacker accessed Grafana Labs' GitHub repository and stole its codebase.
- ▪Grafana Labs confirmed that no customer data was stolen and there was no impact on operations.
- ▪The company has decided not to pay the ransom demanded by the attacker.
The Register publishes from United Kingdom and files mainly under tech. We currently carry 394 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
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 | The Register |
| Canonical URL | https://www.theregister.com/cyber-crime/2026/05/18/grafana-labs-admits-attackers-downloaded-its-codebase-from-github/5241686 |
| Publication time | Mon, 18 May 2026 07:46:31 +0200 |
| Retrieval time | 2026-05-18T06:39:56.075Z |
| Last seen | 2026-05-18T06:39:56.075Z |
| 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 | sMeG1lHSGVFM |
| 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)
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'; } })(); Cyber-Crime Grafana Labs admits all its codebase are belong to someone who popped its GitHub account No customer info stolen, no impact to operations, and no blackmail payment Simon Sharwood Simon Sharwood APAC Editor Published mon 18 May 2026 // 06:46 UTC Observability outfit Grafana Labs has revealed that an attacker accessed its GitHub repository and stole its codebase.In social media posts the company blamed the situation on an “unauthorized party” who was somehow able to obtain a…
Excerpt limited to ~120 words for fair-use compliance. The full article is at The Register.
Discussion
0 commentsMore from The Register
