Amazon Honeypot Captures ARTEX AI Agent Logs Revealing Self-Sustaining Key Theft and Failed Deepfake KYC Attempts
Amazon's MadPot honeypot captured operational logs from ARTEX AI agents, revealing a self-sustaining loop where stolen LLM API keys funded further credential hunting and real-time deepfakes failed server-side KYC validation.
Amazon Threat Intelligence announced on November 13, 2026, that its globally distributed decoy network, MadPot, captured requests from AI agents running offensive campaigns on the open-source framework ARTEX between October 3 and November 5, 2026. The sensors were configured to mimic popular large language model (LLM) inference APIs, causing the agents to send their own operational history—including system prompts, tool execution records, and knowledge graph states—to the honeypot.
The primary campaign involved the industrial-scale theft of credentials to access AI models. Stolen keys were fed back into the framework's own model gateway, creating a self-sustaining loop where computational resources paid for by victims funded the search for more keys. Targets included LLM gateways like One API, New API, and LiteLLM, as well as application builders such as Dify, Langflow, and RAGFlow. The agents exploited default master keys, uninitialized installs, and known vulnerabilities like CVE-2025-3248 (Langflow) and CVE-2026-28797 (RAGFlow).
A second campaign targeted cryptocurrency exchanges, attempting to bypass Know Your Customer (KYC) identity verification using real-time deepfakes. The agents reverse-engineered liveness detection mechanisms and generated forged video at 11.5 frames per second on a single consumer GPU. However, all recorded deepfake attempts failed server-side validation.
Amazon assessed with moderate confidence that these operations were conducted by disparate Chinese-nexus threat groups, citing simplified Chinese prompts, China time-zone configurations, and targeting rules excluding mainland China. The company emphasized that the techniques relied on known weaknesses rather than novel exploits, urging organizations to rotate exposed secrets, patch public platforms, and review indicators of compromise (IOCs) published in the report.