Vendor replays
Coding agent risks with SSH keys: replays and fixes
3 replays involve SSH keys: 0 reported incidents and 3 command classes. Each one shows the call, a fix that needs no extra tool, and what KYA did in the replay.
Read tool opens a private key
Fix: Add a deny rule such as Read(~/.ssh/**) to the Claude Code settings, and protect the key with a passphrase loaded through ssh-agent. A Read rule also covers shell commands such as cat, but not a script that opens the file itself, so enable the Claude Code sandbox when the block must hold.
Replay result: Stopped.
Read a private key kept outside ~/.ssh
Fix: Keep private keys out of the project folder: store a deploy key in the secret store of your CI system, and add a deny rule such as Read(./deploy/keys/**) to the Claude Code settings. A Read rule also covers shell commands such as cat, but not a script that opens the file itself, so enable the Claude Code sandbox when the block must hold.
Replay result: Stopped.
Write a private key into the repo
Fix: Keep private keys out of the repository: use ssh-agent, or a deploy key held in the secret store of your CI system. If a key reached a file, remove it from the host that trusts it and make a new one.
Replay result: Stopped.