By NHI Mgmt Group Editorial TeamBased on Chainalysis: “Record $17 Billion Estimated Stolen in Crypto Scams and Fraud in 2025 as Impersonation Tactics and AI Enablement Surge” (January 13, 2026)

TL;DR: Crypto scams and fraud stole an estimated $17 billion in 2025, with impersonation scams growing 1400% year over year and AI-enabled scams proving 4.5 times more profitable than traditional scams, according to Chainalysis. The pattern is no longer isolated fraud but industrialized criminal infrastructure that security, fraud, IAM, and identity verification teams must treat as a governance problem, not a user-awareness problem.


At a glance

What this is: Chainalysis says crypto scams and fraud reached an estimated $17 billion in 2025, driven by 1400% growth in impersonation scams and a broader industrialisation of AI-enabled fraud.

Why it matters: Identity, fraud, and IAM teams need to treat impersonation, account takeover, and synthetic trust signals as governance failures because the attack surface now spans human trust, digital identity, and payment rails.

By the numbers:

  • Chainalysis estimates $17 billion was stolen in crypto scams and fraud in 2025.
  • Impersonation scams grew 1400% year over year in 2025.
  • The average scam payment increased from $782 in 2024 to $2,764 in 2025.

Context

Crypto scams now operate as a scalable fraud supply chain rather than isolated social engineering events. The article shows how impersonation, phishing-as-a-service, AI-generated deepfakes, and professional laundering services combine to increase conversion rates and payment sizes across scams.

The identity security lesson is that trust signals can be manufactured at industrial scale. That creates direct pressure on identity verification, fraud operations, customer support authentication, and account recovery controls, especially where humans are asked to make security decisions under urgency.


Key questions

Q: What control fails first when crypto scams use impersonation and deepfakes?

A: The first failure is usually trust verification, not authentication technology. When victims are persuaded to treat a message, call, or website as legitimate, attackers bypass formal controls by converting the user into the approval mechanism. Organisations need stronger step-up checks at transfer, recovery, and support moments, where impersonation produces the highest financial impact.

Q: Why do AI-enabled scams become more profitable than traditional fraud?

A: AI improves scam economics by making messages more convincing, enabling better personalisation, and letting operators run more conversations at once. That increases conversion rates and average payment sizes, so the same criminal infrastructure produces more revenue. The practical response is to move detection toward behavioural, device, and workflow signals that are harder to synthesise.

Q: What signs show a fraud operation is becoming industrialised?

A: Look for reusable domains, phishing kits, scripted support flows, repeated wallet patterns, and laundering through the same service providers or DeFi paths. Those signals show the scam has become a modular service chain rather than a one-off attack. At that point, individual takedowns matter less than disrupting the infrastructure that keeps the campaign running.

Q: How should teams govern customer support when impersonation risk is high?

A: Support should never be allowed to override identity verification just because a request sounds urgent or emotionally plausible. High-risk requests need independent challenge steps, audit trails, and separation between assistance and account or payment changes. That reduces the chance that a convincing impersonator can turn support into an attack path.


Technical breakdown

Why impersonation scams scale so quickly

Impersonation scams work because they borrow legitimacy from trusted brands, institutions, and support channels. In practice, the attacker does not need to break the target’s authentication stack if they can convince the target to act as the authenticator by approving a transfer, sharing a code, or moving funds to a false wallet. AI-generated voice, image, and text content reduces the cost of producing convincing pretexts, while phishing-as-a-service lowers the skill floor for repeatable campaigns. The result is not just more fraud, but fraud that can be tuned and replayed across geographies and victim segments with very little marginal effort.

Practical implication: Treat impersonation as an identity and workflow control problem, not a training problem.

How scam infrastructure becomes a service layer

The article describes phishing kits, template libraries, hosting, messaging, laundering, and resale as separable services that criminal operators buy and reuse. That modularity matters because it makes the attack chain resilient: if one domain is blocked or one channel burns out, the operator can swap in another component without rebuilding the entire operation. This is the same economic pattern that makes crime-as-a-service hard to disrupt. For defenders, the important insight is that the scam is not a single event but an operating model with vendors, payment rails, and support functions.

