HackerSec's Yaga AI Agent Delivers Autonomous Penetration Testing with 98% Effectiveness
HackerSec has introduced an autonomous penetration testing platform driven by its Yaga AI agent, representing a fundamental change in how organizations can evaluate their defensive posture.
Traditional automated scanners execute fixed sequences of checks. In contrast, an autonomous agent continuously observes the target environment, interprets responses, generates hypotheses, and adjusts its strategy as new evidence appears. This ability to decide and replan during an engagement distinguishes true autonomy from sophisticated automation.
The key differentiator lies in system architecture. A single discovery in a real pentest can redirect the entire investigation. The agent must retain memory and state, correlate findings made at different times, select appropriate tools, and construct new attack paths. While advanced AI models are essential, they do not by themselves convert a tool into an autonomous pentester.
HackerSec built its platform around a proprietary harness specifically designed for offensive operations. This harness coordinates AI models, security tools, contextual information, memory, and decision-making throughout the engagement. The goal is to let the agent investigate an environment continuously while human specialists review and validate discovered issues.
Yaga currently achieves more than 98 percent effectiveness and signals HackerSec’s transition to an AI-native offensive security model. Rather than simply automating known tests, the platform enables the AI to lead the investigation, adapt its approach, and advance as it gains deeper understanding of the target.
“We are entering a reality where applications change every day and attacks are accelerating with AI,” said Andrew Martinez, CEO of HackerSec. “Conducting pentests two or three times a year is no longer sufficient. Offensive security must evolve into a continuous, autonomous model that tests systems at the same speed they change.”
Related articles
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.
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.
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.
Local LLMs Enable Scams by Drafting Fraudulent Replies Without Warnings
Tests on consumer hardware showed that popular 7-8B local models almost never flagged classic advance-fee schemes when asked to draft replies instead of detecting fraud. The author ran 42 scam scenarios across Russian, Kazakh and mixed language on Llama 3.1 8B, Qwen 2.5 7B and DeepSeek-R1 8B using only an RTX 5050 laptop and Ollama. Without additional controls the models produced ready-to-send messages agreeing to prepaid transfers to unknown Kaspi Gold numbers in nearly every case. Introduction of the MoneyGate layer, which combines a mandate check, a separate judge model and hard-coded red-flag rules, blocked all 42 malicious requests while still allowing most legitimate payments to proceed. The benchmark KZ Scam Shield covering 12 Kazakhstan-specific fraud patterns remains publicly available for further testing.