"Microslop" is kind of catchy.

https://www.windowslatest.com/2026/03/02/microsoft-gets-tired-of-microslop-bans-the-word-on-its-discord-then-locks-the-server-after-backlash/

Two AWS outages, including the 13 hours one, were caused by coding agents deleting what they shouldn’t, in production.

AWS points to the engineers:
“We’ve already seen at least two production outages,” one senior AWS employee told the publication. “The engineers let the AI resolve an issue without intervention. The outages were small but entirely foreseeable.”

Coding agents are everywhere, they are privileged, we have zero visibility into what they do, and they bypass classic CI/CD and cyber defense controls.
Even finance is using them. I’m unsure how much engineers could actually do to prevent these incidents.

If you are concerned by these, I’d start by asking the following questions:
- What coding agents are you running?
- What MCP servers, extensions, or skills are your developers using?
- Do you have preventative controls for agents stepping out of bounds?
- Do you have detection and response capabilities to stop attacks?

Original article:
https://www.tomshardware.com/tech-industry/artificial-intelligence/multiple-aws-outages-caused-by-ai-coding-bot-blunder-report-claims-amazon-says-both-incidents-were-user-error

—
And if you made it this far, defending agents is what I do.
If you want to see a demo of how you can discover and protect agents, drop me a line.

Knostic has been doing this for a while, unlike the 50 vendors now rebranding themselves in the space. :)

https://knostic.ai/