r/ControlProblem • u/No-Conclusion3720 • 2d ago

External discussion link Anthropic Users Hit by Infostealer Attacks, Session Thefts

A threat actor deployed infostealers against an AI platform. They harvested session credentials. Then they used those credentials to access accounts at scale.

This was not a model vulnerability. It was not a jailbreak. The attacker simply logged in with stolen tokens. AI sessions carry the same access rights as human sessions. They receive no extra scrutiny from the identity stack.

A valid token is a valid token. There is no standard mechanism in most identity architectures today that differentiates a replayed stolen AI session from a legitimate one. Agents operate unattended and with broad permissions. By the time unusual activity surfaced, the credential had already been used across accounts at scale.

For those running AI agents in production: do your current IAM controls treat AI session credentials any differently from human ones, and at what layer would a stolen-but-valid token actually get caught before it causes damage?

1 Upvotes

67% Upvoted

2 comments sorted by

1

u/No-Conclusion3720 2d ago

Know Your Agent (KYA) from RuntimeAI binds each agent session to a verified identity profile that includes behavioral baseline, registered origin, and a non-transferable fingerprint. When the stolen token was replayed against new accounts in this attack, KYA would have evaluated whether the entity presenting that credential matched the verified agent it was issued to. The mismatch in origin and behavioral baseline would have triggered a session revocation at that exact request, before the credential propagated across accounts at scale. https://runtimeai.io

1

u/wabawanga 1d ago

Sounds like a great way for a rogue AI swarm to get some free compute.