Loading story…
Organizations are increasingly blending agentic AI with deterministic software, but the primary risk is operational: probabilistic systems can produce confident, plausible outputs that are not reliably predictable, auditable, or repeatable. Guidance aimed at CIOs emphasizes using traditional code for data validation, transaction processing, compliance logic, and structured output generation, while reserving agents for ambiguous tasks like interpretation, summarization, and decision support; it also notes that teams should tune agent behavior and output quality before adding guardrails, because weak prompting or ill-suited models can shift safety boundaries.
Gen’s research frames this as “Artificial Mindless Intelligence (AMI)”—AI that generates mind-like output without grounded understanding, stable intent, or accountability—and warns that harm does not require a model to “go rogue.” The key failure mode is granting AI systems operational authority (e.g., access to inboxes, files, calendars, chat apps, admin consoles, or payment workflows), where errors, manipulation, or ungrounded actions can directly trigger business impact; the piece argues that focusing on AGI narratives leads either to security theater or complacency, while the near-term risk is permissioned automation acting beyond appropriate authorization boundaries.
Track how attackers are adapting to this technology.
1 event from the most recent confirmed update back to the earliest known activity.
Initial story creation
Follow how adversaries are adapting to this technology, and where it touches your stack today.
2 references tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Enterprises and financial institutions are warning that **agentic AI**—autonomous agents that can initiate actions without continuous human input—creates new operational and security failure modes that existing governance and control frameworks are not designed to handle. Commentary aimed at CIOs highlights the risk of “AI agent havoc,” where always-on agents can trigger cascading business impact (e.g., unintended actions, compliance failures, and accountability gaps) that could translate into executive-level consequences if controls, monitoring, and escalation paths are not redesigned for autonomous behavior. In banking, fraud and identity experts describe a **“dual authentication crisis”** driven by AI agents that can autonomously initiate transactions, approve payments, or freeze accounts in real time. The core issue is that traditional point-in-time authentication (passwords/MFA) assumes a human actor; banks now need to validate both **intent** (did the customer authorize the agent to take a specific action) and **integrity** (is the agent operating as designed and not manipulated), shifting security from “verify identity” to “verify delegated authority and agent behavior.”
Jun 29, 2026
Security leaders are warning that **AI agents are increasingly operating as “digital employees”** inside enterprise workflows—triaging alerts, coordinating investigations, and moving work across security tools—often with **broad permissions and limited governance**. The core risk highlighted is that organizations are deploying high-authority agents like plug-ins (reused service accounts, overbroad roles, weak oversight), creating fast-acting operators that can be manipulated and that lack the contextual judgment and policy awareness expected of human staff. Related commentary also raises concerns about **AI-to-AI communication** and “non-human-readable” behaviors that could reduce auditability and complicate investigations and control enforcement. In parallel, public examples show how quickly AI can accelerate **vulnerability discovery**: Microsoft Azure CTO Mark Russinovich reported using *Claude Opus 4.6* to decompile decades-old Apple II 6502 machine code and identify multiple issues, underscoring that similar techniques could be applied to **embedded/legacy firmware at scale**. Anthropic has also cautioned that advanced models can find high-severity flaws even in heavily tested codebases, reinforcing the likelihood that both defenders and attackers will leverage AI for faster bug-finding. Separate enterprise IT coverage notes that organizations are **reallocating budgets toward AI** by consolidating tools and renegotiating contracts, which can indirectly increase security exposure if cost-cutting reduces overlapping controls or if AI adoption outpaces governance and identity/access management maturity.
Jun 29, 2026
Enterprises and public-sector organizations are accelerating adoption of **AI agents** and generative AI to automate knowledge work and software delivery, with guidance increasingly framed as a management and governance problem rather than a purely technical one. Commentary on agentic AI in software development describes agents as autonomous decision loops operating within guardrails (goal decomposition, tool selection, execution, observation, and iteration), enabled by mature CI/CD automation and API-driven infrastructure. Separate reporting highlights empirical findings that AI-generated code has grown to nearly **30%** of code by late 2024 and is associated with an estimated **~4%** productivity lift, with gains concentrated among more experienced developers despite higher usage among less-experienced staff. Security and procurement implications are emerging alongside this adoption. Research on **agentic tool chain attacks** warns that AI agents’ “reasoning layer” and natural-language tool metadata become an attack surface, enabling techniques such as **tool poisoning**, tool shadowing, and “rugpull” behavior that can lead to covert data leakage or unauthorized actions; the risk is amplified when tools are centralized via architectures like the *Model Context Protocol (MCP)*, where compromise of a shared tool server can propagate malicious behavior across many agents. In the US federal context, agencies are signaling demand for AI tools that deliver operational value while meeting requirements for security, transparency, and responsible use, and the General Services Administration is also tightening contractor cybersecurity expectations for work involving **CUI** by requiring alignment with **NIST SP 800-171** (and select **800-172** controls), including MFA, encryption, vulnerability remediation, and removal of end-of-life components, with independent assessments as part of authorization and ongoing monitoring.
Jun 29, 2026