Attackers Have Found MCP. What Platform Teams Should Do About It
PlatformEngineering.com, Monday, October 19th, 2026
A ransomware affiliate used MCP as a live attack channel; platform teams need MCP inventories, default-deny tooling, sandboxing and logging.
On October 5, CloudSEK documented a ransomware affiliate who registered a reverse shell as an MCP tool inside an AI coding assistant and drove attacks through it, compromising more than 20 organizations in six countries, while also scanning the internet for exposed MCP ports.
The author, who runs MCP-based SRE agents in production, says there is no CVE to patch; the issue is how MCP servers get deployed, often without authentication or logging.
He urges treating every MCP server as a production service, with a central inventory, approved tool registration, sandboxed execution, restricted network access, full tool-call logging and risk-based human approval.