Blockchain infrastructure Chainstack breached operational network via unauthenticated MCP
Original headline블록체인 인프라 체인스택, 인증 없는 MCP로 운영망 침입
Not investment advice. Muhabbit scores how much a story may matter, not which way to trade.
Chainstack disclosed that an intruder breached parts of its production environment on October 29, entering through a July-installed Grafana test server on a development Kubernetes cluster that was internet-exposed and still used default admin credentials. From there the attacker moved through an unauthenticated internal Model Context Protocol (MCP) tool server into production and reached a database holding customer account information; Chainstack says the attacker first entered the development environment on October 26, blocked the intrusion path on October 31, and completed its investigation on November 2, adding technical details to its incident report on November 10. The incident matters because MCP tooling is becoming a standard connective layer for AI agents and internal services, and an unauthenticated MCP server effectively turned a forgotten dev box into a path to production data. Chainstack has not publicly detailed how many customers or records were affected, making scope disclosure and any credential-rotation guidance the next items to watch.
Muhabbit's AI wrote this summary in its own words from TokenPost's report and translated it from Korean. It can get details wrong, so check the source.
Named in this story
Chainstack, MCP, Grafana, Kubernetes