Many accounts, one attacker.

Leaked username and password lists get tried against your login. Rate limits per IP miss it; counting accounts per visitor does not.

SignalsvelocitytlsMismatchbot
scenario
Step 4 of 4velocity + tlsMismatchBlock
Figure 1Login attempts from one visitor. Illustrative data. Hover or focus to pause; pick a step to scrub.

How it plays out

The attack, what the verified event shows, and what your code does about it.

01 · The attack

How it usually goes

  1. Combo listsMillions of leaked pairs, tried in bulk.
  2. IP rotationA new proxy for every attempt.
  3. Low and slowFew tries per account, many accounts.
02 · What Trace sees

Fields on the verified event

  • velocityDistinct accounts and IPs per visitor.
    "velocity": {  "detected": true,  "details": { "exceeded": ["linkedIdsPerVisitor24h", "ipsPerVisitor24h"] }}
  • tlsMismatchAn HTTP client pretending to be a browser.
    "tlsMismatch": {  "detected": true,  "details": { "reasons": ["noAlpn"] }}
  • botAutomated login forms.
    "bot": { "detected": true }
03 · What you do

Decide, with your own thresholds

  • AllowFirst attempt
  • ChallengeNew account, new IP
  • Blockvelocity: linkedIdsPerVisitor24h
Read the guide

Decision lab

Switch signals on and off. The score is a plain sum of weights.

decision lab
Signals

Weights are the defaults in scoring.default.json. The cut-offs at 25 and 60 are examples; your app sets its own.

20suspectScore / 100
AllowLet the action through.
20/ 100
reasons
  • velocity+20

Implementation

One browser call, one server check.

01IdentifyCall the SDK on the action and send the eventId with it.
02VerifyYour server reads the event with a secret key.
03DecideAllow, challenge or block, with your own thresholds.
identify.ts
const trace = createClient({ apiKey: 'pk_...', endpoint: 'https://id.example.com' });

// On the action (signup, login, checkout), then send eventId with the form.
const { eventId } = await trace.get();
Example response, illustrative
{  "eventId": "evt_example"}

Start in shadow mode. Block later.

Log the decision for a week, check who it would have stopped, then turn it on.