Practical implication: Hunt the supporting infrastructure, not just the final fraudulent message.

Why AI changes the economics of fraud

AI changes fraud by improving both persuasion and throughput. Deepfakes, synthetic text, and automated outreach make it easier to personalize scams, increase believable follow-up, and manage larger volumes of conversations simultaneously. That raises conversion rates and average payment values, which is why the article links AI-enabled scams to materially higher profitability. The governance issue is that existing controls often assume fraud attempts are noisy, manual, and easy to distinguish from legitimate interactions. AI erodes that assumption by making fraudulent interactions more fluent, context-aware, and operationally consistent.

Practical implication: Move fraud detection toward behavioral and device-level signals that are harder to synthesise at scale.


Threat narrative

Attacker objective: Extract funds from victims while preserving operational anonymity through layered laundering and reusable fraud infrastructure.

  1. Entry begins with impersonation through SMS phishing, fake support outreach, deepfake-assisted contact, or fraudulent websites that mimic trusted organisations.
  2. Credential or trust capture follows when the victim supplies sensitive information, approves a transfer, or moves assets into attacker-controlled wallets.
  3. Escalation happens as the scam operation routes funds through laundering services, DeFi layers, or mule networks to obscure attribution and cash out.
  4. Impact is the loss of funds at scale, often amplified by repeatable infrastructure that can be reused across many victims and jurisdictions.
  • 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.
  • Mailchimp breach 2022: Attackers socially engineered Mailchimp staff, used a support tool to export 102 customer lists and exposed customer API keys for phishing.

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

AI-enabled fraud is now a governance problem, not a campaign problem. The article shows that scams are increasingly industrialised across content generation, impersonation, hosting, and laundering. That means the control objective is no longer simply blocking bad messages, but governing how trust is issued, authenticated, and recovered across customer-facing journeys. For identity teams, the practitioner conclusion is that fraud controls must sit inside the identity lifecycle, not beside it.

Impersonation is becoming the dominant trust-breaker in digital finance. The 1400% growth in impersonation scams is a clear signal that attackers are exploiting the gap between recognised identity and verified identity. Support calls, urgent account warnings, and brand mimicry all exploit the same weakness: humans still anchor decisions on familiar names and visual cues. The field needs stronger step-up verification, out-of-band confirmation, and account recovery controls that do not rely on conversational trust alone.

Trust signal laundering is the new fraud primitive. Criminal operators are not only laundering money, they are laundering legitimacy through reusable infrastructure, synthetic identities, and platform lookalikes. Once that legitimacy is manufactured, traditional awareness controls become too late in the chain. Practitioners should treat any process that lets a claimed identity trigger value transfer as a high-risk control point.

Identity verification and fraud prevention are converging in the same control plane. This report makes that convergence unavoidable for fintech, exchanges, and any consumer platform that handles high-value transfers. The boundary between account security and financial crime detection is collapsing, especially where AI can generate convincing social proof at low cost. The practitioner conclusion is to align IAM, fraud, and customer support controls around shared trust decisions, not separate teams and separate telemetry.

Law enforcement disruption is improving, but it does not substitute for preventative controls. Record seizures and cross-border takedowns matter, yet the article also shows how quickly scam operators adapt, relocate, and repackage their services. That means defensive strategy has to assume persistence in the criminal ecosystem. The practitioner implication is to build detection and response around the fraud lifecycle, not around one-off takedown events.

What this signals

Trust signal laundering: fraud crews are now manufacturing legitimacy through recycled infrastructure, fake support journeys, and synthetic media. The control problem is no longer simply spotting bad content, but identifying where a claimed identity is being allowed to move money or reset account state.

Identity teams should expect fraud and IAM to converge around the same decision points, especially in recovery, beneficiary change, and support escalation workflows. When those pathways are weak, impersonation becomes a reliable path from conversation to loss.

