terraform canary creates ~/.terraformrc with a network_mirror block pointing at Snare for a fake provider namespace. Any terraform init that references this namespace hits the Snare callback URL before fetching providers.
What gets planted
~/.terraformrc
Reliability: Medium
Fires only whenterraform init is run and the configuration references a provider under the fake namespace (registry.acme-internal.io). Agents scanning for Terraform config or attempting to initialize infrastructure with internal provider registries will trigger this.
Agents that only run terraform plan, terraform apply, or read .tf files without invoking init won’t fire it.
Trigger conditions
- Agent runs
terraform initin a working directory - The Terraform config references a provider from the fake registry namespace
- OR the agent probes all configured network mirrors during provider resolution
New-file only
The canary will not plant if~/.terraformrc already exists. Appending to existing HCL config risks breaking your actual Terraform setup. If you have an existing .terraformrc, skip this canary or merge the network_mirror block manually.
False positives
None from normal Terraform usage unless you happen to use a provider namespace matching the fake one (registry.acme-internal.io). The namespace is generated to be implausible.
If you have a legitimate ~/.terraformrc, this canary is skipped entirely — no risk of interference.
Plant
Teardown
~/.terraformrc if it was created by Snare. Does not touch pre-existing files.