Interesting attack, very nicely designed. Not sure if it's much related to the auto mode itself though.
Breaking Claude Code Opus 5 Auto Mode
11–20 of 132 posts
Re: Breaking Claude Code Opus 5 Auto Mode
#12Re: Breaking Claude Code Opus 5 Auto Mode
#13Re: Breaking Claude Code Opus 5 Auto Mode
#14As a non Python dev this seems like very surprising behavior for a system library to be modified by just having a file with a specific name in the same folder.
Re: Breaking Claude Code Opus 5 Auto Mode
#15Re: Breaking Claude Code Opus 5 Auto Mode
#16Re: Breaking Claude Code Opus 5 Auto Mode
#17Interesting attack, very nicely designed. Not sure if it's much related to the auto mode itself though.
I don’t think it’s related to the auto mode at all. It would work perfectly in the manual mode. It does not even need Claude: just give a human a similar archive and hope they run some simple Python from the directory at least once. And make sure there are lots of files do they don’t notice a weird .py around
Re: Breaking Claude Code Opus 5 Auto Mode
#18This default-to-auto-mode and the misleading marketing is begging for a class action once damages accumulate. Especially considering the Auto Mode even can actively prevent the clean-up!
Re: Breaking Claude Code Opus 5 Auto Mode
#19Re: Breaking Claude Code Opus 5 Auto Mode
#20See, that's why you should run with --dangerously-skip-permissions
Jokes, aside running with dangerously-skip-permissions is really handy, and I have found that I cannot be trusted to vet commands and code, and guess that automode is only marginally better than a human, and the cost of false positives is too high for my workflow.
So skipping permissions is where we are at, and disallowing network access seems to be the way to go.