It works the way a penetration tester does.

Most tools scan for known patterns and hand you a list. Deus Rex reasons about the target, chains findings into real attack paths, proves what it can exploit, and helps remediate what it finds.

Five steps. Most tools do three.

  1. 01

    Discover

    Maps your attack surface and every reachable entry point.

  2. 02

    Identify

    Builds attack scenarios from your code, your traffic and the running app, ranked by severity and likelihood.

  3. 03

    Verify

    Gives every scenario its own agent, whose only job is to prove it or rule it out.

Most tools stop here.

Deus Rex keeps going.

  1. 04

    Fix

    Writes the patch in code and raises it as a pull request on your repository.

    +SECRET_KEY = os.environ["DJANGO_SECRET_KEY"]See the full fix
  2. 05

    Retest

    Runs the exploit again to confirm the fix held.

With Autonomous, the pipeline runs again on every release.

Read the methodology

It writes the fix. Here's one.

  1. 1

    Opened by deus-rex-agent. The agent raised the pull request itself, with no human prompt.

  2. 2

    A real vulnerability: a hardcoded secret key, CWE-798.

  3. 3

    The fix, in code: the secret moved to an environment variable, so the app fails fast instead of running with a known insecure value.

  4. 4

    Delivered as a pull request, reviewed and merged on your terms.

1>
2Summary
python-secret-in-code
Hardcoded secret key detected
Vulnerability type
security_misconfiguration (low)
Class
CWE-798
Run id
rex-autofix-b771b8b406aa
How it was fixed

fix(settings): read SECRET_KEY from environment variable

3Patch
notebook/settings.py
@@ -18,7 +18,7 @@
1818 # Quick-start development settings, unsuitable for production
1919  
2020 # SECURITY WARNING: keep the secret key used in production secret!
21-SECRET_KEY = "django-insecure-dev-key-change-me"
21+SECRET_KEY = os.environ["DJANGO_SECRET_KEY"]
2222  
2323 # SECURITY WARNING: don't run with debug turned on in production!
2424 DEBUG = False
4Review requested · Merge when ready

Demonstrated on a Deus Rex test application.

Most AI pentesting stops at the browser.

Deus Rex already tests your mobile apps.

Built on eight years of proprietary offensive tooling and twelve years of real engagements. That is why mobile is live today, not on a roadmap.

SurfaceMost AI pentest toolsDeus Rex
WebLiveLive
iOSOn the roadmapLive
AndroidOn the roadmapLive
DesktopAbsentOur engineers todayOn the platform next
CloudVariesOur engineers todayOn the platform next
NetworkAbsentOur engineers todayOn the platform next
InfrastructureVariesOur engineers todayOn the platform next
IoT and embeddedAbsentOur engineers todayOn the platform next

Today's market makes you buy these separately. We're building them as one.

Deus Rex is built by the team behind Cyrex. In their clients’ words:

Laurent JoppartCISO, Nationale Loterij · Belgium's National Lottery.

Two ways to engage: expert-led or autonomous. Compare them

Request a proposal

Tell us what you ship. Our engineers scope it, and you get a custom proposal within five days.

Tell us the scopeProposal in five daysNo commitment