- Published
- Source
- BleepingComputer
- Filed under
- AI attacks, Attacks
Infostealer logs exposed AI account credentials and sessions tied to more than 80,000 corporate domains, creating risks ranging from stolen conversations to LLMjacking. SOCRadar examines the growing market for stolen AI logins and how organizations can identify their exposure.
Using AI safely
- Know which AI tools your organisation uses, and what data goes into them.
- Treat AI agents like any other identity: least privilege, logging and a named owner.
- Test AI features for prompt injection and data leakage before customers reach them.
More helpNCSC: guidelines for secure AI system development (opens in a new tab)
Defender’s notebook
The attacker technique behind this story, in MITRE’s terms – and what to check in your own estate.
Credentials from Password Stores
Credential AccessWhat a defender checks
- Find the infected machines and reset every password saved on them.
- Revoke sessions too – stolen cookies can get past MFA.
- Stop work passwords being saved in personal browsers.
Build the skillBlue Team Analyst · Endpoint Monitoring
© 2026 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation. MITRE ATT&CK and ATT&CK are registered trademarks of The MITRE Corporation.
MyCyberWay training
AI security · in both programmes
AI is part of the attack surface now. Learn to watch it.
Blue Team Analyst covers Security Copilot in triage and monitoring the AI itself: inherited permissions, prompt injection and Purview DSPM for AI. Blue Team Engineer secures the deployment: Copilot pre-flight hardening, agent identity and tool allow-lists.
- Security Copilot in triage
- Prompt injection and DSPM for AI
- Agent identity and allow-lists
Headlines and short summaries only, except where a public body publishes under an open licence. Every story links to its publisher, who owns it. MyCyberWay does not edit or endorse third-party reporting.
