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
| Field | Why it matters here |
|---|---|
velocity | Events per visitor, per IP and per account. |
bot | Automated browsers requesting codes. |
highActivity | Hundreds of events from one visitor a day. |
- 1
Identify on the action
Call the browser SDK when the user performs the action, not on page load, and send the
eventIdwith the request. Pass your own user id aslinkedIdwhenever you have one: the account signals count by it.TypeScriptconst { eventId } = await trace.get({ linkedId: user?.id, tags: { action: 'sms-pumping' } }); - 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);try: event = client.get_event(event_id) except trace_device.VerifyError: event = None # fail opentry { $event = $client->getEvent($eventId); } catch (Trace\VerifyError $e) { $event = null; }Map<String, Object> event = null; try { event = trace.getEvent(eventId); } catch (Trace.VerifyException e) { /* fail open */ }const event = await trace.verify(eventId).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
Decide
TypeScriptconst { 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 theeventfrom step 2 instead. The thresholds are yours. Trace scores and explains;event.reasonslists which signals added how much, so log it with every decision.
Example decisions
Code requests from one visitor, illustrative:
| Number | Time | Decision | Why |
|---|---|---|---|
| +20 10 •••• 4412 | 10:00:02 | Allow | First code |
| +20 10 •••• 4412 | 10:01:30 | Allow | Resend |
| +882 •••• 0917 | 10:01:34 | Block | velocity: new numbers, same visitor |
| +882 •••• 0918 | 10:01:35 | Block | bot |
Roll it out
- Ship steps 1 to 3 with logging only: record the decision, block nothing.
- 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.
- Turn on Verify first, then Block for the clearest cases.