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
How to Grant AI Agents Access to Internal APIs via MCP: Key Questions Security Teams Will Ask
As AI agents increasingly need to call internal APIs, security teams focus on three core questions: who granted access, how to revoke it, and how to investigate incidents after the fact. The answers lie in operation-level access control rather than traffic inspection alone. MCP, now managed by the Agentic AI Foundation under the Linux Foundation, has become the standard for connecting AI agents to enterprise systems with hundreds of millions of SDK downloads monthly. The article details how NEOMSA APIM implements MCP servers, tool publication from OpenAPI specs, subscription-based scopes, and 15 independent security checks. It explains why classic traffic filters fail against valid but unauthorized tool calls and stresses the need for owner approval, application-specific identities, and proper identity propagation through token exchange. Rate limiting at the subscription level and business-object validation are presented as essential controls to prevent overreach and duplication.
AI Gateway Emerges as Unified Control Layer for Enterprise LLM Access and Data Protection
As organizations scale LLM usage beyond individual enthusiasts to dozens of teams, IDEs, internal agents, and automations, AI Gateway becomes essential infrastructure for security, cost management, and reliability. The solution acts as a single entry point that authenticates users, enforces policies, performs DLP checks, depersonalizes sensitive data, routes requests across providers, and enables detailed auditing and billing. Companies face strict requirements under Russian Federal Law 152-FZ on personal data, along with risks of leaks involving API tokens, client information, and internal code when employees bypass official channels. Mature implementations from Cloudflare, Kong, and Microsoft Azure API Management already demonstrate analytics, rate limiting, fallback mechanisms, and governance features. Compatibility with OpenAI API reduces migration friction when switching between providers, including Chinese models, while handling edge cases like tool calls and vision capabilities. The article stresses separating AI Gateway responsibilities from DLP, MCP Gateway, and guardrails to avoid creating an unmanageable monolithic system. Early implementation priorities include ownership, comprehensive auditing from day one, real-world client compatibility testing, shadow-mode DLP, and clear documentation of production architecture.
AI Accelerates DevSecOps but Expands Attack Surfaces Across Code, Supply Chains, and Runtime Environments
Experts from Solar, Luntry, and Hexway report that AI has shortened the vulnerability exploitation window from 63 days in 2019 to just hours in 2025. The shift toward third-party libraries and vibe coding has redirected attacker focus to supply-chain compromises affecting thousands of organizations. AI-generated code introduces unique risks because it often bypasses established libraries, testing phases, and security reviews, with 41% of confidential data leaks into LLMs now consisting of source code. While AI tools like the Solar appScreener plugin achieve over 90% accuracy in triage and 85% in code-fix recommendations, human verification remains mandatory for critical vulnerabilities. Platforms such as Hexway ASOC and Luntry extend protection into container orchestration and runtime monitoring to handle AI agents that make decisions during execution. The overall effect is a tenfold increase in AppSec team capacity, yet also a larger volume of findings that must be managed through integrated ASOC workflows.
OpenAI Deactivates Three-Year-Old Pro Account Used for Bug Bounty Work, Permanently Cutting Off All Chat History and Files
A long-time OpenAI user has publicly detailed the sudden deactivation of a three-year-old account that held both ChatGPT Pro and the specialized Daybreak Blue cyber access program. The account, used for legitimate penetration testing and bug bounty submissions, was terminated without prior warning after the user accepted the required hardware security token. All accumulated conversations, generated files, and project data became immediately inaccessible, with no export option available even after repeated appeals. Support channels, including AI-moderated chat and direct email, refused to reopen the case or provide any data recovery path. The incident highlights growing reports of similar account terminations on Reddit and raises questions about the value of OpenAI’s trusted-access programs for security researchers. The affected user is now considering chargeback options through their bank while warning others to regularly export important data.