By NHI Mgmt Group Editorial TeamBased on AU10TIX: “Top Fraud Trends for 2025-2026” (July 16, 2025)

TL;DR: Fraud operations now resemble SaaS businesses, with modular kits, on-demand botnets, and AI-enhanced social engineering compressing the time from compromise to extraction by 30% in 2024, according to AU10TIX. Static verification and batch controls are no longer enough when attackers can scale, adapt, and monetise within minutes.


At a glance

What this is: This guide explains how fraud moved from manual scams to industrialised, AI-assisted operations and highlights the controls needed to keep pace with faster compromise and extraction.

Why it matters: It matters because identity, fraud, and IAM teams now face attacks that adapt in real time, which means static verification, batch review, and one-time onboarding checks leave too much room for abuse.

By the numbers:

  • 2024 saw a 30% reduction in dwell time between account compromise and monetary extraction.

Context

Fraud is no longer best understood as a one-off scam or a single bad login. The article describes a shift toward industrialised fraud operations that blend automation, social engineering, and subscription-style tooling, which puts pressure on identity programmes to respond in real time rather than after the fact.

For IAM and fraud practitioners, the governance gap is clear: controls built around static verification, delayed review, and batch decisioning do not fit an environment where attackers can probe, adapt, and monetise within minutes. The operational question is no longer whether fraud exists, but whether identity controls can keep pace with it.


Key questions

Q: What breaks when customer verification still relies on static KYC checks?

A: Static KYC checks break down when identity data is stale, publicly exposed, or easy to replay. They create a false sense of assurance because the business treats one early check as durable proof. In practice, that leaves fraud teams, IAM teams, and compliance teams with a control that is strong only on paper.

Q: Why does AI-driven fraud increase risk for phishing, account takeover, and payment abuse?

A: AI lowers the effort needed to create believable messages, fake identities, and mass campaigns, so attackers can target more people with less skill. That raises the success rate of phishing and follow-on account takeover because victims are more likely to trust the content. The result is faster fraud scaling, more losses, and greater pressure on detection teams.

Q: How can security and fraud teams tell whether their controls are failing?

A: Look for two signals at once: rising false positives that push real customers away and rising fraud leakage that appears only after chargeback analysis. If both are increasing, the decision layer is probably too slow, too binary, or too detached from session context.

Q: How do IAM and fraud teams work better together on identity proofing?

A: They need shared policy for evidence quality, risk scoring and escalation. IAM controls decide what access is granted, while fraud controls surface suspicious patterns before or after issuance. When those teams operate separately, weak proofing can look compliant even while fraud risk is increasing.


Technical breakdown

Fraud-as-a-service changes the attacker operating model

Fraud-as-a-service turns crime into a modular delivery model. Instead of building every capability from scratch, operators subscribe to phishing kits, deepfake tooling, credential-stuffing services, and laundering infrastructure, then coordinate them through a commercial-style ecosystem. That lowers the skill threshold and increases campaign velocity. For defenders, the key shift is that the same campaign logic can be reused across many targets with minimal friction, so isolated controls miss the broader abuse pattern. Identity systems must assume repeatable, distributed abuse rather than a single malicious actor acting alone.

Practical implication: detection and fraud governance must look for reusable attack patterns across channels, not just single-event anomalies.

AI-driven social engineering compresses verification windows

AI-written phishing and deepfake calls increase the credibility of impersonation by matching tone, context, and timing more closely than traditional scams. The article ties this to higher click-through rates and faster conversion from engagement to compromise. That matters because many identity workflows still assume a human reviewer has enough time to notice drift, challenge an applicant, or escalate a suspicious case. When the attacker can imitate familiar behaviour on demand, trust signals become easier to spoof and slower human decision loops become a liability.

Practical implication: move high-risk identity decisions closer to the moment of interaction and add stronger liveness and behavioural checks.

Real-time fraud monitoring is now an identity control, not just an analytics layer

