Leaked username and password lists get tried against your login. Rate limits per IP miss it; counting accounts per visitor does not.
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 credential stuffing 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
- Combo lists. Millions of leaked pairs, tried in bulk.
- IP rotation. A new proxy for every attempt.
- Low and slow. Few tries per account, many accounts.
What to look at
| Field | Why it matters here |
|---|---|
velocity | Distinct accounts and IPs per visitor. |
tlsMismatch | An HTTP client pretending to be a browser. |
bot | Automated login forms. |
- 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: 'credential-stuffing' } }); - 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 } = await trace.verify(eventId); if (signals.bot.detected || signals.tlsMismatch.detected) return block(); if (signals.velocity.detected) return captchaBeforePassword(); return checkPassword();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
Login attempts from one visitor, illustrative:
| Account | IP | Decision | Why |
|---|---|---|---|
| user_1182 | 81.4.x.x | Allow | First attempt |
| user_2093 | 102.33.x.x | Verify | New account, new IP |
| user_7731 | 45.12.x.x | Block | velocity: linkedIdsPerVisitor24h |
| user_0420 | 188.2.x.x | Block | velocity + tlsMismatch |
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.