Skip to content
AI Infrastructure
AI Infrastructure11 min read0 views

Premium-Rate Number Scams and AI-Call Defenses in 2026: Beating Wangiri and IRSF

IRSF cost telecoms $6.69B last year. Wangiri call-back scams target AI voice deployments by rinsing minutes through premium-rate destinations. Here is the AI-driven defense pattern that catches both before billing close.

International Revenue Share Fraud cost telecoms $6.69 billion in 2024 alone, and the new attack vector in 2026 is AI voice itself - attackers compromise a SIP trunk, place automated calls to premium-rate destinations they control, and walk away with revenue share before the customer notices. Wangiri (one-ring scams that bait callbacks) and IRSF together are the dominant outbound voice fraud pattern. The defense is real-time anomaly detection plus geo-blocked egress.

Background

IRSF works by exploiting the legitimate revenue-share business model that international premium-rate operators use to pay content providers. Fraudsters lease premium-rate ranges, then compromise a customer's PBX, SIP trunk, or VoIP credentials and pump traffic to those ranges. The originating carrier collects from the customer and pays termination fees to the destination network; the destination network shares revenue with the fraudster. By the time the customer sees the bill, the fraudster has cashed out.

Wangiri ("one ring" in Japanese) is the consumer flip side: scammers place a single-ring call to millions of phones, and a fraction of recipients call back, hitting the same premium-rate range. Both flows exploit the same revenue-share infrastructure. AI voice deployments are particularly exposed because they often place high volumes of outbound calls to many destinations and an attacker who hijacks credentials can blend in.

The 2026 defense pattern has three layers. First, geo-blocking at the trunk: deny outbound to countries the business never calls. Second, real-time anomaly detection: ML models that flag call patterns deviating from baseline. Third, IPRN range monitoring: subscribe to a fraud intelligence feed (Neural Technologies, BICS, iBASIS) that publishes known premium-rate ranges.

Hear it before you finish reading

Talk to a live CallSphere AI voice agent in your browser — 60 seconds, no signup.

Try Live Demo →

Architecture

flowchart TD
    A[AI Agent places outbound] --> B[Egress Policy Engine]
    B --> C{Destination country allowed?}
    C -->|No| D[Reject + alert]
    C -->|Yes| E{Destination in IPRN feed?}
    E -->|Yes| D
    E -->|No| F[Anomaly check]
    F --> G{Pattern deviates from baseline?}
    G -->|Yes| H[Throttle + alert]
    G -->|No| I[Place call via SIP trunk]
    I --> J[Log to fraud telemetry]
    J --> K[ML model retrain weekly]

The IPRN feed is the highest-leverage piece: most fraud destinations are known. Subscribing costs a few hundred dollars a month and prevents most damage.

CallSphere implementation

CallSphere runs egress policy on every outbound call across our six verticals. The default policy on Healthcare AI, Real Estate AI, Sales Calling AI, Salon AI, IT Helpdesk AI, and After-Hours AI is US and Canada only; international expansion requires explicit per-tenant unlock with a fraud risk attestation. We integrate the BICS IPRN feed for known premium-rate ranges and our fraud detection ML model (one of 90+ tools) runs against the call telemetry pipeline in real time. Anomaly thresholds default to 3 standard deviations above tenant baseline; alerts go to both the tenant's admin console and our SOC. Our 115+ DB tables include a fraud_events table with full audit trail. HIPAA + SOC 2 controls cover the fraud telemetry. Scale ($1499/mo) tenants get 24/7 SOC review of high-severity alerts. The 22% affiliate program credits Scale upgrades driven by international expansion.

