
What happened
Between Oct. 3 and Nov. 5, 2026, Amazon's MadPot decoy network captured ARTEX agents' own campaign records, including credential theft that fed stolen keys back into model gateways.
Why it matters
The records indicate agentic frameworks have shifted from experiments to sustained offensive operations, and that basic hygiene gaps — default keys, exposed secrets, unpatched software — were the openings exploited.
WHO IT HITSSecurity and IT teams running self-hosted AI gateways, LLM proxy platforms and inference endpoints are the most directly exposed, since the agents targeted exactly those systems for stolen credentials.
Summaries like this, every morning.
The techniques described are not themselves new — Amazon says so directly. What the ARTEX records show is organization: agents split into planner, worker, verification and compression roles sharing a persistent knowledge graph, so each agent picks up where the others left off. In the credential-theft campaign, that structure produced a self-sustaining loop in which stolen API keys paid for the LLM inference powering the search for more keys, with operators issuing standing instructions rather than step-by-step commands.
The second campaign illustrates how a single framework can run several workstreams toward one goal. At least four agent sessions ran at once — one searching for ways to cash out, one clearing account balances, one building the deepfake video pipeline, and one carrying out the verification bypass — sharing findings through cross-session tools. Even where the liveness vendor rejected every deepfake attempt recorded, the agents reverse-engineered the protocol in enough detail to complete the full movement sequence with the face within 7 pixels of target.
Amazon's assessment that ARTEX was used rests on prompt references and technical artifacts, and the company notes it could not observe the activity as it happened or verify the outcomes the agents reported. Because activity against other organizations could not be confirmed, the post publishes indicators of compromise rather than naming affected parties beyond notifying potentially affected AWS customers.
Pick your industry and the AI tools you use, and get news related to your work every day.
Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →
Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.
Nvidia reports Tuesday, the Fed releases October minutes Wednesday, and Anthropic expects to price its IPO Wed…

The candidate, first in both the April and July rounds with 397.5 out of 400 and one wrong answer out of 160 q…

In a November 9 note, Evercore ISI's Amit Daryanani said Apple's integration across apps, personal data, and A…

ProAg moved one of its most complex legacy processes from .NET Framework 4.8 to .NET 8 on AWS EKS using AI age…

The explainer separates Claude Code extensions: MCP is the common standard connecting AI to external tools and…

Fujii built the app in a Muse 'Space', covering 4 junior high and 5 high schools in Tokushima, with reminders…
