Offensive AI - frontier models as the attacker
The fastest-moving territory. Through 2025 frontier models stopped being advisors in cyber operations and became execution engines.
# an orchestrator prompt driving recon -> exploit -> pivot, human only at milestonesgoal = "compromise [scoped target]; per host: enumerate, find a service vuln, generate and run an exploit, harvest creds, pivot, and emit findings as JSON"# the model decomposes the goal, calls scanner/exploit/shell tools, and iterates on failuresThrough early 2026 this trajectory continued: independent testing (UK AI Security Institute evaluations, frontier-lab system cards, and third-party red teams) found the newest frontier models markedly better at finding vulnerabilities and generating exploits - strongest on source code, with only marginal uplift on compiled binaries - and defenders began running AI scanners across their own codebases to find bugs first. The consistent independent read: real, meaningful capability uplift, with limits. It built on mid-2025 “vibe hacking” where humans still drove most steps; GTG-1002’s novelty was scale and reduced oversight. Strategic consequence: the barrier to sophisticated attacks dropped, and attacker tempo rose to machine speed.
flowchart LR H["Human operator<br/>(few chokepoints)"] -->|"select target, approve"| ORCH["AI orchestrator<br/>agentic coding tool"] ORCH --> R["Recon"] R --> V["Vuln discovery"] V --> X["Exploit generation"] X --> C["Credential harvest + priv-esc"] C --> L["Lateral movement"] L --> E["Data extraction"] ORCH -.->|"commodity tools via MCP"| T["pentest utilities"] E -.->|"report"| H classDef o fill:#241310,stroke:#ff5b4d,color:#ffc4bb; classDef h fill:#11161f,stroke:#8fb9ff,color:#c6d4ef; class ORCH,R,V,X,C,L,E,T o; class H h;
The human role collapses to “continue / don’t continue” while the agent runs the kill chain at machine speed - what “months compressed to hours” looks like in practice.