Vendor reports service restoration and project count

Mittwald's incident account describes unauthorized access through a Model Context Protocol server designed to let agent clients manage hosting resources. A failure in the authorization mapping allowed activity to cross from the caller's expected project authority into other customer project scope. The vendor identified 56 affected customer projects and described containment and follow-up security work. That project figure counts affected projects, not proven data theft victims or unique companies.

The report notes speed or automation consistent with possible attacker use of AI tools, but does not provide a model transcript or causal proof that an autonomous agent planned or executed the intrusion. The affected MCP integration makes the incident intrinsically relevant to AI tooling as an attack surface. No verified field evidence justifies labeling the attacker as BY AI solely from timing.

A real production breach involving a hosting provider's AI-facing MCP server and the 56 customer projects it identified as affected.

The vendor report does not independently establish full contents taken from every project, a reusable exploit affecting other providers or actual autonomous AI direction. Project count and business/customer count are different denominators.

The vendor dates initial probing to October 21, with accounts created from October 23 and targeted exploitation on October 27. It detected anomalous activity on November 4 and temporarily disabled its AI-facing MCP server, mStudio sign-in, SSH and other account operations during containment. Its November 7 account identifies 56 affected projects, not 56 corporate victims and not a verified number of stolen documents.

Mittwald infers possible use of AI tooling from the speed of the intruder's actions, sometimes separated by seconds. That does not establish a model-directed intrusion or an ARTEX connection. The confirmed AI-specific failure was the MCP integration becoming an unauthorized path into managed hosting resources, a path ordinary dashboard users might never invoke. The company says customers' hosted websites stayed available; an organization responding to this incident should review the exact projects and access keys granted through MCP, not assume all hosting assets were reached.