How to Fix a Replay Attack That Repeats a Captured Action Packet

An attacker captures a legitimate action packet (claim reward, perform trade) and resends it, and your server happily processes the duplicate because nothing marks it as already handled. Add per-message uniqueness so a resent packet is recognized and dropped.

How to fix it

1. Add a nonce or sequence number

Include a unique nonce or a monotonically increasing sequence per session in each action message, and reject any value already seen or lower than the last accepted one.

2. Bind messages to the session

Tie the anti-replay window to the authenticated session and rotate it, so packets captured from one session cannot be replayed into another.

3. Make state-changing actions idempotent

Give each action a unique ID and dedupe server-side, so even a replayed packet that slips through produces no second effect.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every HTML5 error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.