AWS merges malicious PR into Amazon Q (lastweekinaws.com)

I’m curious exactly what happened here. The 404media article isn’t detailed enough to be sure. My guess is the PR took advantage of some code injection possibilities in the GitHub Actions on the repo to grant the attacker admin access. But that’s a wild guess.

I guess they put their AI in charge of code review?

Copy-on-write filesystems should be the norm.

Another article came out earlier about dataloss from some vibecoding project and an automated snapshot setup would have mitigated this very issue.

I found a postmortem which seems to be well written: https://www.mbgsec.com/posts/2025-07-24-constructing-a-timel...