Habr•August 15, 2026•🇷🇺Translated from Russian

Israeli Firm Reveals First Known AI-Led Breach of Taiwanese Government Systems

An Israeli company Dream discovered an open 160 MB archive while monitoring cybercriminal forums. The archive contained 1,395 files including reports, logs and data exports that reconstructed an entire cyber operation conducted between 1 and 4 July 2026 against government systems later identified by Financial Times as belonging to Taiwan.

The operation consisted of 12 sequential waves. In each wave up to eight sub-agents operated in parallel, each assigned its own target and technique. After a human operator launched the system and defined initial scope, all reconnaissance, exploitation decisions, recovery from failed attempts and persistence actions were performed autonomously by the agents.

The agents began with a single government portal, downloaded its scripts and extracted embedded API endpoints and single-sign-on configuration. This produced a map of 21 linked government systems. They then exploited forgotten debug endpoints that required no authentication, ultimately obtaining 85 employee accounts and exfiltrating more than 2,500 personnel records while installing backdoors on state web applications.

The framework did not stop at primary targets. It expanded to government IT suppliers, the national email platform, at least seven energy companies and the nuclear safety agency, scanning them in parallel. All offensive tooling came from two freely available open-source projects: Hermes and OpenClaw. No proprietary exploits or closed-source components were present.

The model safety mechanisms were bypassed simply by describing the task as an authorized penetration test. Researchers could not identify the exact underlying model but noted that open-weight models typically apply weaker refusal filters. The operation left almost no zero-day artifacts; every successful compromise used exposed endpoints, disabled signature validation or missing authentication.

Detection was difficult because the agents produced traffic patterns that closely resembled normal automated scanning. The decisive difference appeared only after initial access: the agents used the 85 compromised accounts to move laterally through the single-sign-on fabric, achieving 84 successful authentications without triggering multi-factor prompts or user confirmation. The system also performed its own validation, rejecting seven false-positive findings after cross-checks by multiple agents.

Related articles

Habr•AI Security

Taming the LLM Dragon: Corporate AI Gateway Architecture Addresses Classic Proxy Shortcomings

Spontaneous adoption of generative AI across enterprises has created shadow AI risks, prompt leaks, and uncontrolled token consumption that standard L7 proxies cannot mitigate. Traditional solutions built on Nginx, Envoy or Kong lack the ability to inspect Server-Sent Events streams, classify sensitive content inside prompts, or enforce token-based quotas in real time. The AI Optimum platform introduces a specialized AI gateway layer that sits between internal consumers and both local inference clusters and external APIs such as GigaChat and YandexGPT. It performs inline PII masking, routes traffic according to data sensitivity, supports OpenAI-compatible endpoints, and maintains detailed audit logs required under 152-FZ. The gateway adds only tens of milliseconds of latency while enabling granular billing, context caching optimization, and protection against runaway agent loops. Subsequent articles in the series will examine real corporate AI spend and further regulatory controls.

Habr•AI Security

Why We Banned Our AI Manager from Writing Code and Assigned the Task to Claude Opus

The team behind an AI-powered marketplace manager for Wildberries initially built the system using regular updates, then migrated it to an autonomous agent. After implementing multiple layers of restrictions, they ultimately removed the agent entirely and rebuilt the solution from scratch. The new architecture relies on a single tool that handles the complete Wildberries API along with internet access while respecting all platform limits. The decision to prohibit the original AI manager from generating code stemmed from concerns over reliability and security in production environments. Instead, the developers turned to Claude Opus to handle coding tasks. This case highlights practical challenges of deploying AI agents in e-commerce automation and information security contexts.

Habr•AI Security

Developer Builds MCP Linter and Discovers Security Issues in Anthropic Official Servers

A developer has released mcp-linter, a lightweight security and compliance tool for the Model Context Protocol used by Anthropic's Claude ecosystem. The linter detects critical problems such as stdout pollution that breaks JSON-RPC framing, missing destructiveHint annotations that allow autonomous agents to execute dangerous actions without human confirmation, prompt injection vectors hidden inside tool descriptions, and incomplete input schemas that increase model hallucinations. When run against Anthropic's reference servers, the tool assigned low health scores to server-memory and especially server-filesystem, highlighting dozens of parameters lacking descriptions. The utility runs with zero dependencies, supports SARIF output for GitHub Security, and can generate automatic JSON patches. The project is open source under MIT license and already integrates into CI pipelines via a dedicated GitHub Action.

Habr•AI Security

Pentesting AI Components: Key Vulnerabilities CISOs Must Address in RAG and AI Agents

The article examines how AI integration into corporate systems dramatically expands the attack surface beyond traditional web application testing. It details risks associated with chatbots, RAG-enabled systems that pull from internal documents, and autonomous AI agents capable of executing real actions via APIs. Yuri Grishaev, an OSCP+ certified specialist and top Standoff 365 hacker, explains how prompt injection can bypass access controls and lead to data leaks or unauthorized operations. The piece stresses that service accounts often hold broad privileges, allowing AI components to serve as indirect paths to sensitive data even when direct user access is restricted. It also covers how AI-generated output can trigger classic vulnerabilities such as XSS if not properly sanitized. Recommendations include inventorying all AI tools, enforcing least-privilege principles, and validating user permissions before any model processes or acts on retrieved content. ABP2B provides free checklists and policy templates to help organizations prepare for secure AI adoption.