SMS pumping

Stop bots draining your OTP budget.

10 minutes

SMS pumping triggers thousands of verification texts to premium numbers. Check the device before you pay for the message.

What you will build: a check on the action you protect that allows normal users, asks doubtful ones to verify, and blocks the clear cases. See the sms pumping overview for the attack in pictures.

Before you start

Finish one Web quickstart (for example JavaScript or React) and one Server quickstart (for example Node.js). The decision code below is TypeScript; every server SDK returns the same event.

How the attack works

  • OTP floods. Scripts requesting codes in a loop.
  • Premium numbers. Texts routed to numbers that pay the attacker.
  • Rotating IPs. Per-IP limits never trigger.

What to look at

FieldWhy it matters here
velocityEvents per visitor, per IP and per account.
botAutomated browsers requesting codes.
highActivityHundreds of events from one visitor a day.
  1. 1

    Identify on the action

    Call the browser SDK when the user performs the action, not on page load, and send the eventId with the request. Pass your own user id as linkedId whenever you have one: the account signals count by it.

    TypeScript
    const { eventId } = await trace.get({ linkedId: user?.id, tags: { action: 'sms-pumping' } });
  2. 2

    Verify on your server

    import { verifyEvent } from '@trace-id/sdk-node';
    
    const event = await verifyEvent(eventId, { secretKey: process.env.TRACE_SECRET_KEY!, endpoint, timeoutMs: 1500 }).catch(() => null);

    Events can be verified for 60 minutes. If verification fails, decide whether to fail open or closed; for most of this flow, fail open.

  3. 3

    Decide

    TypeScript
    const { signals, suspectScore } = await trace.verify(eventId);
    
    if (signals.bot.detected || signals.velocity.detected) return tooManyRequests();
    if (suspectScore >= 40) return captchaFirst();
    return sendOtp(phone);

    trace.verify() is the embedded call; with a server SDK, use the event from step 2 instead. The thresholds are yours. Trace scores and explains; event.reasons lists which signals added how much, so log it with every decision.

Example decisions

Code requests from one visitor, illustrative:

NumberTimeDecisionWhy
+20 10 •••• 441210:00:02AllowFirst code
+20 10 •••• 441210:01:30AllowResend
+882 •••• 091710:01:34Blockvelocity: new numbers, same visitor
+882 •••• 091810:01:35Blockbot

Roll it out

  1. Ship steps 1 to 3 with logging only: record the decision, block nothing.
  2. After a week, look at who would have been blocked or asked to verify. Shared computers, offices and privacy tools are the usual false positives.
  3. Turn on Verify first, then Block for the clearest cases.
Suggest an edit

Spotted something wrong or unclear? Tell us on GitHub and we will fix it.