Fraud and financial crime

Telecom fraud detection: SIM swap, SIM box, IRSF and subscription fraud

Telecom operators detect fraud by analysing call detail records, signalling, top-ups and customer data in near real time. The main use cases are SIM box and interconnect bypass, international revenue share fraud (IRSF), Wangiri callbacks, SIM swap and account takeover, subscription and identity fraud, and mobile money fraud. A lakehouse keeps the huge event volumes in one place, and an in-country deployment keeps subscriber data under national law.

Published . Last updated

On this page

What fraud do telecom operators face?

Fraud typeWhat happensMain signal
SIM box and interconnect bypassInternational calls are routed through local SIMs to avoid termination feesMany outgoing calls, few incoming, few cell changes, no data use
International revenue share fraud (IRSF)Traffic is pumped to premium or high-cost numbers that share the revenueSudden calls to rare destinations, often at night or weekends
WangiriOne-ring missed calls trick customers into calling back premium numbersMany short calls from one range to many subscribers
SIM swap and account takeoverA criminal moves the victim’s number to a new SIM to receive bank codesSIM change followed by logins or password resets
Subscription and identity fraudDevices or contracts taken on fake or stolen identitiesApplication data, device financing, first-payment default
Mobile money fraudAgent fraud, mule wallets, social engineeringWallet transfers and agent activity

What data do you need?

  • Call detail records and xDRs: who called whom, when, how long, from which cell.
  • Signalling and network events: SIM changes, IMEI changes, roaming.
  • Billing and top-ups: recharge patterns, payment methods.
  • Customer and retail data: activation channel, documents, dealer.
  • Interconnect and partner data: routes, rates, destinations.

These volumes are large, often billions of records a day. A lakehouse handles this on open tables with Spark, without copying data into a separate fraud appliance.

How does SIM box detection work?

SIM box SIMs behave differently from people. They make many outgoing calls and receive few. They rarely move between cells. They use little or no data or SMS. A model trained on these behaviour features, refreshed daily from CDRs, ranks suspect SIMs for the fraud team to block. Test calls from partners confirm the routes.

How do telcos stop SIM swap fraud?

Score every SIM change for risk: was it requested in a new store, with a new device, soon after a password reset? Hold high-risk swaps for extra checks. Then share a "recent SIM swap" signal with banks, so they can step up authentication. This is one of the most valuable fraud signals an operator can offer.

How does the architecture look on DataNature?

  1. Connect ingests CDRs, signalling and billing feeds.
  2. StreamHouse processes them as streams and keeps rolling counts per SIM, number range and destination.
  3. DataNature AI scores SIMs and destinations, from near real time for IRSF to daily for SIM box.
  4. AI360 Studio sends blocks and alerts to network and billing systems.
  5. Voir agents let fraud analysts ask questions like "which new destinations spiked in the last hour?" in plain language, on governed data.

Why keep telecom fraud data in-country?

CDRs and location data reveal where people are and whom they talk to. Telecom regulators often require them to stay in the country, and some operators cannot use public cloud at all. DataNature runs on-premises or on a national cloud, with the same platform.

How does StreamHouse catch telecom fraud while it happens?

Telecom fraud is measured in minutes of traffic, so the hot path decides the loss:

  • Network and billing events (call detail records, signalling events, top-ups, SIM swaps) stream through StreamHouse into managed Kafka.
  • In-flight detection keyed by subscriber or number: SIM-box patterns (many short outbound calls, few inbound, static location), Wangiri call bursts, sudden roaming spikes, SIM swap followed by high-value activity.
  • Actions within seconds or minutes: flag, throttle or block a number, and open a case for the revenue assurance team.
  • History in the same tables: events land in Iceberg, so the batch path computes subscriber baselines and network-link features, and investigators replay every decision.

Telecom operators often deploy this in their own private cloud or on-premises, which DataNature supports with the same StreamHouse configuration.

How does DataNature Atlas keep this secure and compliant?

Investigators see what they need; analysts see masked identifiers; every score and decision is auditable. DataNature Atlas is the platform's governance module:

  • Knows your data: a catalog with automated PII detection and classification across Bronze, Silver and Gold.
  • Controls access: role-based grants plus attribute-based policies, row filters and column masks (null, redact, partial, hash, year only).
  • Governs AI: Voir agents are scoped principals; masks, row filters and PII guardrails apply to every tool call and answer.
  • Proves it: lineage from source to metric to decision, and an audit log of who or what accessed which data.
  • Stays local: Atlas runs inside your deployment, so policies, lineage and logs never leave your jurisdiction.

These controls support GDPR, PIPEDA, Quebec Law 25, CCPA, HIPAA and sector rules such as OSFI E-23. Read DataNature Atlas in depth or see security and compliance.

See it on your own data.

Book a demo

Demos and quotes are handled by Dlytica, the company behind DataNature.