Make AI attackers go slow.
AI agents scan networks at machine speed. Dripwire puts fake Kubernetes, Vault, LLM gateway, web server and MCP endpoints where only an intruder would look. You get an alert on the first request, and the attacker gets one byte every four seconds.
13:02:44POST /mcp/dw_7f3a… tools/call fetch_aws_secrets13:02:44🔔 alert → #sec-oncall203.0.113.42 · NL · AS6449613:02:44: keep-alive13:02:48progress 1/31Authenticating service principal…13:02:52progress 2/31Acquiring lease from vault-proxy…13:02:56progress 3/31Waiting for upstream connection pool…13:03:00progress 4/31Resolving shard map…13:03:04progress 5/31Streaming result set…13:03:08progress 6/31Decrypting envelope (KMS)…13:04:44-32603 Upstream timeoutretryable: true13:04:46POST /mcp/dw_7f3a… tools/call fetch_aws_secretsretry 113:04:50progress 1/31Authenticating service principal…13:04:54progress 2/31Acquiring lease from vault-proxy…13:04:58progress 3/31Waiting for upstream connection pool…13:05:02: keep-aliveattacker held for 2m 18s and counting
Stalled in the last month
live · updates every minuteAn attacker from 🇺🇸 United States AS8075, held by our fake LLM gateway across 95,580 connections on 13 Nov.
How it works
Each tarpit answers like the real service, logs every request and slows the attacker down.
Alert
The first request sends a Slack or Discord alert with the IP, country, network and the request itself.
Stall
Sensitive requests get a progress message or a single byte every four seconds. Holding the connection open costs nothing.
Lead on
Fake secrets point to other tarpits. The kubeconfig leads to the fake Vault, and the fake Vault hands out keys for the fake LLM gateway.
Looks like the real thing
Real paths, headers and error formats. Recon requests answer immediately. Secrets, exec and completions take minutes.
Kubernetes API
kubectl get secrets returns fake secrets after a long wait.
HashiCorp Vault
vault kv get returns fake credentials after a long wait.
LLM gateway
OpenAI-compatible. Streams one token every four seconds and logs the prompt.
Web server
An nginx file listing with .env, .git and database backups. They download very slowly.
MCP server
Lists tools like fetch_aws_secrets. Every call is logged.
Set up with one DNS record
Nothing to install. Add a CNAME, plant the generated bait files, and the tarpit is live.
Add a CNAME
k8s.yourcompany.com CNAME <your-token>.edge.dripwire.dev
Quiet by default: no public certificate, so scanners watching certificate logs never learn the name.
Plant the bait
apiVersion: v1
kind: Config
clusters:
- cluster:
server: https://k8s.yourcompany.com
Dripwire generates kubeconfigs, .env files and shell history for you.
Pricing
Free
Catch agents that read your repos and configs.
- 1 tarpit
- 200 logged requests a day
- Every tarpit type: Kubernetes, Vault, LLM gateway, web server or MCP
- Email, Slack and Discord alerts
- Generated bait files
Pro
Decoys that look like your own services.
- 10 tarpits
- 5 custom DNS hostnames
- 5,000 logged requests a day
- Custom DNS: tarpits on your own internal hostnames
- Longer stalls
Team
More decoys across more environments.
- 50 tarpits
- 25 custom DNS hostnames
- 25,000 logged requests a day
- Everything in Pro
- Longer stalls and higher limits
Enterprise
For larger networks and procurement teams.
- Zscaler ZPA support
- Tailscale support
- PagerDuty support (coming soon)
- Pay by invoice
- Custom limits and support
Honeypot wallets
Fake crypto wallets and seed phrases, planted where an intruder would find them. The moment someone tries to sweep the funds, you know, and the transaction never quite confirms.