Offensive AI and AI security
Agents that carry out intrusion tasks, and tools for attacking AI systems. Two different problems, and worth not conflating them.
Where the limit sits today
None of these tools replaces an operator. What they do well is cover surface and never tire; what they do badly is decide what matters. In a DORA TLPT engagement the part the supervisor examines — the justification of the scenario and the chain of evidence — is still human, and will stay human for as long as accountability has a name attached to it.
AI that attacks
Agents that run reconnaissance, exploitation and validation. The field moves weekly; this list is reviewed on the date shown at the foot of the page.
CAI · Cybersecurity AI
FrameworkFrom Alias Robotics, in Vitoria, Spain. An agent framework for offensive security, with a published paper and verified results in bug bounty programmes. It is the most serious European project in this space, it is open source, and it is two hours' drive from here. Worth following even if you never run it.
CAI · paper
LiteratureThe paper. Read it for the evaluation methodology, which is what almost never accompanies tools of this kind: with no measurement protocol, any agent's numbers are marketing.
BugTraceAI
ScannerAn autonomous multi-agent scanner that detects, exploits and validates. The validation stage is the interesting part: it is precisely where the rest of these projects fail and end up delivering noise for somebody to discard by hand.
pentest-ai
FrameworkOrchestrates the usual tooling — nmap, nuclei, ffuf — with a model that chains and prioritises but issues no verdict: validation comes from the tool, not the model. That is exactly the right principle, and what separates a useful assistant from a generator of invented findings.
PentestGPT
PrecursorThe pioneer. Several projects now beat it, but its split between reasoning, generation and parsing remains the clearest explanation of why a bare language model does not perform a penetration test.
hackingBuddyGPT
AcademicFrom the ipa-lab group. Deliberately minimal: its value is that you can read all of it in an afternoon, and there is peer-reviewed work behind it on Linux privilege escalation. The best entry point if you want to understand the loop rather than just run it.
awesome-ai-offensive-security
CensusTo keep your bearings. A maintained census of a field that changes every few weeks. Use it as radar, not as judgement: inclusion is not endorsement.
Attacking the AI
The inverse problem, and the one we are asked about most since models went into production touching customer data.
MITRE ATLAS
TaxonomyThe ATT&CK equivalent for artificial intelligence systems. It is the shared vocabulary: without it, two reports on the same model are not comparable and the client cannot aggregate anything.
OWASP Top 10 for LLM Applications
ScopingA reasonable starting point for scope. Treat it as a taxonomy rather than a checklist: whoever walks the whole list and signs has audited the document, not the system.
PyRIT
AutomationFrom Microsoft. Automates generative AI red teaming and gives systematic coverage of adversarial prompt families. Good for breadth; depth is still manual.
garak
ScannerFrom NVIDIA. A vulnerability scanner for language models, with hundreds of ready-made probes. It is the closest thing to an nmap for models, with the same virtue and the same flaw: it tells you what is there, not what it means.
Last reviewed:
Start with the scope
A thirty-minute conversation is enough to determine whether the engagement makes sense, which type fits and what order of magnitude it carries. No cost, no commitment.