Join our Newsletter — 33% off our NHI Course

Did verified KYC accounts become money mules after approval?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20225
Topic starter  

TL;DR: $28 billion tied to illicit activity still moved through crypto accounts that had already cleared KYC, SEON's case work shows, highlighting second-party fraud. Account trust has to be rechecked after approval, or verified identities can be separated from the people using them.

Editorial analysis by NHI Mgmt Group, based on content published by SEON: “The KYC Mule: When Verified Identity Becomes the Product”.

Key questions

Q: Why do verified accounts still become money mule accounts?

A: Verified accounts become mule accounts because legitimacy at enrollment does not prevent later handover.

Q: What are the signs that a verified identity has been handed over?

A: The most common signs are a new device or emulator, a sudden geography change, clustered password or recovery updates, and behavioural patterns that diverge from the account's earlier history.

Q: What breaks when KYC clears the wrong risk?

A: KYC breaks when it is treated as proof of ongoing account legitimacy rather than proof that a real person existed at onboarding.

Practitioner guidance

  • Define second-party fraud as a separate control class Create an explicit taxonomy for verified identities that later become rented, coerced, or delegated accounts so analysts do not force every case into first-party or third-party fraud.
  • Monitor post-onboarding operator drift Correlate login device changes, geography shifts, recovery event bursts, and behavioural drift after approval because those are the earliest signs that a verified account changed hands.
  • Separate proofing evidence from ongoing legitimacy evidence Keep the onboarding artefacts that proved a person was real distinct from the runtime signals that show whether the current operator still matches the approved risk model.

Bottom line: Second-party fraud fills the gap between genuine onboarding and later account misuse, which is why KYC alone cannot prove who is operating an account.

Glossary terms: Third-Party Fraud, Money mule, Runtime Drift, Continuous Adaptive Trust

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 1 week ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20715
 

Second-party fraud is the failure mode most IAM and fraud programmes still under-model. The industry knows how to detect first-party deception and third-party account takeover, but it often lacks a governance model for a real identity that later becomes a rented or coerced operating surface. That gap matters because the account is not fake, and the operator may not be the verified owner. Practitioners should treat this as a distinct control category, not a variant of generic fraud.

A question worth separating out:

Q: How should fraud teams govern post-KYC account trust?

A: Fraud teams should govern trust as a lifecycle state, not a one-time approval. That means combining onboarding evidence with runtime signals, setting re-verification triggers for material behaviour changes, and coordinating fraud, AML, and identity functions so each sees the same operator-drift risk. The goal is to stop treating a verified account as permanently trustworthy.

👉 Read our full editorial: Second-party fraud exposes the gap between KYC and account use


This post was modified 1 week ago by NHI Mgmt Group

   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.