QBE North America and Control Risks warned that agentic AI can accelerate commercial espionage and fraud, citing a survey of 400 U.S. decision makers in which 29% said they had experienced a cyber incident where AI was believed to be involved. The security takeaway is that autonomous tool use changes the defender's problem from one-off content generation to multi-step campaigns that can chain reconnaissance, credential abuse, phishing, and data theft. QBE's report and insurance trade coverage frame the risk as faster and cheaper attack execution, so practitioners should prioritize identity telemetry, tool-call monitoring, and cross-system anomaly detection rather than treating AI misuse as only a content-filtering issue.
Agentic AI raises the risk profile for commercial espionage because it can turn reconnaissance, social engineering, credential abuse, and follow-on exploitation into longer automated workflows. For security and ML teams, the practical shift is from detecting generated content to detecting autonomous behavior across identities, tools, APIs, and data paths.
What happened
QBE North America released a report with Control Risks on commercial espionage and fraud in the era of agentic AI. The report says agentic systems can lower the skill and cost needed to conduct multi-step attacks, and QBE's survey of 400 U.S. decision makers at companies with 100 to 2,000 employees found that 29% reported at least one cyber incident in the past year where AI was believed to have been used.
Security context
The important distinction is autonomy. A chatbot used to draft phishing copy is one risk; an agent that can plan, browse, call tools, adapt to obstacles, and repeat actions is a different monitoring problem. That makes identity controls, tool-call logs, endpoint telemetry, and data-access anomaly detection more important than content moderation alone.
For practitioners
Treat agentic AI misuse as a workflow-detection problem. Defenders should look for chained actions, unusual token or API use, credential reuse, unexpected data movement, and behavior that spans systems over time. Risk teams should also avoid overclaiming: the report is a risk analysis and survey, not proof that every observed incident was fully autonomous.
What to watch
The useful follow-up signals are incident reports with clear agentic workflows, insurance-loss data that separates AI-assisted from non-AI attacks, and controls that can attribute high-risk tool use without blocking legitimate internal automation.
Key Points #
- 1Agentic AI changes security monitoring from generated-content review to workflow detection across tools, identities, and data access.
- 2QBE's 400-respondent survey gives a directional risk signal, but incident attribution should still be treated cautiously.
- 3Practitioners should prioritize telemetry for chained actions, anomalous credentials, API activity, and sensitive data movement.
Scoring Rationale #
This is a notable AI-security risk story because it links agentic workflows to commercial espionage and fraud, with survey data and insurer analysis that matter to enterprise controls. It is not higher because the evidence is primarily a risk report and survey rather than a newly disclosed technical exploit or large confirmed incident.
Sources #
Public references used for this report. Practice interview problems based on real data
1,625 SQL & Python problems across 15 industry datasets — the exact type of data you work with.