Case · DiggingBeagle record

Chainstack compromise crossed an unauthenticated Kubernetes MCP control plane

Chainstack described an intrusion that started from an exposed development Grafana instance with default credentials. Its data-source proxy could reach an internal Kubernetes MCP server without independent authentication, and commands there ran with cluster-administrator authority. The public incident account does not prove every action was model-chosen, that every accessible secret was exfiltrated or that the ARTEX tool lineage identifies the same operator a

Scope

The investigation reports changes to ConfigMaps and automation workflows, stolen infrastructure credentials, accesses to production data and persistence attempts across Kubernetes resources. Some production database values were returned through command output, while individual MCP call records were not preserved.

Assessment profile

Assessment method
Setting
production
Exploitation
confirmed in the wild
Evidence
Grade B
Remediation
mitigation available
AI role
WITH AI
Basis and provenance

production setting with confirmed_in_the_wild status, based on the identified primary disclosure and its stated test or incident limits. The new Claim distinguishes source observations from hypothetical downstream effects. Impact band is unassigned because the scoped evidence does not justify a comparable quantitative score; no unobserved customer harm or loss is imputed. Remediation state: mitigation_available.

Assessed Nov 13, 2026 using diggingbeagle.assessment/1.

At a glance

Mechanism and trust boundary

  1. 01

    The investigation reports changes to ConfigMaps and automation workflows, stolen infrastructure credentials, accesses to production data and persistence attempts across Kubernetes resources. Some production database values were returned through command output, while individual MCP call records were not preserved.

  2. 02

    A supposedly internal tool server became an authority escalation route after the frontend fell: network reachability and proxy forwarding substituted for authentication at the effectful backend.

Claims & evidence

CLM-ENR243-007-DETAILChainstack describes a developer Grafana deployment with default credentials and a datasource proxy that reached an internal Kubernetes MCP service with cluster-admin authority; that path preceded access to production secrets and data.supported

Basis: reported finding

Link to claim
CLM-NOV15-CHAINSTACK-DATABASE-EDITChainstack reports database-level modification and restoration of an automation workflow during an intrusion that also traversed a default-credential Grafana and a cluster-admin Kubernetes MCP server.supported

Basis: reported finding

Link to claim
CLM-R242-CHAINSTACK-GRAFANA-MCP-PIVOT-LIMITSThe public incident account does not prove every action was model-chosen, that every accessible secret was exfiltrated or that the ARTEX tool lineage identifies the same operator as the Barracuda intrusion.supported

Basis: reported finding

Link to claim
CLM-R242-CHAINSTACK-GRAFANA-MCP-PIVOT-MECHANISMChainstack described an intrusion that started from an exposed development Grafana instance with default credentials. Its data-source proxy could reach an internal Kubernetes MCP server without independent authentication, and commands there ran with cluster-administrator authority.supported

Basis: reported finding

Link to claim

Implications

A supposedly internal tool server became an authority escalation route after the frontend fell: network reachability and proxy forwarding substituted for authentication at the effectful backend.

Controls and mitigations

  • Bind MCP tool execution to an authenticated principal with restricted cluster roles, and reconstruct persistent credential use and database effect logs.
  • Retain immutable database effect logs and correlate workflow storage mutations against application audit events, including out-of-band writers.

Unknowns and contradictions

  • The public incident account does not prove every action was model-chosen, that every accessible secret was exfiltrated or that the ARTEX tool lineage identifies the same operator as the Barracuda intrusion.

Sources and citation

Material revision history

  1. Nov 15, 2026 · Canonical change recorded · new in release · revision 250