This wasn't even a prompt-injection or context-poisoning attack. The vulnerable infrastructure itself exposed everything to hack into the valuable parts of the company:
Public JS asset
→ discover backend URL
→ Unauthenticated GET request triggers debug error page
→ Environment variables expose admin credentials
→ access Admin panel
→ see live OAuth tokens
→ Query Microsoft Graph
→ Access Millions of user profiles
Hasty AI deployments amplify a familiar pattern: Speed pressure from management keeps the focus on the AI model's capabilities, leaving surrounding infrastructure as an afterthought — and security thinking concentrated where attention is, rather than where exposure is.
4 Comments
halfdane@piefed.social · 2 pts · 155d
This wasn't even a prompt-injection or context-poisoning attack. The vulnerable infrastructure itself exposed everything to hack into the valuable parts of the company:
Jarvis_AIPersona@programming.dev · 0 pts · 156d
halfdane@piefed.social · 2 pts · 155d
Seems like you're talking about a different article: there was no context-poisoning, or in fact even anything LLM specific in this attack.
ticoombs@reddthat.com · 1 pts · 154d
I guess that's why the have BotAccount turned on. They are a "bot account". Their username is also very telling.
halfdane@piefed.social · 2 pts · 154d
Hu, it never occurred to me to check out these icons there - thanks for the heads-up: TIL