All articles Fraud & ATO

IRSF Fraud SMS: Premium-Rate OTP Abuse

Translucent glass phone slab sending a thin blue beam toward a cluster of glowing nodes on a black background

IRSF fraud SMS attacks are a billing problem that looks like a traffic spike. International revenue share fraud pushes messages toward numbers in ranges where the termination fee is shared with whoever controls the range. In a product with an OTP flow, every send-code request is a billing event someone else can trigger. You pay per message, the range operator pays the attacker a share, and the first real signal is an invoice weeks later.

Most teams find it after the fact. Signups looked healthy, the resend endpoint worked as designed, and the provider delivered every message. The abuse hid inside normal usage: a real endpoint, a real verification flow, and a wrong assumption that per-IP rate limiting was enough.

This guide covers how IRSF shows up in signup and login OTP flows, why per-IP limits miss it, and how per-number and per-range caps become allow, step-up and block decisions before a message leaves your server.

How IRSF shows up in your OTP flow

The pattern is boring once you know it. Someone scripts your send-code endpoint, points it at numbers inside a range they benefit from, and asks for a code for each one. Four shapes:

  • Bulk signup. Accounts with plausible emails, one OTP request each, numbers bunched in a narrow prefix.
  • Resend loops on login. Request, wait out the cooldown, request again. The endpoint did its job; the meter ran.
  • Rotation inside a range. Each number is used once, so a per-number cap never trips while the range takes hundreds of sends.
  • Drift across prefixes. The attacker moves to the next range every few hours to stay under whatever you watch.

What they share is speed and narrowness: fast requests, numbers concentrated in one prefix, and no link to the accounts being created.

Why per-IP limits miss it

IRSF traffic arrives from proxies, datacenter ranges, mobile carriers and residential networks, often one request per IP. IP limits either fire on legitimate users behind carrier-grade NAT or never fire at all. The billing unit is the message, so the control belongs on the message: the destination number, the prefix it belongs to, and the account or device asking for it. A cap on how many codes a number can receive is a policy about money; a cap on how many requests an IP made is a policy about HTTP.

Grid of charcoal glass tiles with one tile lit blue, illustrating a single abused number among many

Set caps in units you actually pay for

Four limits cover most of the exposure, and they work together:

  • Per number. A small allowance per number per window. Real users rarely need more than a couple of codes; a third request in a row is usually a step-up, not a block.
  • Per range. Cap by the leading digits of the E.164 number, so twenty fresh numbers in one prefix share a budget. This is the limit that catches rotation.
  • Per network or operator. Some ranges are worth blocking outright.
  • Per device and account. Ties the request to the client asking for it, so a device that has never signed up cannot request codes in volume.

A policy sketch, illustrative only:

sms
  per_number : 3 per 24h
  per_range  : prefix e164[:6], 40 per 1h
  per_device : 5 per 1h
  block      : premium ranges on your list

Prynt Control enforces the sms use case with these caps and returns a decision with a reason code plus a suggested step. Phone numbers and cards are kept only as keyed hashes, so enforcement does not need raw numbers. The endpoint side is covered in our notes on form protection.

Turn the caps into allow, step-up, block

A cap that only blocks is a blunt instrument. Split the decision:

Three concentric translucent rings around a blue node on a dark surface, representing layered per-number and per-range limits

  • Allow normal sends from normal clients.
  • Step-up when a number or range is close to its cap: ask for a captcha or verify the email first, and hold the SMS until that passes.
  • Block when the range is on your list or the device has a history of adverse decisions.

Run it in mirror mode first. Prynt Control’s 14-day mirror period records decisions without blocking anything, so you can compare them against your own send logs and fix thresholds before they touch a real customer. Then enforce in stages: step-up first, block later, and keep the reason codes. Prynt never blocks by itself: your code receives the decision and decides what to do with it.

Review the decisions, not just the blocks

Log the use case, the decision, the reason code and the request ID on every OTP request. Watch three things weekly: send volume per range, the share of step-ups that pass, and accounts that hit a cap and then convert. A range with volume and no conversions is either abuse or a broken flow. For coordinated patterns across accounts, the signals described in fraud rings help connect requests that look unrelated in isolation. Setup details live in the docs.

FAQ

Three floating glass panels on black, one open, one behind a thin barrier and one closed, representing allow, step-up and block decisions

Does this replace my SMS provider’s fraud controls?

No. Your provider sees the message and the destination; you see the account, device and product context behind the request. Keep provider alerts and enforce caps on your endpoint, before the request reaches the provider.

Will per-number caps lock out real users?

Not if caps lead to step-up instead of block. A user who retries once passes a captcha or email check and gets the code. Only ranges on your block list, or devices with repeated adverse decisions, get a hard block.

Do I need raw phone numbers to enforce caps?

No. Prynt Control keeps phone numbers and cards only as keyed hashes, which is enough to count sends per number and per range without holding the raw value.

Where to start

Set the four caps, run the mirror period, and compare decisions with your send logs before you enforce anything. Prynt Control answers the sms use case on your server with allow, step-up or block plus a reason; you keep the final call. Start at pryntid.com and keep the first rollout to step-ups.

Try it free

Prynt is device intelligence with a free plan: 5,000 identifications a month, visitor IDs with confidence and bot detection — no credit card. Upgrade to Pro for VPN, proxy, tampering and behavioral signals.

Keep reading