The article describes AI/ML fraud detection as a system that ingests device, behavioural, network, and transactional signals to generate live risk scores. That is more than analytics. It is a control plane for deciding whether to step up authentication, quarantine a transaction, or block a session. Adaptive profiling and continuous retraining matter because fraud patterns shift faster than static rules can be updated. In practice, this makes the fraud stack part of IAM and KYC governance, not a separate back-office function.

Practical implication: integrate risk scoring with authentication and transaction controls so the response happens before loss materialises.


Threat narrative

Attacker objective: The objective is to monetise compromised identity trust as quickly as possible by turning access into payments, account abuse, or laundered proceeds.

  1. Entry begins with AI-written phishing, deepfake impersonation, or other social engineering that creates a believable first contact and gains trust.
  2. Credential access follows through credential stuffing, synthetic identity creation, or harvested logins that give attackers valid footholds into accounts.
  3. Escalation occurs as the same fraud operation pivots quickly through additional targets, payment rails, or laundering channels before defenders can intervene.
  4. Impact is monetary extraction at scale, with the article noting that attackers can move from compromise to extraction much faster than legacy controls can detect.
  • CoPhish OAuth phishing via Copilot Studio: Datadog showed Copilot Studio agents on a Microsoft domain can front OAuth consent phishing and forward stolen tokens; no victims reported.
  • Twilio 0ktapus breach 2022: SMS phishing of employees exposed 209 Twilio customers and 1,900 Signal users, part of the 0ktapus campaign against 130+ firms.

Read and download The State of NHI & AI Agent Breach Report 2026, covering 200+ breaches impacting Non-Human Identities including AI Agents.


NHI Mgmt Group analysis

Fraud has become an identity governance problem, not just a fraud detection problem. The article shows that attackers now combine AI-assisted impersonation, credential abuse, and automation into repeatable identity abuse chains. That moves fraud out of a narrow operations lane and into IAM, KYC, and risk governance. The practitioner conclusion is that identity assurance must be treated as a live control surface, not a one-time checkpoint.

Static verification is structurally mismatched to industrialised fraud. The article’s core pattern is not merely more attacks, but faster attacker iteration and monetisation. Controls that rely on delayed review, batch scoring, or single-step proofing assume the attacker stays visible long enough to be reviewed. The implication is that identity programmes built on episodic trust decisions are already behind the threat model.

Identity trust debt is the new fraud exposure. Deepfakes, synthetic identities, and outsourced credential testing all exploit the gap between initial trust establishment and later abuse detection. Once that gap widens, organisations accumulate trust debt that fraud rings can cash in at scale. The implication is that governance has to focus on how trust is earned, refreshed, and revoked across the full identity journey.

Real-time risk scoring is becoming a control, not an optimisation. The article describes AI-driven monitoring that blends behavioural, device, and transactional signals to decide whether a session or payment should proceed. That is a governance shift, because the decision point moves from post-event investigation to pre-loss intervention. Practitioners should treat real-time scoring as part of identity enforcement architecture.

Fraud teams and IAM teams are converging on the same problem space. When attackers use the same identity artefacts for onboarding abuse, account takeover, and payment fraud, the control model cannot stay siloed. This is where the strongest programmes will join identity proofing, authentication, and transaction monitoring into one decision loop. The practitioner conclusion is that cross-functional governance now matters more than point solutions.

From our research library:

  • Sophisticated multi-step fraud rose 180%, according to Sumsub's Identity Fraud Report 2025-2026.

What this signals

Identity trust now decays faster than many governance programmes assume. When compromise can turn into monetisation within minutes, the review cycle is no longer the main control. The control point shifts to issuance, proofing, and live decisioning, because that is where abuse can still be interrupted.

Fraud and IAM are converging around the same decision surface. Onboarding, authentication, and payment approval are no longer separate problems when the same actor can spoof identity, test credentials, and cash out in one chain. Practitioners should expect more pressure to unify risk signals across those stages rather than manage them as isolated queues.


