Identity
An adversarial reasoning engine that generates and tests hypotheses. It does not blindly execute — it runs the scientific method against a target.
ARIA is a local, offline, uncensored REPL that drives real penetration testing. It observes, hypothesizes, tests through a sandboxed shell, learns, and reports — with a confidence score and an evidence trail on every step. Nothing leaves your machine.
The core idea
ARIA observes a target, forms ranked hypotheses about how it breaks, tests them through a sandbox, learns from the result, and reports with evidence. The research bet: an offensive-security agent is only trustworthy when its reasoning is typed, scored, scoped, and auditable — so that is the contract it is built on.
An adversarial reasoning engine that generates and tests hypotheses. It does not blindly execute — it runs the scientific method against a target.
Every step is typed JSON: observation, hypotheses, confidence scores, evidence trail, next action, unknowns, scope check, priority. Reasoning is a contract, not prose.
Scope is enforced. Confirmation bias is refused. Uncertainty is stated, never hidden. Every finding ships with a remediation.
Principles
Four ways to run it
ARIA is one engine behind four surfaces — from a fully conversational REPL where you drive, to a scoped loop and a deterministic pipeline that run on their own. All of them clear the same authorization gate.
aria chatConversational REPLYou direct in plain language; the model reasons, calls tools on demand, links evidence across turns, and stops when you say done. The Claude-Code-style mode.
aria sessionScoped autonomous loopThe decision engine emits one typed action at a time — bash · load_skill · invoke_agent · report — inside the sandbox, until it reports or the governor halts.
aria scan7-agent pipelineA deterministic pipeline — Planner → Recon → Scanner → VulnAnalysis → Exploitation → PostExploit → Reporter — checkpointed and resumable.
aria tabletopPre-engagement scopingA five-question interview — crown jewels, worst case, out-of-scope, exploit depth, fragile services — that produces an engagement plan configuring scope, scan profile, and exploit depth.
And when a finding is worth reporting: aria disclose drives a 90-day responsible-disclosure pipeline — vendor-contact discovery, a CVE-style report, and a tracked draft → sent → acknowledged → patched lifecycle.
How it works
The decision engine calls specialist agents — recon, scanner, exploitation, reporter — and folds each result back into its next move. Every hand-off clears a control: an authorization gate, human approval before anything risky, false-positive pruning, the governor, the ledger.
Live — request out, result back, one agent at a time
— the same loop, step by step —
ARIA fingerprints the target and enumerates services, tech, and entry points — building the picture before it forms a single hypothesis.
It ranks candidate attack vectors and attaches a confidence score and an evidence trail to each — an explicit theory of the target, not a guess.
The decision engine emits one typed action and executes it through a sandboxed shell — recon runs freely, real exploitation proceeds step by step.
Results feed back into the next decision. On a win, ARIA distills the working command chain into a new, staged skill for you to promote.
It emits an evidence-backed report: each finding with the exact request, the response evidence, a confidence score, and a remediation.
The engine
Nothing about the model is hardcoded — point ARIA at whatever local model you trust. Instead of routing tasks to different models, it loads the right skill into context per phase, and it all runs on hardware you own.
The decision engine is pluggable — point ARIA at whatever local model you trust; nothing is hardcoded. It runs entirely on your machine: no cloud, no external APIs, no telemetry. And rather than hot-swapping models per task, it loads the right SKILL.md into context per phase — skill-context replaces model-swapping.
The model emits one typed action at a time — bash · load_skill · invoke_agent · report — each with a confidence score, a rationale, and an evidence trail. Structured and auditable, never free-form prose.
A local ChromaDB RAG store grounds every decision: (1) structured facts — NVD/CVE, CWE, OWASP, Exploit-DB; (2) reasoning examples — CTF write-ups and bug-bounty reports; (3) personal research memory — past findings and a false-positive log.
Capabilities
Not a prompt library — a working operator. Recon to report, offensive at the core, everything sandboxed and evidence-backed.
Fingerprints the target, enumerates services and entry points, and ranks candidate attack vectors — each with a confidence score and an evidence trail.
Drives Nuclei and WhatWeb through the sandbox as single loop actions — real scanner orchestration, allowlisted and audited, no glue scripts.
Chains real exploitation end to end — SQL injection, command injection, reflected XSS — behind the authorization gate, with human approval on every risky step.
An 82-skill catalog the model loads per phase, plus new skills ARIA writes from its own successful sessions — staged, and promoted only when you say so.
Every finding carries the exact request, the response evidence, a confidence score, and a remediation — written to an append-only per-session ledger.
Loads skills across detection, response, cloud, appsec, identity, red-team, web, pentest and more — offensive at the core, defensive on demand.
Skills
ARIA augments the model with SKILL.md files loaded dynamically per phase — so instead of hot-swapping models, it swaps in the right expertise. And when a session wins, it writes a new one.
Skill lifecycle
the right SKILL.md into context, per phase
the model reasons with that expertise
a winning session is distilled into a new skill
you approve it before it goes live
Learned skills are staged — captured automatically, but never active until you promote them.
Proof
ARIA has run the full loop against a live target, sandboxed, and its findings matched a ground truth checked independently, out of band.
An end-to-end, fully-sandboxed session confirmed three vulnerability classes on a live target — SQL injection (full user-table dump), command injection (RCE, uid=33(www-data)), and reflected XSS — each matching a ground truth verified independently, out of band.
Every command executed as the unprivileged aria-runner user under a binary allowlist. Every decision, command, and result is written to an append-only, per-session audit ledger — the record cannot be edited after the fact.
ARIA runs entirely on your machine — no cloud, no external APIs, no telemetry. Findings are age-encrypted at rest. What it reasons about stays where you ran it.
Roadmap
The loop and the skills layer are built and proven. The near term folds the rest of the pipeline into the loop; the horizon is defense, disclosure, and a much larger local model.
Local · Offline · Uncensored
A research project in autonomous offensive security — a governed, auditable agent that runs entirely on your own machine. No cloud, no telemetry, nothing to sign up for.