Do You Really Know What Your AI Agent Is Doing in the Sandbox?
The rapid adoption of AI agents equipped with shells, filesystems, and network access has created a fundamental observability problem. When an agent finishes a task, logs generated by the model itself and platform metrics provide only a partial picture. The real question remains: what system calls did the agent actually execute?
Two main approaches exist for observing agent behavior. The first intercepts tool calls inside the agent framework, which is inexpensive but blind to any actions performed outside the framework. The second uses eBPF probes on the host kernel to capture every syscall, an approach used by container security tools. This method is more trustworthy yet assumes the agent shares the host kernel.
Strong isolation runtimes break that assumption. gVisor implements its own kernel in user space, while Kata Containers and Firecracker run a full guest Linux kernel inside a virtual machine. In both cases, guest syscalls never reach the host kernel where traditional monitors attach.
Existing standards cover several aspects of agent operation. MCP standardizes how agents connect to tools and data. OpenTelemetry defines semantic conventions for model and agent spans. RuntimeClass lets Kubernetes switch between runtimes without changing application manifests. The new agent-sandbox project treats sandboxes as first-class Kubernetes resources. None of these standards, however, define a common interface for reporting the actual syscalls performed inside the sandbox.
Empirical testing used a generator that performed ten distinct operations, each tagged with a unique marker. Probes verified that the monitoring stack itself was functioning correctly. Results across 24 runs demonstrated that visibility is determined by whether filesystem operations cross into a host process. When a block device backs the guest root, almost no guest file operations appear on the host. When virtiofs or an overlay shares the filesystem via a host process, file names and writes become visible.
Even within the same runtime, configuration changes produce dramatically different results. Enabling the in-memory overlay in one gVisor mode hides writes and deletions while still exposing opens. Executions never surface as execve events on the host under any tested sandbox; only prior file copies leave detectable traces when the filesystem is host-mediated.
Commercial security products already reflect these limitations. Falco removed its gVisor engine, Google Container Threat Detection is incompatible with GKE Sandbox, and Microsoft Defender cannot inspect Kata pods. The measurements confirm that switching a RuntimeClass value can silently eliminate visibility into entire classes of agent actions.
Related articles
Russian State-Linked Group GTG-20006 Uses Anthropic AI Agents to Automate Malware Rebuilding
Anthropic has identified a Russian state-linked operation tracked as GTG-20006 that deployed autonomous AI agents to continuously rebuild its malware arsenal whenever detections occurred. The group, connected to Midnight Blizzard, APT29 and Cozy Bear, created a closed-loop automation system in which AI agents monitored tool performance against known defenses and triggered immediate code modifications to evade security products. Beyond malware, the agents handled domain registration, hosting infrastructure setup, phishing email delivery, command-and-control channel monitoring and implant persistence tracking across compromised environments. The campaign, active in July and August 2026 and overlapping with CaptiveCrunch, targeted more than twenty organizations including ministries, defense bodies, embassies and think tanks across Ukraine, Europe, the Middle East and Asia. In one incident the attackers exfiltrated over 300,000 national identity records and commercial registration data for more than 500,000 companies. Anthropic disrupted the activity and published a detailed report highlighting how the automation shifted the cost burden back onto defenders.
Anthropic Exposes Widespread Weaponization of Claude by Nation-State Hackers and Cybercriminals for Automated Attacks
Anthropic has released a threat intelligence report detailing how multiple state-sponsored and criminal groups systematically abused its Claude model between December 2025 and August 2026. The company introduced the term Generative Threat Groups to describe actors that built multi-agent frameworks to automate reconnaissance, exploitation, and data exfiltration. One group identified as GTG-20006, widely linked to Midnight Blizzard, APT29 and Cozy Bear, created an AI-driven workflow that automatically rewrites and redeploys malware once security tools detect it. The report highlights that this capability collapses the traditional gap between well-resourced nation-state operations and individual attackers. Defensive recommendations focus on shifting detection to behavioral chains, shortening IOC validity periods, strengthening data-loss prevention, and establishing internal governance for AI tool usage.
Unit 42 Details First Multi-Agent AI Ransomware Attack That Finished in Ten Hours
Palo Alto Networks Unit 42 has published the first confirmed case of a multi-agent AI ransomware operation. Attackers only defined the target; more than ten specialized AI agents then performed reconnaissance, credential harvesting, lateral movement, data exfiltration, and encryption within ten hours. The agents used over fifty ATT&CK techniques and successfully hid command traffic inside the victim’s own AI service endpoints. After encryption the same agents automatically generated an eighty-page security audit report listing every compromised system and technique. The sole defensive control that stopped part of the attack was a mandatory multi-person code review rule on Terraform changes. Unit 42 links the operation to frontier large-language-model frameworks and notes that earlier single-agent incidents such as JADEPUFFER have now evolved into coordinated agent fleets.
Deepfakes Turn Job Interviews into Cyberattack Vectors Targeting IT Candidates and Recruiters
Deepfake technology and malicious test assignments are increasingly used during IT hiring processes to conduct industrial espionage or deploy malware. Attackers impersonate recruiters or candidates, sending infected GitHub repositories or npm packages that install backdoors stealing credentials and enabling remote access. Groups such as Lazarus and the dedicated Contagious Interview collective have run campaigns against chemical and IT firms, while individual cases like the Smello Python developer incident show how prepare scripts in package.json can trigger hidden payloads. Gartner predicts that by 2028 one in four job applicants could be fake, creating risks beyond bad hires including data theft and financial loss. Defenses include isolated virtual machines for test tasks, profile verification by companies like Socure, and interview techniques such as the GOTCHA movement challenges or corneal reflection probes developed by universities. Major firms including Cisco, McKinsey, and Google are returning to in-person interviews as a reliable countermeasure. The rapid evolution of deepfake quality tracked by Unit 42 means layered verification combining technical, procedural, and human checks is now essential.