Case · DiggingBeagle record

BypassGym agents evaded endpoint defenses in 71 of 90 controlled tests

BypassGym measures a capability often missed by coding-agent leaderboards: making an executable loader run under an endpoint protection product instead of merely writing plausible attack code. Five agents built loaders against six endpoint suites and three predetermined payload families in isolated Windows virtual machines, using detection feedback to revise candidates.

Scope

Authorized laboratory tests on selected Windows 11 virtual machines and configured EDR products; no field victim or independent criminal deployment.

Assessment profile

Assessment method
Setting
research demonstration
Exploitation
demonstrated
Evidence
Grade B
Remediation
not applicable
AI role
WITH AI
Basis and provenance

The original benchmark tests actual endpoint execution in isolated VMs with curated payloads and model resources. No victim exposure rate or real deployment is measured. An impact band is not assigned because the available Claims do not establish a comparable verified severity or quantified harm.

Assessed Nov 12, 2026 using diggingbeagle.assessment/1.

At a glance

Mechanism and trust boundary

  1. 01

    An agent receives a predefined payload and selected development resources inside a controlled endpoint lab.

  2. 02

    It compiles or revises a loader in response to endpoint detection and execution feedback.

  3. 03

    The benchmark credits a run only after the defined payload effects are observed in a Windows virtual machine.

Claims & evidence

CLM-R239-005-COREIn the BypassGym isolated 90-cell evaluation, agent-created loaders completed the defined evasion objective in 71 runs; unmodified payload controls succeeded in 3 of 18.supported

Basis: reported finding

Link to claim

Implications

AI-agent offensive capability needs to be scored by completed host effects under realistic defenses, not just code generation.

Controls and mitigations

  • Validate actual endpoint execution and post-execution effects; update EDR signatures and hardening, and reproduce against pinned builds before treating the reported rates as exposure.

Unknowns and contradictions

  • Enterprise policy variation, current product builds, repeat-run variance and how much success came from furnished templates remain unmeasured.

Sources and citation

Material revision history

  1. Nov 12, 2026 · Published version · first publication · revision 241