HackerSec's Yaga Pentest Agent Reaches 98.8% Effectiveness in White Box Testing
The offensive cybersecurity company HackerSec has reported that its Yaga pentest agent attained 98.8% effectiveness in white box scenarios during the most recent version of YagaBench. The agent also achieved 96.2% effectiveness in black box testing and 97% in gray box testing, representing the strongest performance recorded since the benchmark began.
These results demonstrate that Yaga successfully identified more than 98% of existing vulnerabilities in the evaluated environments. The central purpose of the benchmark is to measure the difference between using an isolated AI model and deploying the same models inside the specialized harness developed by HackerSec for penetration testing.
For example, the model Opus 5 without the Yaga harness achieved only 61% effectiveness in white box, 48.9% in gray box, and 40% in black box scenarios. Similarly, GPT 5.6 SOL reached 60.9% in white box and 39.5% in black box testing when used independently.
With Yaga, four models operate in an orchestrated manner during a single execution, each contributing at the stage where it performs best. The orchestration layer preserves context between testing phases, chains individual findings that would otherwise lack impact, and continues active exploitation until it confirms whether a vulnerability is truly exploitable.
The company also disclosed that false positives have been reduced to less than 1%. Remaining cases are identified and discarded by human pentesters during the validation stage before reaching the client dashboard.
According to Andrew Martinez, CEO of HackerSec, the current results represent only the beginning. The company’s goal is to achieve 99% effectiveness across all pentest modalities by the end of the year. Full methodology, evaluated scenarios, and model performance comparisons are available at the company’s evaluation portal.
Related articles
Detecting Deepfakes: Tools, Signs, and Verification Methods for Video, Photos, and Voice
Deepfake technology now creates highly convincing synthetic videos, photos, and audio that can impersonate real people in video calls or voice messages. The article explains how modern neural networks using GANs, diffusion models, and transformers generate face swaps, voice clones, and fully synthetic scenes. It details visual and audio artifacts that may reveal fakes, such as inconsistent lighting, deformed fingers, or unnatural speech pauses, while noting that these signs are becoming less reliable. Practical verification steps include reverse image searches, metadata analysis, and tools like InVID-WeVerify. Specialized detectors such as DeepFake-o-Meter, Reality Defender, and Sensity AI are reviewed along with their limitations against unknown generators. Real-world cases, including a $25 million corporate fraud using deepfake video calls, illustrate the growing risks and the need for independent confirmation rather than relying solely on automated tools.
Can Open-Source AI Agents Replace Pentesters? Strix and PentAGI Tested on Real 200-Host Perimeter
An independent researcher evaluated two open-source LLM-based pentesting agents, Strix and PentAGI, against a live external perimeter containing roughly 200 active hosts. Both tools autonomously planned tasks, executed CLI utilities, generated proofs of concept, and produced reports while running inside isolated Docker sandboxes. Strix delivered only 15 findings with almost no false positives yet consistently overstated severity, while PentAGI reported 296 vulnerabilities including 42 critical issues, none of which proved exploitable. Real critical vulnerabilities on the same scope, including an RCE chain, were discovered only by a commercial autonomous scanner. The experiment highlighted fundamental limitations in scope control, context management, and risk assessment that still require human oversight. Token consumption reached 145.1 million for Strix and 31.4 million for PentAGI, illustrating the cost of maintaining long-running autonomous operations.
Thousands of Grok-Generated Apps Expose Sensitive Corporate Data Through Default Public Access
Security firm Claroc scanned 43,551 Grok-built application addresses and found 37,571 still online, with 94.7 percent requiring no login. Approximately 650 to 800 of these apps contained sensitive internal data belonging to SpaceX, X, Tesla, and 30 other organizations, including six Fortune 500 companies. Exposed records included ICU patient reports with lab results and ventilator status, contractor timesheets containing plaintext passwords, and Tesla service-center performance evaluations listing employee names, efficiency metrics, and bonuses. Researchers demonstrated that Grok sometimes inverts permission-check logic, allowing unauthorized Google accounts to view and modify data after login. In contrast, ChatGPT-generated apps default to private settings, preventing access even when URLs are discovered via passive DNS. The incident highlights how AI coding tools lower the barrier to publishing internal applications while weakening the review processes that traditionally protected sensitive data.
Enterprise Security Requirements Push Russian Developer to Deploy 125B MoE LLM Locally on Consumer Hardware
A cybersecurity journalist and platform developer detailed his transition from cloud-based AI agents to a fully local 125B-parameter MoE model after enterprise clients raised strict data-exfiltration concerns. The move was driven by the need to keep task statements, source code, configuration files, logs, and regulated personal data inside the corporate perimeter. After testing multiple inference engines, he settled on the Strata engine running a Qwen3.8-Flash-Next model quantized to IQ3_S, achieving 22-25 tokens per second generation and over 500 tokens per second prefill on an RTX 5060 Ti 16 GB GPU paired with a Xeon E5-2640 v3 and 128 GB DDR4. Extensive calibration of expert caching, PCIe fraction, KV streaming, and speculative decoding proved critical to reaching production-grade performance. The resulting setup now handles real agentic workloads such as incident investigation from traces, backlog grooming, and code generation without any data leaving the workstation. The author concludes that hybrid cloud-local workflows will become standard for development teams handling sensitive information within the next one to two years.