- Published
- Source
- The Hacker News
- Filed under
- AI attacks, Attacks
The bug was simple: the login let you choose where your sign-in code went. Proving it on a live website was the hard part. TL;DR During an authorized assessment, an AI pentesting agent found a critical authentication bypass on a major insurer's production website, on its own. One login request let the user choose where the one-time passcode went. The attack was the easy part. Proving it…
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)
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.
