AML.T0132 · Misconfigured or Publicly Exposed AI Services

Explore 3 source-supported AI security cases for AML.T0132 · Misconfigured or Publicly Exposed AI Services in MITRE ATLAS, with evidence, scope, and defensive analysis.

Risk category

AI agents and LLM platforms are deployed across diverse architectures, including standalone servers, SaaS platforms, and low-code builders. All of these often have misconfigured access controls, ranging from missing authentication in LLM runtimes to permissive public access settings, that significantly expand their attack surface. AI agent's security posture affects how attackers are able to explore which agentic attack surface is available to them and directly either expands or limits an adversary's ability to discover and interact with a target's AI agents. For example, one internet-facing AI service could be more easily discoverable by any unauthenticated user, while another may require compromised credentials to even be discovered. Adversaries may discover and interact with AI agents and LLM services as unauthenticated users via a combination of various OSINT and active scanning methods. These could include using search engines to discover accessible agentic deployments (See [Search Open Technical Databases](/techniques/AML.T0000)), search backlinks which could indicate existing or open agents which have been embedded to frontends (See [Search Open Website/Domains](/techniques/AML.T0095)), or directly scanning a target's AI infrastructure (See [Active Scanning](/techniques/AML.T0006)).

Official framework source ↗ · Open interactive explorer ↗

Incident ·

Flowise Honeypot: Unauthenticated API Abuse, Beacon Setup, and Agent Probing

Sekoia recorded six phases of real attacker traffic against an internet-facing decoy that emulated Flowise 2.2.8, a platform for building AI workflows. The exposed management API let the attacker retrieve planted credentials and add a workflow configured to call back. The attacker then tried to override prompts, probe session memory and ask the simulated agent about real third-party infrastructure. The decoy returned simulated responses, so the requests do not establish real command execution, database access or a Nightingale compromise.

ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.

AIA · Read the full case ↗ · SecureFlow · Read the full case ↗

Incident ·

Chainstack: A Grafana Proxy Reached a Privileged, Unauthenticated MCP Server

Chainstack provides blockchain infrastructure services. Chainstack traced its October 2026 intrusion from a test Grafana instance to an unauthenticated, cluster-admin MCP server, then to production through compromised machine credentials. The investigation found database access, secret theft and several persistence routes. It did not recover individual MCP calls or establish customer-node modification. ARTEX is the operator’s assessment of the attacker’s tooling, not actor attribution.

ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.

AIA · Read the full case ↗ · SecureFlow · Read the full case ↗

Validated Research ·

Exposed ClawdBot Control Interfaces Leads to Credential Access and Execution

A security researcher identified hundreds of exposed ClawdBot control interfaces on the public internet. ClawdBot (now OpenClaw) "is a personal AI assistant you run on your own devices. It answers you on the channels you already use ... , plus extension channels. ... It can speak and listen on macOS/iOS/Android, and can render a live Canvas you control." The researcher was able to access credentials to a variety of connected applications via ClawdBot's configuration file. They were also able to invoke ClawdBot's skills by prompting it via the chat interface, leading to root access in the container. The researcher searched Shodan to identify Clawdbot instances exposed on the public internet, some without authentication enabled. The researcher demonstrated that the ClawdBot's authentication mechanism could be bypassed due to a proxy misconfiguration. With access to ClawdBot's control interface, they were then able to access ClawdBot's configuration, which contained credentials to a variety of other services. Across various exposed instances of ClawdBot, they identified Anthropic API Keys, Telegram Bot Tokens, Slack Oauth Credentials, and Signal Device Linking URIs. The researcher prompted ClawdBot directly via the chat interface, which led to exposure of its system prompt. They were also able to get ClawdBot to execute commands via its bash skill, which at least in at least one instance led to root access in the ClawdBot container. The researcher noted a broad range of other impacts they could have had with this level of access, including: - Manipulation of user chat history with the ClawdBot AI agent - Exfiltration of conversation histories of any connected messaging services - Impersonation of users by sending messages on their behalf via connected messaging services

ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.

SecureFlow · Read the full case ↗