Build steps

  1. Default-deny outbound to every country the business does not actually call; whitelist only what is needed.
  2. Subscribe to an IPRN intelligence feed (BICS, iBASIS, Neural Technologies); update daily.
  3. Build a baseline of normal outbound patterns per tenant per hour: destinations, durations, volumes.
  4. Train an anomaly detection model on the baseline; retrain weekly.
  5. Wire alerts to a SOC channel and the tenant admin console; hard-block on critical signals (10x volume to a new destination).
  6. Audit egress logs daily for the first 30 days of any new deployment.
  7. Rotate SIP credentials after every personnel change; require MFA on all VoIP admin access.
  8. Test quarterly: simulate an IRSF attempt to validate detection latency.

FAQ

How much does IRSF cost on average? Industry data shows median compromise costs $20k to $50k per incident, with high-end attacks running over $1M. The compromise window is often hours, not days.

Can AI voice deployments be the attack vector? Yes. An attacker who compromises an AI voice tenant's SIP credentials can pump calls to premium-rate destinations. Egress policy and rapid anomaly detection are the only real defenses.

Still reading? Stop comparing — try CallSphere live.

CallSphere ships complete AI voice agents per industry — 14 tools for healthcare, 10 agents for real estate, 4 specialists for salons. See how it actually handles a call before you book a demo.

Are STIR/SHAKEN signed calls safe from IRSF? STIR/SHAKEN authenticates the calling number, not the called number. It does not prevent fraud where the attacker is calling premium-rate destinations from compromised legitimate accounts.

What is Wangiri exactly? Single-ring calls that hang up before answer. Recipients see a missed call from an international number and call back; the callback hits a premium-rate range and rings up charges. AI voice is mostly an outbound risk vector for IRSF, not Wangiri specifically, but the same destinations are involved.

Does CallSphere reimburse fraud losses? Pass-through Twilio billing applies. Our SOC monitoring on Scale plans typically catches attacks within minutes. We do not contractually reimburse but routinely partner with Twilio's fraud team to dispute unauthorized charges.

Sources

Start a 14-day trial with managed fraud defense, browse pricing for Scale plans, or book a demo. Partners earn 22% via the affiliate program; enterprise fraud questions go to contact.

Share

Try CallSphere AI Voice Agents

See how AI voice agents work for your industry. Live demo available -- no signup required.

Related Articles You May Like

AI Voice Agents

MOS Call Quality Scoring for AI Voice Operations in 2026: Beyond 4.2

MOS 4.3+ is the band where AI voice feels human. Drop below 3.6 and conversations break. Here is how to measure, improve, and alert on MOS in production AI voice using G.711, Opus, and the underlying packet loss / jitter / latency math.

AI Engineering

SIP Debugging with sngrep and Wireshark for AI Voice Calls in 2026: The Hands-On Playbook

When your AI voice agent gets one-way audio, missed DTMF, or codec mismatch, sngrep and Wireshark are still the fastest path to root cause in 2026. Here is the playbook.

AI Strategy

State Data Residency for AI Voice in Healthcare — Texas, Nevada, Colorado in 2026

Texas SB 1188 requires US-resident EHRs from January 1, 2026; Nevada's consumer-health-data law constrains health data; Colorado AI Act takes effect June 30, 2026. AI voice agents must architect for state-by-state data localization.

AI Infrastructure

RTP Transcoding Cost for AI Voice in 2026: Why Edge Placement Beats Central GPU

Transcoding RTP to WebSocket is more CPU-intensive than people expect. For AI voice in 2026, where you place the transcode (edge near the carrier vs central near the model) decides your cost-per-minute.

AI Infrastructure

VoIP Fraud Detection for AI Voice Deployments in 2026: Patterns, Tooling, Playbooks

VoIP-related security incidents jumped 47% since 2024 and AI deployments are the new soft target. Here is the production fraud detection stack: rate limiting, anomaly ML, IPRN intel, and SOC playbook for AI voice.

AI Infrastructure

Kamailio Dispatcher for AI Voice Scaling in 2026: Round-Robin Is Not Enough

Kamailio 6.0's dispatcher module is how you horizontally scale AI voice bridges behind a SIP front-end. Round-robin is the easy answer; call-load and weight-based dispatching is the right one.