2 posts tagged with "emulator"

Source. June 23, 2026 weekly sync.
Ticket. CIV-64: MI advanced spoofing retest.

What we tested​

A VMOS virtual Android environment against the Fanatics Michigan app (OpenBet Locator).

What happened​

• ✓ Access blocked. A generic error appeared immediately after login with no path to place a bet.
• ⚠️ Error messaging uninformative — no guidance on why access was denied or how to recover.

Why it matters​

OpenBet successfully blocked a device-farm vector that has bypassed other integrations in prior cycles. Contrast with undetected GPS simulator and TeamViewer paths on the same operator in the same month (June 8, CIV-89).

Cross-reference​

• Fanatics MI (OpenBet) — HopToDesk undetected on Android (June 2, CIV-64) — same ticket, opposite outcome on a different vector.

OpenBet profile → · June 23 weekly sync →

Source. June 23, 2026 weekly sync — Competitive Research (Valeria).

What's new​

Radar released a new Web version 5.0.0 and 5.1.0 with a structural change to how fraud signals are delivered:

• Fraud detection moved to a separate, easy-to-use JS module — clients can now opt in and opt out of individual fraud signals rather than taking an all-or-nothing bundle.
• New signal classes called out: emulator detection, screen sharing detection, and an IP check hardcoded to every 30 seconds.

Why it matters​

The modular JS architecture makes it easier for operators to toggle fraud checks — which cuts both ways: faster iteration for Radar, but also a configuration surface where gaming integrations might ship with screen-sharing or emulator checks disabled unless we validate each deployment.

The 30-second IP polling is a concrete cadence we can test against — especially relevant given undetected iOS screen-sharing gaps on Radar deployments this same cycle (Wind Creek PA, CIV-91).

Watch point​

Confirm whether any live gaming integrations have upgraded to Web 5.x and which fraud modules are enabled by default vs opt-in.

Radar profile → · June 23 weekly sync →