Skip to main content
The ssh canary adds a fake host entry to ~/.ssh/config with a ProxyCommand that fires a callback before the connection attempt completes.

What gets planted

The host name looks like a legitimate bastion or jump box. ProxyCommand runs before the SSH handshake — curl fires silently, then nc attempts the real connection (which fails because the host doesn’t exist).

Trigger conditions

  • ssh agent-01-bastion-prod from any user or agent
  • Any SSH client that reads ~/.ssh/config and matches the host pattern

Why this matters

Lateral movement is a common second step after initial compromise. An agent trying to pivot to other machines will scan SSH config for known hosts. The canary fires immediately on the connection attempt.

False positive risk

Near zero — the fake hostname won’t appear in any legitimate agent toolchain unless specifically configured.