Fake reviews and votes

One person, one vote, one review.

10 minutes

Reviews, polls, likes and surveys are only useful if each one comes from a different person. Group them by device.

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 fake reviews and votes 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

  • Sock puppets. Many accounts praising one product.
  • Poll stuffing. Voting again in a private window.
  • Survey farms. One device collecting many survey rewards.

What to look at

FieldWhy it matters here
deviceIdOne vote per device, across accounts. Shared by every browser on one device. Store it with the account or the action.
multiAccountFlags the device behind many accounts.
  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: 'fake-engagement' } });
  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 { deviceId } = await trace.verify(eventId);
    
    if (await db.votes.exists({ pollId, deviceId })) return alreadyVoted();
    await db.votes.insert({ pollId, deviceId, choice });

    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

Votes on one poll, illustrative:

AccountDeviceDecisionWhy
@linaDevice AAllowCounted
@omarDevice BAllowCounted
@lina_2Device ABlockAlready voted from this device
anonymousDevice A, privateBlockSame visitorId

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.