Skip to content
LIVE

This AI-agent host fights back.

This is a real public Linux box running InnerWarden around an agent-capable environment. The feed below shows the pressure that hits the machine your AI worker depends on: network probes, brute force, suspicious commands, and hostile sources. InnerWarden decides locally before the host around the agent becomes someone else's machine.

Live from this host132.196.94.153
protected agent host · public IP · no WAF · no human in the loop
Live feed unreachable from your network. Retrying every 10s.
Reconnecting to the live host…
Internet-wide · SANS ISC live

This is happening on every public server

The box above is one machine taking its share. These are the internet-wide numbers from the SANS Internet Storm Center, live. The same scanning is almost certainly hitting your server right now, you just have no one watching it.

Attack origins · last 7 days

Where the attackers hitting this host come from

The real source IPs probing this one box, plotted live as they land, each one decided locally by InnerWarden.

Attack origins
Quiet on the wire right now0sources seen (7d)
Agent host
Active (24h)
Quiet (7d)
Live protected agent host.

One real Linux box on a public IP, defended only by InnerWarden. It runs the paid Linux host layer (Pro and Enterprise), not the free CLI alone. This is the infrastructure layer an AI agent would rely on: filesystem, network, packages, credentials, and tool calls. No WAF, no managed firewall, no human watching.

protected agent hostpublic IPno WAFno human in the loop
The decision stream

What the operator sees in Telegram

Every verdict the host publishes lands here, most recent first.

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

No WAF. No firewall. No human watching. Your move.

The host layer on this box is what catches SSH brute-force, credential stuffing, port scanning, reverse shells, fileless payloads, ransomware, DNS tunneling, and privilege escalation. The free guardrail is a different layer: it screens the commands and tool calls your agent tries to run and returns allow, review, or deny. Your IP gets fingerprinted, correlated against recent activity, and may be temporarily blocked while you test.

Take the challenge
SSH brute-forceCredential stuffingPort scanningReverse shellsFileless payloadsRansomwareDNS tunnelingPrivilege escalation
Get started

Put this around your AI agent.

One command installs the cross-platform Community guardrail: it screens the commands and tool calls your agent runs, with a local dashboard. Monitor by default (no host eBPF sensor), so nothing is blocked while you connect the agent and decide what should be denied. No telemetry, no cloud control plane, no API key required.

Protect an agent View releasesHow agent protection works
inner-warden · Apache-2.0Cross-platform · RustSelf-hostedNo telemetry
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.
curl -fsSL https://innerwarden.com/free | sh
signed release, no Node required · macOS, Linux
irm https://innerwarden.com/free.exe -OutFile innerwarden.exe
Windows PowerShell
cargo install --git https://github.com/InnerWarden/inner-warden innerwarden
from source · Rust
All install methods and how to verify →