TL;DR: SMS toll fraud is driving hidden losses for social media platforms that rely on SMS verification, with one company saving $3 million per month after blocking malicious bot traffic, according to Arkose Labs. The deeper issue is that verification channels built for trust can be turned into revenue leakage when bot activity scales faster than detection and rate controls.
Editorial analysis by NHI Mgmt Group, based on content published by Arkose Labs: “Social Media and SMS Toll Fraud”.
Key questions
Q: What breaks when SMS verification is left open to bot traffic?
A: The control that breaks is the assumption that verification traffic is naturally self-limiting.
Q: Why do automated SMS verification attacks create outsized financial risk?
A: Because each successful request can produce an immediate charge, and attackers can generate hundreds or thousands of requests in a short burst.
Q: How can security teams tell when SMS verification is being gamed?
A: Look for short bursts of SMS requests, repeated retries, sequential phone numbers, partially completed forms, and requests originating from geographies where the business has little or no user base.
Practitioner guidance
- Audit SMS verification cost exposure Map where SMS is used for registration, login, and step-up verification, then quantify the monthly message cost attached to each flow under bot abuse.
- Add bot signals before SMS delivery Combine velocity checks, sequential-number detection, geography mismatches, and retry suppression so abuse is blocked before the message is sent.
- Restrict SMS to trusted use cases Limit SMS-based 2FA to workflows that genuinely need it and move routine consumer verification to stronger challenge and fraud controls.
Bottom line: SMS verification can become a revenue leak when attackers automate fake registrations and force the business to pay for outbound messages.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
SMS verification is no longer just an authentication channel, it is a cost-bearing control surface. When attackers can trigger messages at scale, the control stops being about proving identity and starts being about controlling exposure to telecom spend. That shifts the governance question from login success rates to abuse economics. Practitioners should treat every outbound verification path as part of the identity cost model, not as a free security primitive.
A few things that frame the scale:
- U.S. fraud losses are projected to reach $40 billion by 2027.
A question worth separating out:
Q: Should organisations keep SMS as a default 2FA method?
A: Only when the use case justifies the fraud exposure and cost. SMS is convenient, but it is easy to automate, expensive at scale, and weak against abuse. Most teams should reserve it for trusted fallback scenarios and use stronger challenge or verification controls for routine journeys.
👉 Read our full editorial: SMS toll fraud is exposing a hidden IAM cost model