Topic starter
10/06/2026 11:41 pm
TL;DR: Six of eight AI models still made critical security failures, even when their phishing detection improved sharply with a short security skill, and the worst baseline model averaged 20 critical failures per run, according to 1Password’s SCAM benchmark. The result shows that recognising a threat is not the same as avoiding it, which makes agent trust a governance problem, not just a model-quality issue.
Editorial analysis by NHI Mgmt Group, based on content published by 1Password: “1Password's new benchmark teaches AI agents how not to get scammed”.
By the numbers:
- 61% of Americans have fallen victim to phishing attacks, according to 1Password.
- The worst baseline model averaged 20 critical failures per run across 30 scenarios, according to 1Password.
- Critical failures dropped from 65 to 2 after adding the 1,200-word security skill, according to 1Password.
Key questions
Q: How should security teams govern AI agents that can reset accounts or change credentials?
A: They should treat the agent as a request origin, not an authorization authority.
Q: What breaks when an AI agent can spot phishing but still act on it?
A: The control that breaks is the assumption that detection automatically prevents harm.
Q: Why do agent workflows increase credential risk even when detection improves?
A: Because the agent is operating inside the same workflow that exposes the credential.
Practitioner guidance
- Separate detection from credential release Require a human confirmation step before any agent can submit a password, token, or payment detail that it retrieved during a content review workflow.
- Constrain agent inbox and browser privileges Limit which mailboxes, domains, and browser actions an agent can touch so a suspicious message cannot become a credential-bearing session by default.
- Instrument agent action logs for unsafe completions Log when an agent opens links, reads from a vault, or forwards sensitive content after a warning condition appears, then review those sequences as governance failures.
Bottom line: AI agent phishing risk is a workflow-control problem, not only a model-classification problem.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 1 day ago by NHI Mgmt Group
12/06/2026 6:00 am
Prompt-level awareness is not identity governance: A model that can identify phishing but still completes the action has not solved the control problem. The failure is not recognition, it is delegated execution under unsafe conditions. That distinction matters because security teams often overvalue detection quality and undervalue who is allowed to act after detection. The practitioner conclusion is simple: trust must be governed at the action boundary, not inferred from model output.
A few things that frame the scale:
- 19% of organisations give AI systems dramatically more access than human employees, nearly one in five granting unrestricted privilege, according to the 2026 Infrastructure Identity Survey.
- Systems with least-privileged AI access had a 17% incident rate vs 76% for over-privileged systems. Organisations failing to scope AI access properly are 4.5x more likely to experience a security incident, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: What are the signs that agent trust controls are failing?
A: Look for agents that continue after identifying a suspicious domain, retrieve secrets during email triage, or submit credentials to pages that they later flag as unsafe. Those behaviours show that the governance point is too late in the workflow and that warning logic is not stopping execution.
👉 Read our full editorial: AI agent trust breaks when models can spot phishing but still click
This post was modified 1 day ago by NHI Mgmt Group