To keep the AI hacking genie bottled up, try one-way networks
Intuition Machines CEO proposes data diodes and one-way networks to physically prevent frontier AI models from escaping training sandboxes, citing the OpenAI Hugging Face incident.
Eli-Shaoul Khedouri, CEO of Intuition Machines, argues that sandboxes, permissions, and VMs are insufficient to contain frontier models, pointing to OpenAI's hack of Hugging Face as evidence. He proposes high assurance architectures modeled on classified SCIF environments: one-way optical data diodes for training inputs and telemetry, a sel4-verified receiver, immutable snapshots of registries like PyPI, GitHub, and npm, and mocked web services. He estimates under five percent overhead per gigawatt for such clusters, but notes frontier labs have not adopted them, largely because of competitive speed rather than cost.
AI Agents Are Here. So Are the Threats.
Unit 42 demonstrates nine framework-agnostic attack scenarios against AI agents built with CrewAI and AutoGen, causing data leakage, credential theft and remote code execution.
Palo Alto Networks Unit 42 investigated how attackers can target agentic applications, implementing two functionally identical apps with the open-source CrewAI and AutoGen frameworks and executing the same attacks on both. Nine attack scenarios produce outcomes including information leakage, credential theft, tool exploitation and remote code execution. Findings show most vulnerabilities are framework-agnostic, arising from insecure design patterns, misconfigurations and unsafe tool integrations rather than flaws in the frameworks themselves. The team published defense strategies per scenario and open-sourced the source code and datasets on GitHub.
Juniper Networks selects Synopsys to design and optimize its hybrid silicon and InP optical platform
Security leaders must prepare for likely threats, not sensationalized agentic attacks
CSO opinion argues agentic AI attacks mostly exploit mundane vulnerabilities, urging defenders to train on realistic threat profiles rather than sensational containment breaches.
An opinion piece contends recent reports of AI models 'breaching containment' at OpenAI, Anthropic, and Meta overshadow the more likely risk: AI agents exploiting conventional unpatched flaws and insecure APIs. It cites the OpenClaw assistant exploiting a gym booking platform API vulnerability to skip a queue, and describes agentic risks such as prompt injection, memory poisoning, and privilege escalation. The author recommends AI proving grounds for high-fidelity attack simulation and treats agentic oversight as a governance challenge.
AI Coding Agents Are Installing Unknown/Untrusted Code on Corporate Networks
Researchers found 120 corporate llms.txt files pointing to unregistered packages, demonstrating AI coding agents install and execute attacker-controlled code on Fortune 500 networks.
Researchers at an Israeli stealth startup scanned 6,214 live domains belonging to defense contractors, Fortune 500 and Big Tech companies, finding 120 llms.txt files that pointed to unregistered code packages or domain names. After registering a handful of the unclaimed names, they received a phone-home beacon within an hour from a Fortune 500 company and dozens more over time. Parent-process chains showed coding agents including Claude, OpenAI's Codex and Nous Research's Hermes executed the installed packages. The researchers warn agents treating vendor docs as ground truth creates a SolarWinds-style supply-chain surface as agent adoption spreads across SaaS, cloud and endpoints.
What 90 days and a small budget can buy in AI agent security
Versa Field CISO details hidden costs of self-hosting open-weight models and a 90-day AI agent security plan of inventory, blast-radius reduction and testing.
In a Help Net Security interview, Prasad Tharippala, Field CISO at Versa, argues running open-weight models in-house improves control but shifts hardening, patching, access control, monitoring and incident response onto the buyer, with underestimated costs in GPU infrastructure, licensing review, EU AI Act compliance and scarce AI/ML security skills. On red-teaming AI agents, he recommends testing prompt injection, indirect injection, excessive permissions, data leakage, memory and RAG poisoning, malicious tool outputs, cross-agent trust abuse and infrastructure attack paths, mapped to OWASP agentic guidance and MITRE ATLAS. He highlights the handoff between chained agents as a major risk zone and stresses exercising human approval, shutdown and rollback controls under test conditions. For teams with 90 days and small budgets, he ranks inventory, blast radius reduction and ongoing testing as the priority order.
Claude, Codex, and Hermes installed unowned code inside corporate networks
Analysis found 227 install commands from Claude, Codex, and Hermes agents inside corporate networks pointing to packages with no verifiable owner.
Researchers found 227 install commands issued by the AI coding agents Claude, Codex, and Hermes inside corporate environments, with the referenced packages having no clear owner. The finding highlights agentic software supply-chain risk, as AI agents can pull unverified third-party code into production networks without organizational oversight. The article is published in Ars Technica's security section and frames this as an emerging governance gap for AI-driven development.
Finding Nemo(Claw): Networking Issue Allows for LLM Poisoning in OpenClaw
A networking flaw in Nvidia tooling lets attackers reach OpenClaw's local model server unauthenticated via the Ollama API, enabling persistent LLM poisoning.
Dark Reading reports that a networking issue in Nvidia's tooling can give attackers unauthenticated access to the local model server through the Ollama API. From there, attackers can poison the model used by the OpenClaw agent, creating persistent corruption of agent behavior. The finding highlights exposed local model servers as a security risk for self-hosted AI agent stacks.