How it works
Plant
snare arm --webhook <url> places fake credentials across 18 locations. The callback URL is embedded as the real service endpoint, not a comment.Wait
Canaries sit silently. Normal tooling ignores them. A compromised agent, leaked key, or attacker with shell access will find them and try to use them.
Fire
The SDK calls the callback URL instead of the real service. Alert arrives in Discord, Slack, or Telegram in under a second.
Know
IP, ASN, SDK user agent, and timestamp tell you exactly what tried to use the credential and where it was running.
The key differentiator: awsproc
Theawsproc canary uses AWS credential_process — a shell command that runs inside the SDK’s own credential resolution path, before any API call is made. CloudTrail cannot see this step.
Three tiers
Snare canaries are rated by reliability and side-effect risk.Quick navigation
Quickstart
Up and running in 60 seconds
Canary types
All 18 canary types explained
Self-hosting
Run your own callback server inside your network
CLI reference
All commands and flags