For practitioners

  • Strengthen identity proofing with liveness and behavioural checks Add passive liveness, challenge-response testing, and behavioural biometrics to the onboarding path so synthetic or impersonated identities face multiple independent hurdles before approval.
  • Move high-risk decisions to real-time risk scoring Connect device signals, transaction context, and behavioural anomalies to a live scoring engine so the system can step up, pause, or quarantine in the same session.
  • Test fraud controls against deepfake and synthetic-ID scenarios Run exercises that simulate deepfake calls, AI-written phishing, and synthetic identity onboarding to measure whether reviewers and automation can still detect coordinated abuse.
  • Break the link between compromise and extraction Use transaction throttling, escalation thresholds, and manual review triggers for unusual payment or payout paths so compromise does not immediately translate into loss.

Key takeaways

  • AI-assisted fraud now behaves like an industrialised identity abuse market rather than a collection of isolated scams.
  • The article’s scale signal is the shrinking window between compromise and extraction, which leaves less room for batch controls and manual review.
  • Practitioners should treat proofing, authentication, and transaction monitoring as one real-time control loop if they want to interrupt monetisation.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

OWASP Non-Human Identity Top 10, OWASP API Security Top 10 and MITRE ATT&CK address the attack and risk surface, while NIST CSF 2.0 sets the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
OWASP Non-Human Identity Top 10NHI-04 — Insecure AuthenticationAI-assisted impersonation and proofing bypass target authentication trust.
NHI-10 — Human Use of NHIFraud rings abuse identity workflows to impersonate people and reuse trusted channels.
Recommendation — Harden authentication flows against AI-assisted impersonation and step up assurance when signals drift. Separate human trust signals from machine-driven fraud patterns in onboarding and escalation.
OWASP API Security Top 10API2 — Broken AuthenticationCredential stuffing and automated login testing exploit weak auth on digital flows.
Recommendation — Apply API authentication controls where login or token flows are exposed to automation.
NIST CSF 2.0PR.AA-05 — Access Permissions, Entitlements and AuthorizationsIdentity decisions must change when fraud signals indicate elevated risk.
Recommendation — Tie access and transaction authorisation to live risk scoring instead of static approval states.
MITRE ATT&CKTA0006;TA0040 — Credential Access; ImpactThe article describes credential harvesting followed by monetary extraction as the attack outcome.
Recommendation — Map fraud chains to credential access and impact to prioritise detection before cash-out.

Key terms

  • Fraud-As-A-Service: Fraud-as-a-service is the outsourcing of scam operations through rented tools, stolen data, and ready-made attack services. It lowers the skill needed to commit fraud and lets bad actors scale quickly across industries. For defenders, it means attacks are faster, cheaper, and more operationally organized than traditional one-off fraud attempts.
  • Synthetic Identity Document Fraud: Synthetic identity document fraud is the use of fabricated or AI-generated identity documents to impersonate a real or invented person. It targets verification workflows by presenting fake passports, driver’s licences, or IDs that can look credible enough to pass basic checks unless teams use stronger authenticity and anomaly detection controls.
  • Deepfake-based impersonation: A fraud technique that uses synthetic audio, video, or both to make an attacker appear to be a trusted person during a live interaction. The tactic exploits human trust in familiar cues and often aims to trigger urgent actions such as payments, resets, or access changes before verification is challenged.
  • Real-Time Fraud Monitoring: Real-time fraud monitoring is the continuous evaluation of device, behavioural, network, and transaction signals to decide whether an action should proceed. In modern identity programmes, it acts as an enforcement layer because the response must happen before the fraud chain reaches cash-out or account abuse.

Deepen your knowledge

NHI governance, agentic AI identity, and machine identity lifecycle are core topics in our NHI Foundation Level course, the industry's only accredited NHI security programme. If you are responsible for identity security strategy or NHI governance in your organisation, it is worth exploring.
NHIMG Editorial Note
Published by the NHIMG editorial team on July 11, 2026.
Updated on October 11, 2026.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org