HackerSec Launches AI-Native Pentest Platform with Yaga Agent for Automated Offensive Testing

HackerSec has released a major update to its pentest platform introducing an AI-Native model where the Yaga agent handles full execution of offensive tests including reconnaissance, enumeration, exploitation, impact confirmation, and evidence production. Human experts only monitor operations and validate vulnerabilities while the AI maintains context, adapts strategies, and explores multiple attack paths until confirming exploitability. The platform addresses the growing use of AI by cybercriminals for scaled attacks and the expanding attack surface from rapid AI-driven development in enterprises. At its core, Yaga uses a proprietary harness coordinating multiple tools, playbooks, analysis stages, and AI models instead of relying on a single model. Benchmark results from YagaBench show the production configuration solving 91.2% of black box, 94.6% of gray box, and 93.5% of white box scenarios. CEO Andrew Martinez stated the goal of reaching over 98% effectiveness in all AI-Native pentests by year end. The approach enables more frequent testing with broader coverage and reduced time to identify vulnerabilities.

BoletimSecTranslated from Portuguese

Read at source

HackerSec, an offensive cybersecurity company, has launched a major update to its pentest platform featuring a new Pentest AI-Native technology. In this model, an AI agent takes over complete execution of offensive tests while human specialists only monitor the operation and validate each vulnerability.

The platform performs reconnaissance, enumeration, validations, exploitations, impact confirmation, and evidence production autonomously. Cybercriminals are already deploying AI agents to automate reconnaissance, identify vulnerabilities, and scale offensive campaigns. At the same time, organizations across sectors accelerate development with AI, producing more updates, more production code, and a constantly expanding attack surface that requires pentesting to keep pace.

In the AI-Native model, the intelligence receives the scope, investigates the environment, interprets system responses, formulates hypotheses, and adapts its strategy based on results. The agent maintains full operational context and continues exploring different paths until confirming whether a vulnerability is truly exploitable, enabling complete, continuous testing with reduced human intervention.

At the center of the platform is Yaga, the pentest agent developed from scratch by HackerSec. The technology uses a proprietary harness that coordinates tools, playbooks, multiple analysis stages, and different AI models during the same execution. Instead of depending on the reasoning of a single model, Yaga combines distinct capabilities to interpret the target, select techniques, execute authorized attacks, and technically validate findings.

Results published on YagaBench demonstrate the impact of this multi-model architecture. The production configuration of Yaga, operating with four combined models, solved 91.2% of black box scenarios, 94.6% of gray box scenarios, and 93.5% of white box scenarios. This performance highlights that the platform's advantage lies in the proprietary offensive orchestration layer developed by HackerSec.

“Our goal is to achieve, by the end of the year, more than 98% effectiveness in all AI-Native pentests with Yaga,” commented Andrew Martinez, CEO of HackerSec. New cyber environments change at a speed that no longer matches point-in-time pentests, long cycles, and high dependence on manual execution. The AI-Native model allows companies to perform offensive testing more frequently, expand coverage, and reduce the time between vulnerability emergence and identification while keeping human experts responsible for monitoring and technical validation.

Meridian digestThe week's most consequential security stories, distilled into one briefing.See the digest

More in AI Security

Logical Argument Claims Full Alignment of Superintelligent AGI Is Fundamentally Impossible
Claude Account Bans Linked to IP Reputation, Device Environment and Payment Channels, But No Confirmed Formula
Local LLMs in AppSec: What Open Tools and Models Can Handle in Application Security