VPN and proxy detection

Know when the location is not where the user is.

10 minutes

Compare the device clock with the IP country, and check Tor exits, hosting ranges and your own blocklists.

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 vpn and proxy detection 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

  • Region hopping. Prices, content or offers from another country.
  • Hidden origin. Fraud from high-risk regions through a VPN.
  • Tor. Anonymous traffic on sensitive flows.

What to look at

FieldWhy it matters here
vpnDevice offset that no zone of the IP country has.
torRequest IP in your Tor exit list.
datacenterIpHosting and cloud ranges most VPNs exit from.
  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.

    TypeScript
    const { eventId } = await trace.get({ tags: { action: 'vpn-detection' } });
  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, ip } = await trace.verify(eventId);
    
    if (signals.tor.detected) return block();
    if (signals.vpn.detected) return priceFor(defaultRegion);
    return priceFor(ip.country);

    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

Visitors to a regional offer, illustrative:

IP countryDevice clockDecisionWhy
EgyptUTC+2AllowConsistent
GermanyUTC+1AllowConsistent
United StatesUTC+2Verifyvpn: timezone mismatch
Tor exitUTCBlocktor

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.