Demonstration · Red team

ULTIMA: adversarial workbench

We do not ask you to trust that our implementations are sound; we attack them ourselves, on purpose, and gate the fix so the same weakness cannot return. ULTIMA is the purple-team loop behind Qrypto Federal: it finds, ZAP hardens, and a resilience gate locks the result.

findharden gatedefensive only

Demonstration: a walkthrough of the ULTIMA method. No live attack is executed from this page.

The loop

Find, harden, gate

Find
ULTIMA attacks the implementation
Harden
ZAP fixes the root cause
Gate
a regression gate locks it

A finding is only closed when a gate proves the fix and would catch the regression, not when someone says it is fixed.

What it looks for

Implementation security, not just algorithm choice

Choosing a NIST algorithm is the easy part. The failures that matter live in the implementation: timing side channels, decryption oracles, missing consistency checks, and trust stories an artifact cannot actually support.

Constant-time

Timing & side channels

Secret-dependent branches and memory access are measured against a constant-time gate; a secret should not be readable from how long an operation takes.

Oracles

Decryption-failure oracles

Implicit rejection is preserved: a bad ciphertext must not be told apart from a good one before the authentication tag, or the decision leaks.

Consistency

Pairwise & verify-after-sign

Keys are checked for pairwise consistency and withheld on failure; signatures are verified after signing before they are relied upon.

Trust stories

Claims the artifact supports

A label like “post-quantum” or “forward-secret” is only allowed where the artifact actually provides the property; the mismatch is the finding.

Run an attack

Execute from this page

The live ULTIMA workbench runs inside the enclave against authorized, in-scope targets only. No attack is launched from this public page.

Run timing probe (not enabled) Run oracle probe (not enabled)

FLAG: not executable here, by design. ULTIMA operates on our own stack or an explicitly authorized target, inside the sovereign edge, with results graded and disclosure owner-gated. It is defensive and legitimate-use only. These controls are intentionally disabled in this public demonstration; nothing on this page attacks anything.

Hold us to it

Ask how we attack our own implementations before we ship them.