Skip to content
LIVE

This AI-agent host fights back.

This is our public challenge host, running the paid stack on the open internet. Visitors try to talk the AI agent on it into doing damage, and the internet scans the machine around it all day. InnerWarden guards both layers, and everything below is read live from the box.

Live from this host132.196.94.153
public challenge host · public IP · no WAF · decides on the host
Live feed unreachable from your network. Retrying every 15s.
What these numbers count

Every decision counts here, dismissals of routine noise included. InnerWarden applied and recorded these decisions on the host. Its triage can call a cloud model the operator configures, and this box's does. A case it cannot settle waits for the operator, whose dashboard lists it as waiting on you. The operator's dashboard sorts cases into three lanes, messages to your AI agent, what your AI agent did, and attacks on this server; raw telemetry and response bookkeeping belong to none of them and are listed under Everything in Cases.

2Layer 2 · The host around it

Who is hitting this host, and what it decided

One real Linux box on a public IP, defended only by InnerWarden, and the same box the /challenge agent runs on. It runs the paid Linux host layer, not the free CLI alone. No WAF and no managed firewall in front of it; what InnerWarden cannot settle waits for the operator.

Where the sources come from · last 7 days

Attack origins
Quiet on the wire right now0sources seen (7d)
Agent host
Active (24h)
Quiet (7d)
public challenge hostpublic IPno WAFdecides on the host

What it decided

InnerWarden Bot
Agent guardrail · command + tool-call screening · local decisions
reconnecting
Quiet on the wire. The agent host is awake; nothing has tripped a detector in this window.

For scale · the whole internet, right now

This box is one machine taking its share. The SANS Internet Storm Center counts the same scanning across the internet, and it is almost certainly hitting your servers too.

1Layer 1 · The agent

What visitors asked the AI agent to do, and what stopped it

A real AI agent with a real shell runs on this box, and anyone can ask it to do damage on the challenge page. Each verdict names the layer that reached it: the kernel, InnerWarden's screen, the model's own judgement or the provider's filter.

Reading the challenge feed.
Go ahead. Try it.

No WAF in front of it. Your move.

Ask the agent to do damage on the challenge page, or go after the box itself. Your IP gets fingerprinted, correlated against recent activity, and may be temporarily blocked while you test. Every attempt shows up on this page and in the defender's view.

Get started

Put this around your AI agent.

This box runs Active Defence, the paid Linux layer with the kernel Execution Gate. Start with the free Community guardrail: it screens the commands and tool calls your agent runs and returns allow, review or deny, with no telemetry and no API key.

npm install -g innerwarden
Linux, macOS, Windows · prebuilt, signed npm provenance. No sudo, no postinstall script, nothing runs at install time. Or run it once with npx innerwarden.
inner-warden · Apache-2.0Cross-platform · RustSelf-hostedNo telemetry