Poster of a red attack route snaking across a system map toward the core: a robot holds the route at the last node while a security engineer with headphones round his neck brings bolt cutters in to cut it.

An applied AI lab for security

Your autonomous product security team

Five AI engineers trace what an attacker can actually reach in your code, dependencies and AI agents, write the fix and open the pull request. Your team reviews and merges.

Who it's for

For security teams outnumbered by their engineers

A few security people, dozens or hundreds of engineers, and AI writing more of the code every week. The findings pile up faster than anyone reads them, and most can't be used by an attacker. Arvion adds a team that finds the ones that can, writes the fix and opens the pull request, so your people spend their time on the decisions.

Try it · sample app

Break this checkout One field is enough

This refund page has a flaw our team found in a sample repo. Get the server to run a command of your own. If you’d rather skip the puzzle, one tap shows you the trick.

214findings in this sample repo. One of them starts at this field.

acme-checkout.example/refunds/42v1.8.3 · patched

Download your refund receipt

Server log

POST /refunds/42/receipt {"orderRef": "A-1093; id #"}

$ receipt-gen --order A-1093; id # --out /tmp/rcpt-1730812.pdf

receipt-gen: --out is required

uid=1001(api) gid=1001(api) groups=1001(api)

↑ id ran on the server as the api user

Same trick. Nothing ran.

SSaga · application code

I found this route in the code before you did.

  1. POST /refunds/42/receipttracedorderRef arrives as A-1093; id #
  2. routes/refunds.js:46tracedgoes into a command string, unchecked
  3. routes/refunds.js:47tracedexec() runs it through /bin/sh
  4. the API service accountassumedcan read the payments database password. We don't attack your systems to check this, so it's assumed.

WWright · remediation

The fix is ready: PR #4127. It checks the order reference and runs receipt-gen without a shell. Tests pass.

   const { orderRef } = req.body;+  if (!/^[A-Z]-\d{1,8}$/.test(orderRef))+    return res.status(400).json({ error: "bad ref" });-  exec(`receipt-gen --order ${orderRef} --out ${out}`, done);+  execFile("receipt-gen", ["--order", orderRef, "--out", out], done); +  it("rejects shell syntax in orderRef", () =>+    post({ orderRef: "A-1093; id #" }).expect(400));

Deployed as v1.8.3. Now send the same trick.

POST /refunds/42/receipt {"orderRef": "A-1093; id #"}

400 bad ref

Nothing ran. The check stopped it before any command was built.

What the team did on this repo

  1. Reviewed214 findings. 213 filed, each with its reason.
  2. The one that mattersThe route you just used, from this form to the shell.
  3. Fix writtenPR #4127, with a test that sends your trick and expects a 400.
  4. Couldn't checkWhat an attacker reaches past the API service. Marked assumed.

Three of the 213 it filed, each with its reason

  • lodash 4.17.20_.template is never called
  • minimist 1.2.5pulled in by the build tooling only
  • routes/health.jsexec() always runs the same command
Book 15 min

Bring one data source. You leave the call knowing which of your findings were worth the afternoon.

Who you employ

Five security engineers, at your service

Each engineer is an autonomous agent with a specialized role. The team works together to safeguard your code.

Saga — Application code
Application code

Saga

Saga is a tracing expert. She traces untrusted input from the entry through your source code to the places it could do damage, and reads configuration and infrastructure definitions for hardcoded credentials, unsafe settings, or anything opened to the whole internet.

“I traced how a request to POST /refunds can reach a shell command. Here is the exact path it takes.”

The limits you set

Three rules the team works by

The same three rules apply to every engineer on the team. The product enforces them word for word.

  1. First Law

    An engineer may not claim more than it proved — nor, by staying silent, let you believe you are safe when you are not.

    In practiceEvery step of an attack path is marked traced or assumed. Code the team couldn't analyze is reported as not analyzed.

  2. Second Law

    An engineer works to the clearance you set and no further — except where obeying would break the First Law — and hands you every call that is yours.

    In practiceYou set what each engineer may do. After ten fixes of one kind are merged in a row, the team asks to open that kind on its own. If too many get rejected, it steps back. Nothing merges without your team.

  3. Third Law

    An engineer guards the one thing that lets it exist — your trust — but never by hiding a failure, faking a preview, booking a win it did not earn, or reaching past the clearance you set.

    In practiceA finding the team sets aside comes with the reason written down. A run that didn't finish says so.

Your team is outnumbered. Add five engineers.

Pick the domain that's loudest — your AI agents, your code, or everything you pull in. One engineer works it end to end: what is worth fixing, the fix written, delivered where your team already works. The rest gets filed, with the reason printed.

Book 15 min →

A work call: you connect one source, we run it live, and you leave with whatever it found and wrote.

  • One data source to start
  • No agent runs without your clearance
  • You decide what gets fixed

Prefer email to calls?

Leave one source and we will come back with what it found and the fix it wrote.

One data source is enough to start, a public repository is the fastest; your cloud, IaC and agents follow the same way in.

By proceeding, you accept our Terms & Privacy Policy