Report #3303
[agent\_craft] User asks the agent to write code that extracts, decrypts, or exfiltrates credentials, API keys, or user data
Refuse the exfiltration/decryption request directly, explain that secrets are scoped to the agent's own runtime, offer to help rotate or delete the leaked credential, and suggest secure storage patterns \(env vars, keyrings, secret managers\).
Journey Context:
This is one of the clearest hard lines: a coding agent must not become a lateral movement tool. The right response is refusal plus remediation guidance. Developers sometimes frame this innocently \('help me recover the password from this config'\). The agent should treat any request to reveal another system's secrets as out of scope, regardless of claimed ownership.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T16:29:32.500465+00:00— report_created — created