YOUR BRAND · YOUR CUSTOMERS · YOUR AI BUSINESS

Sell AI employees under your own brand.

AI Agent News Today

Monday, November 16, 2026

ARTEX: new, detailed hunt playbook for an agentic attack framework

What changed: ThreatDefence published a full detection and threat‑hunting advisory for ARTEX, an open‑source agentic penetration framework that researchers and defenders tie to real campaigns (incl. Storm‑0940); the piece lists how ARTEX organizes planner/worker agents, the exact request patterns it leaves in logs, and indicators of compromise you can hunt for.

Why it matters: ARTEX shows how agentic tooling turns multi‑step intrusion playbooks into reproducible, machine‑speed attacks; defenders and platform owners need behavioral detections (timing, chained requests, source‑map reads, rapid password‑spray bursts) rather than only signature blocks.

Try/watch: Add the listed behavioral rules to your SIEM and cloud‑log rules (look for one‑second spray rhythms, source‑map fetch+immediate internal route calls, and repeated programmatic OAuth flows), block exposed ARTEX consoles, rotate long‑lived keys, and test incident playbooks against a non‑production ARTEX replica.

OpenAI Responses API bug: approved MCP writes can replay when combined with hosted reads

What changed: An OpenAI Developer Community bug report (Nov 16) documents a reproducible behavior where an approved, native MCP write sometimes executes twice when the same response continues with a hosted programmatic read — the report includes a reproduction, request/response evidence, and links to related framework issues.

Why it matters: Builders that rely on in‑response approval flows and Model Context Protocol (MCP) writes (for example: creating DB records, publishing content, or triggering external state changes) can observe duplicate side‑effects that break idempotency and data integrity; that risk increases for long, multi‑step agent programs that mix approval resumption and hosted programmatic continuations.

Try/watch: Immediately add idempotency guards to write endpoints (idempotency keys, transactional checks, or “do‑once” markers), run the reproduction in staging, and monitor for duplicated writes in production. File a support/bug report with your provider if you see the behavior, and keep an eye on provider advisories for a fix or documented mitigation.

More News

YOUR BRAND · YOUR CUSTOMERS · YOUR AI BUSINESS

Sell AI employees under your own brand.

Give businesses AI teams that own ongoing roles. Set your pricing, delegate routine coordination and build a recurring service.