AEGLIX News
Amazon's threat intelligence team captured records of AI agents operating from decoy servers in its MadPot network between October 3 and late last week, revealing a playbook that targets LLM gateways and AI application builders to harvest API keys. The company said it cannot verify the outcomes reported by the captured agents and has moderate confidence the agents ran on ARTEX, an open-source AI penetration testing tool whose developer made its GitHub repository unavailable on October 8 after abuse reports.
According to the captured records, the operation aims at a wide range of platforms, encompassing LLM gateways like One API, New API, Veloera, Sub2API and LiteLLM, as well as AI application builders such as Dify, FastGPT, Langflow, RAGFlow, Open WebUI, LobeChat and Ollama. The playbook leverages default credentials, incomplete installations and known vulnerabilities, notably an authentication bypass via the isCliRequest header in One API family systems and server-side request forgery through URL-fetch features that can reach cloud metadata services.
Cloudflare detected New Worker scripts named artex-*, artex-pgrecon-*, artex-pgw-* and artex-do-* executing at over 69 requests per minute across multiple account segments, signaling active automation linked to the tooling. The FBI released a FLASH alert indicating threat actors have employed ARTEX since at least August against organizations across numerous sectors globally, summarizing 11 prior reports without disclosing a new incident. A server-side template injection vulnerability in RAGFlow, tracked as CVE-2026-28797, permits any authenticated user to execute operating system commands; the National Vulnerability Database lists version 0.24.0 and earlier as affected and shows no patched version available.
Amazon recommends treating AI applications, model gateways, and inference endpoints like production systems and watching for misuse through unexpected spending or unusual usage. Community forks, archived copies, and a commercial ARTEX PRO version remain available despite the original repository removal.
Report prepared 2026-11-16 · Based on reporting from The Hacker News. Source publication date above; subsequent developments may not be reflected.