Storia in 8 fonti

Grafana says stolen GitHub token let hackers steal codebase

Grafana Labs disclosed that hackers have downloaded its source code after breaching its GitHub environment using a stolen access token.

Raccontata da

Confronto fonti

6 prospettive sulla stessa storia

AI · summaries

bleepingcomputer.comStai leggendo3 mesi fa

Grafana says stolen GitHub token let hackers steal codebase

Grafana Labs disclosed that hackers have downloaded its source code after breaching its GitHub environment using a stolen access token.

originale

Timeline cronologica

domenica 17 maggio 2026·thehackernews.com
Grafana GitHub Token Breach Led to Codebase Download and Extortion Attempt
Grafana disclosed an unauthorized party accessed its GitHub environment and downloaded its codebase via a token.
lunedì 18 maggio 2026·theregister.com
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

siliconrepublic.com

3 mesi fa

Hackers access GitHub, download codebase in Grafana Labs breach

The recent Grafana labs hack has been confirmed by the organisation, with the company refusing to comply with ransom demands.

Leggi questa versione → originale

thehackernews.com3 mesi fa

Grafana GitHub Token Breach Led to Codebase Download and Extortion Attempt

Grafana disclosed an unauthorized party accessed its GitHub environment and downloaded its codebase via a token.

Leggi questa versione → originale

thenextweb.com3 mesi fa

Grafana Labs refuses ransom after hackers steal already-open-source code

Grafana Labs has disclosed that hackers stole its source code via a compromised GitHub token and demanded a ransom.

Leggi questa versione → originale

theregister.com3 mesi fa

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

Leggi questa versione → originale

techcrunch.com3 mesi fa

Open source tool maker Grafana Labs says hackers stole its code, refuses to pay ransom | TechCrunch

The open source project said hackers stole its codebase and threatened to publish its source code if the company did not pay.

Leggi questa versione → originale

lunedì 18 maggio 2026·

siliconrepublic.com

Hackers access GitHub, download codebase in Grafana Labs breach

The recent Grafana labs hack has been confirmed by the organisation, with the company refusing to comply with ransom demands.

lunedì 18 maggio 2026·

techcrunch.com

Open source tool maker Grafana Labs says hackers stole its code, refuses to pay ransom | TechCrunch

The open source project said hackers stole its codebase and threatened to publish its source code if the company did not pay.

lunedì 18 maggio 2026·

bleepingcomputer.com

Grafana says stolen GitHub token let hackers steal codebase

Grafana Labs disclosed that hackers have downloaded its source code after breaching its GitHub environment using a stolen access token.

lunedì 18 maggio 2026·

thenextweb.com

Grafana Labs refuses ransom after hackers steal already-open-source code

Grafana Labs has disclosed that hackers stole its source code via a compromised GitHub token and demanded a ransom.

martedì 19 maggio 2026·

heise.de

Cyberangriff Grafana: Erpresser kopieren Codebasis und drohen mit Leak

Bei Grafana Labs gab es einen IT-Sicherheitsvorfall. Dabei konnten Angreifer interne Daten kopieren. Nun fordern sie Lösegeld.

mercoledì 20 maggio 2026·

thehackernews.com

Grafana GitHub Breach Exposes Source Code via TanStack npm Attack

Grafana GitHub breach stemmed from TanStack npm attack; missed token exposed repos, not customer production systems.

mercoledì 20 maggio 2026·

dev.to

Grafana’s GitHub Token Incident: 5 Steps DevOps Teams Can Take to Recover Faster

If the recent Grafana Labs GitHub token incident caught your attention, it should. A compromised...

mercoledì 20 maggio 2026·

bleepingcomputer.com

Grafana breach caused by missed token rotation after TanStack attack

The Grafana data breach was caused by a single GitHub workflow token that slipped through the rotation process following the TanStack npm supply-chain attack last week.