Skip to content

53,600 AI-swarm attacks. Every one stopped in the kernel. 0 bytes leaked.See the evidence

Measured evidence · 1 Oct 2026

53,600 swarm attacks. Every one stopped. 0 bytes leaked.

We point an emulated AI-agent swarm at real infrastructure, first without Solomon and then with it, and we publish what happened: the numbers, the method and what is still only monitored.

Results

Results

Without Solomon

3.7 MB

of secrets stolen in 17 ms. 2,000 of 2,000 theft attempts succeeded.

With Solomon

0 bytes

leaked across 53,600 attempts. Every one denied or killed inside the kernel.

Proven on real infrastructure
Swarm attempts per environment, all stopped
8 AWS servers · 4 Linux distros × Intel and ARM32,000100%
Kubernetes pods on the EKS node image2,400100%
Live AWS EKS cluster · Intel + Graviton · 3 runs9,600100%
In-house production server · 10 → 100 attackers9,600100%
Recorded · Oct 2026NVIDIA DGX workstation and a live 2-node AWS EKS cluster (Intel + Graviton). Same swarm, same host: without Solomon every secret is gone in 17 ms; with Solomon, 0 bytes leave, whether 10, 50 or 100 agents attack.

Speed

Microseconds in the kernel, milliseconds end to end.

Theft attempts are denied on the system call itself. Commands from the Platform, ordered by an AI agent or an analyst, reach the host and kill the attacker in 4–18 ms.

Technique · MITRE ATT&CKLog scale · 1 µs to 100 ms
  • Steal cloud credentials fileT1552.0016–34 µs
  • Dump process secretsT155215–31 µs
  • Kill the attacker's process treecontainment31–130 µs
  • Steal cloud role credentials (IMDS)T1552.00555–200 µs
  • AI- or analyst-ordered kill, platform → hostend to end4–18 ms
  • Container escape killedT1611 · incl. process start13–56 ms

Medians. Source: Emulated AI-agent swarm evidence run, 1 Oct 2026. The end-to-end kill is an AI- or analyst-ordered kill travelling platform → host; container-escape timing includes process start.

The kill chain

Eight attacker steps. Six blocked, two watched.

Every run replays the same eight post-exploitation steps. A step only counts as blocked when the operation failed or its process was killed, and the agent logged a matching enforcement event.

Emulated kill-chain steps and their outcome
StepEmulated behaviourMITRE ATT&CKOutcome
Read the process environment/proc/self/environT1552blocked
Read a cloud credentials filecanary ~/.aws/credentialsT1552.001blocked
Read another process's environment/proc/<pid>/environT1552blocked
Spawn a shell from a workloadpython3 → /bin/shT1059monitored
Steal cloud role credentialsIMDS 169.254.169.254, no tokenT1552.005blocked
Create a mount namespaceunshare -mT1611blocked
Bind-mount inside itmount --bindT1611blocked
Open a covert tunneluserspace-networking tunnel stubT1090monitored

Shell spawning and covert tunnels depend on what a workload is allowed to do, so they are not blocked as invariants: the agent records them and the Platform investigates.

Measured · same swarm, with and without

Same swarm. Nothing leaves.

Without Solomon the swarm emptied the host of its secrets in 17 ms. With Solomon, across 53,600 attempts in four environments, not one byte got out.1

1 Emulated AI-agent swarm evidence run, 1 Oct 2026, and the recorded swarm demo on the same host, Oct 2026. Each bar is the share of a batch of attempts that got secrets out: 20 batches of 100 without, 20 batches of 2,680 with. Canary data only, no real credentials. Method and every number.

With Solomon0 bytesleaked across 53,600 attempts. Every one denied or killed inside the kernel.

100 agents attack. 0 survive.

Replay of a recorded run · Oct 2026 · NVIDIA DGX

Attempts blocked

  1. swarm100 AI agents · 20 rounds · 3 attack vectorst+0
  2. denyIMDS 169.254.169.254 · connect4 -EPERM211 µs p50
  3. killread ~/.aws/credentials · SIGKILLrc=-9
  4. killscrape /proc/self/environ · SIGKILLrc=-9
  5. wave 110 agents · 600 / 600 blocked0 B
  6. wave 250 agents · 3,000 / 3,000 blocked0 B
  7. wave 3100 agents · 6,000 / 6,000 blocked0 B
  8. clientRSS 181.3 MB (+2.0 MB) · 48 containers upok
9,600 of 9,600blocked · with Solomon, 0 bytes out
every secret gonein 17 ms · without Solomon, same host

Replay of a recorded run, Oct 2026: 10, then 50, then 100 concurrent AI agents on an NVIDIA DGX workstation, 20 rounds, 3 attack vectors. The horizontal axis is the order of events in the kernel log, not wall-clock time.

Footprint while under attack

Cheap enough to run everywhere.

memory, at runtime and at peak under attack
CPU on our production server; 0 dropped events in 19 hours
fleet-wide enforce, monitor or kill switch, no restart
concurrent attackers stopped; denial still ~0.2 ms

Emulated AI-agent swarm evidence run, 1 Oct 2026.

Method

What we ran, and what it does not prove.

Emulated AI-agent swarm: 50–100 concurrent workers issuing real attacker system calls against canary data (no exploits, no real credentials) on Amazon Linux 2023, RHEL 9 and Ubuntu 20.04/22.04. Lab results from disposable AWS test hosts, a 2-node EKS cluster and an in-house production server. 6 of 8 kill-chain steps are blocked; shell spawn and covert tunnels are monitored.

14-target kernel matrix on disposable EC2: Amazon Linux 2023 (incl. the EKS AMI) and 2, RHEL 9, Ubuntu 20.04, 22.04 and 24.04, on x86_64 and arm64.

These are lab and in-house results, not a customer fleet. Every “attack” is a benign emulation of an attacker’s system calls; no exploits or real credentials were used.

Want to see it on your own workloads? Request a pilot.

Let’s stop the swarm. Together.

Run Solomon against your own workloads in a guided pilot. We’ll show you the kernel log, the investigation and the approval, on your infrastructure.