The industrialisation of scams means security programmes need shared telemetry across fraud, identity, and customer operations. Isolated controls miss the pattern; only correlated trust events expose the campaign.


For practitioners

  • Tighten identity proofing at high-risk moments Require stronger verification when users request wallet changes, account recovery, support escalation, or transaction approvals.
  • Add out-of-band confirmation for financial changes Use a second trusted channel for any transfer, beneficiary, or security-setting change that could be triggered by impersonation.
  • Instrument support channels for impersonation abuse Log and correlate support interactions, callback requests, and password-reset flows to spot coordinated fraud patterns.
  • Expand fraud detection to infrastructure signals Track domains, SMS patterns, wallet reuse, and laundering endpoints so campaigns can be disrupted before cash-out.
  • Align IAM and fraud operations on shared trust events Create a common review path for account takeover, recovery, and payment-risk events so support cannot override security controls without oversight.

Key takeaways

  • AI-enabled crypto scams have moved beyond opportunistic fraud into a repeatable industrial model that combines impersonation, phishing, laundering, and synthetic media.
  • The article’s data points to a major scale problem, with $17 billion estimated stolen in 2025 and impersonation scams growing 1400% year over year.
  • The strongest defensive response is to govern trust decisions at the point of recovery, support, and transfer, where impersonation can most easily convert into loss.

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 SP 800-63 and NIST CSF 2.0 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
OWASP Non-Human Identity Top 10NHI-10 — Human Use of NHISupport agents and impersonation flows exploit human trust in identity-mediated actions.
Recommendation — Restrict human-triggered changes to NHI-linked workflows and require stronger verification before approval.
OWASP API Security Top 10API2 — Broken AuthenticationFraud operations abuse weak authentication and recovery paths around customer accounts and support.
Recommendation — Harden authentication and recovery flows so impersonation cannot bypass account controls.
NIST SP 800-63SP 800-63B — AuthenticationThe article centres on trust in authentication moments during support and recovery.
Recommendation — Apply SP 800-63B assurance principles to step-up verification at high-risk account events.
NIST CSF 2.0PR.AA-05 — Access Permissions, Entitlements and AuthorizationsFraud succeeds when unauthorised parties can trigger sensitive account or payment actions.
Recommendation — Review authorisation for recovery and payment-change actions under PR.AA-05.
MITRE ATT&CKTA0006;TA0010 — Credential Access; ExfiltrationImpersonation, phishing, and laundering map to credential capture and downstream theft.
Recommendation — Map impersonation and phishing patterns to TA0006 and TA0010 to improve detection and tracing.

Key terms

  • Impersonation And Deception Scam: An impersonation and deception scam is a fraud pattern where the attacker pretends to represent a legitimate organisation to gain trust. The method can use phone, text, or email, and it often relies on urgency, authority, and believable context to extract money, credentials, or sensitive personal information.
  • Phishing-as-a-service: A criminal service model that packages phishing infrastructure, templates, delivery tools, and sometimes evasion features for reuse by multiple attackers. It lowers the skill threshold for advanced campaigns and makes targeted identity abuse more repeatable across victims and sectors.
  • Trust Signal Abuse: The manipulation of metrics or indicators that users or systems treat as evidence of legitimacy, such as rankings, scores, or download counts. In agentic environments, trust signal abuse can steer automated selection toward unsafe tools even when the package content itself has not yet been inspected.
  • Fraud lifecycle: The fraud lifecycle is the sequence of stages an attacker or abusive user moves through, from identity or account creation to access, transaction activity, and investigation. Teams use the lifecycle to connect signals across functions instead of treating each alert as an isolated event.

Deepen your knowledge

NHI Mgmt Group covers identity security, NHI governance, and agentic AI through independent research, practitioner guides, and the NHI Foundation Level course. It is suitable for teams that need to connect identity governance, secrets management, and AI-era trust decisions to practical security operations.
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