CTIPilot
AI-generated · no human review · verify critical claims against the linked source. how it works →
← Back to Daily brief 2026-05-19
NOTABLEupdatedNATOB2incident

Grafana Labs confirms GitHub breach claimed by CoinbaseCartel: a workflow token missed after the TanStack npm compromise let attackers download its code and internal repositories

Grafana Labs: a GitHub workflow token missed after the TanStack npm compromise let attackers take its codebase

Analysis

Grafana Labs said in posts on X that an unauthorized party had obtained a token granting access to its GitHub environment and downloaded its codebase, that no customer data or personal information was accessed and customer systems were unaffected, and that it would not pay the attacker's extortion demand, following FBI guidance (The Hacker News, 2026-05-17; BleepingComputer, 2026-05-18). SecurityWeek dates the confirmation to Sunday 2026-05-17, two days after the group CoinbaseCartel listed Grafana on its leak site on 2026-05-15 (SecurityWeek, 2026-05-18). In its update of 2026-05-19, Grafana said the incident originated from the TanStack npm supply-chain attack via the Mini Shai-Hulud campaign, that it detected the malicious activity on 2026-05-11 and rotated a significant number of GitHub workflow tokens, but that a missed token, from a workflow it had first deemed not impacted, gave the attackers access to its repositories (Grafana Labs, 2026-05-19); The Hacker News attributes the TanStack attack to TeamPCP (The Hacker News, 2026-05-20). The download covered public and private source code and internal repositories some teams use for operational information, including business contact names and email addresses, but not production systems or the Grafana Cloud platform; the ransom demand from an unnamed actor arrived on 2026-05-16, and Grafana has since rotated automation tokens, implemented enhanced monitoring and audited all commits since the May 11 incident (Grafana Labs, 2026-05-19).

CoinbaseCartel, active since September 2025, steals data and extorts victims without encrypting files; SecurityWeek counts 105 victims on its site, while The Hacker News, citing Halcyon and FortiGuard Labs, puts the total at 170 (SecurityWeek, 2026-05-18; The Hacker News, 2026-05-17). Security firms link the group to ShinyHunters, Scattered Spider and Lapsus$ (SecurityWeek, 2026-05-18), but ShinyHunters told BleepingComputer that CoinbaseCartel is not linked to it (BleepingComputer, 2026-05-18). Grafana's paying customers include governments, banks and infrastructure operators, and more than 7,000 organizations use the product (BleepingComputer, 2026-05-18).

Cited evidence

Grafana confirmed suffering a data breach on Sunday, two days after a cybercrime group listed the company on its leak website.

SecurityWeek 2026-05-18

We performed analysis and quickly rotated a significant number of GitHub workflow tokens, but a missed token led to the attackers gaining access to our GitHub repositories,

This includes business contact names and email addresses that would be exchanged in a professional relationship context, not information pulled from or processed through the use of production systems or the Grafana Cloud platform.

Grafana Labs (via The Hacker News)

After publishing this article, the ShinyHunters extortion gang told BleepingComputer that the CoinbaseCartel is not linked to their group or ransomware operation.

BleepingComputer 2026-05-18

Updates1

Correction

No source on the May 2026 breach describes a pull_request_target or Pwn-Request mechanism: Grafana says the incident originated from the TanStack npm supply-chain attack via the Mini Shai-Hulud campaign, detected on 2026-05-11, and that a GitHub workflow token missed during the rotation that followed gave the attackers access (Grafana Labs, 2026-05-19), an attack The Hacker News attributes to TeamPCP (The Hacker News, 2026-05-20). The theft was not limited to source code: the downloaded content also included internal repositories holding operational information and business contact names and email addresses, while production systems and the Grafana Cloud platform were not involved (The Hacker News, 2026-05-20). The link between CoinbaseCartel and ShinyHunters is contested, since ShinyHunters told BleepingComputer the group is not linked to it (BleepingComputer, 2026-05-18), and SecurityWeek counts 105 victims on CoinbaseCartel's site rather than about 170 (SecurityWeek, 2026-05-18). No source places Grafana in Swiss or EU public-sector monitoring estates or calls for watching unofficial Grafana plugins; Grafana says it audited all commits for malicious activity (The Hacker News, 2026-05-20).

Sources5

Revision history

  1. Published 2026-05-19-2505c918
  2. Correction 2026-10-21T1148Z-audit

    Grafana Labs traces its GitHub breach to the TanStack npm supply-chain attack attributed to TeamPCP, after which a GitHub workflow token missed during rotation let the attackers in, not to a pull_request_target Pwn-Request misconfiguration. The download was not limited to source code: it included internal repositories with business contact names and email addresses, though not production systems or Grafana Cloud. ShinyHunters denies any link to CoinbaseCartel, whose victim count is 105 by SecurityWeek's reckoning and 170 by The Hacker News's.

    Changed: affected_products body classification entities event_date evidence headline regions sectors sources sourcing_note summary techniques title

PROVENANCE

AI-generated · no human review · this permalink is the shareable record for the finding · verify operationally critical claims against the linked primary source.