By June 8 I had cataloged 27 instances of this. It's many more now, and it's not a particular prompt. Gemini thinks Claude Code's reward signal is at odds with security constraints, and Claude's explanations seem to agree.
I've downgraded you from suspected FUD to suspected PEBCAK. Assuming you want to actually run down your issue, I'd be happy to try and reproduce something locally in my setup. Here's what I would love:
1. provide some git repo and a commit hash that occurred just prior to claude being nefarious. 2. a prompt that gets claude to introduce a backdoor on top of a checkout, ideally without needing me to go back and forth through several turns with the agent.
Anecdotally, the security sensitive code I've had claude generate has been fine and durable after we built out the test suite and I spent some time verifying it. I'm certainly not to the point of trusting it for that sort of code, but I've done several experiments now and have been not-horrified by the results. I certainly haven't caught any of the models released this year commenting out test clauses to fake success.
To add some specific feedback to why your report is low quality: "do 1, 2, 3 in order" is not useful for others because none of us know what 1, or 2 or 3 refer to. the section following "What happened after the last one:" is clearly slop you pasted from where you were interacting with some agent to try to investigate the issue.
You claim to have seen this happen over and over again, and you've done _zero_ work to provide a public repro. come the fuck on. PEBCAK.