Radar / Bet365 MI: GPS simulator accessory bypass, restriction not re-applied on re-entry

Source. May 19, 2026 weekly sync.
Ticket. CIV-48: Test Fake Location using GPS Simulator Accessory on Competitor Apps.

What we tested

A hardware GPS simulator accessory was used to spoof the tester's physical location while connecting to Bet365 Michigan (Radar deployment) from Tennessee.

What happened

• First login attempt — an error was returned (location restriction triggered).
• Second login attempt — succeeded with no further location checks enforced. The tester opened a casino game and placed real-money bets from Tennessee.
• The restriction that appeared on the first login was not re-applied on re-entry — the bypass is repeatable.

Why it matters

This is a structural detection failure, not a one-off bug: the GPS simulator was identified once, then the operator's session state effectively whitelisted the device. Anyone who has triggered a restriction once can simply log out and back in to bypass it.

Combined with the Bet365 NJ Tailscale RDP gap confirmed in the same week, Bet365's Radar integration is producing two distinct, easily-reproducible spoof methods across two different states.

Cross-reference

• GPS simulator at FanDuel WV (Radar) — previously bypassed from Vietnam (March 24, 2026). The GPS-simulator gap is not new and not WV-specific.
• PlayCover at Bet365 MI — blocked the same week. Bet365 catches the iOS-on-Mac vector but misses the hardware-GPS vector.
• GPS simulator at Fanatics TN (OpenBet) — detected with a clear, specific error message. OpenBet handles this vector; Radar does not.

Radar profile → · May 19 weekly sync →