Is FUT exeSniper | SBC Solver & Autobuyer safe?
FUT EXE is medium risk.
FUT exeSniper | SBC Solver & Autobuyer runs code returned by futexe.com inside EA's Ultimate Team web app.
When the EA Ultimate Team web app loads, the extension posts stored FUT exe account fields and hardware details to futexe.com/api/sniper/access, caches the returned script, and runs it in the page. Its EA autologin feature also stores the user's EA email, password, and TOTP seed in signin.ea.com localStorage so it can fill and submit the login flow automatically.
Who publishes itFUT ExeSniper - no other listings under this identity, 2 shared hostnames
FUT ExeSniper - no other listings under this identity, 2 shared hostnames
Shared hosts - 2 hostnames
Hostnames hardcoded in this extension that few other listings call. That can mean one operator behind both, and it can equally mean a small shared vendor, so it is context rather than a conclusion. Hosts that many listings call are left out: they are services, not connections.
FUT EXE findings
FUT exe posts hardware details and stored account data to futexe.com
Code analysis shows that with the EA web app open, the extension sends CPU, memory and graphics details plus stored account fields to futexe.com.
This was not observed during dynamic analysis.
What actually happens
You have the EA Ultimate Team web app open in a tab.
The extension gathers hardware details and sends them with your stored account fields to futexe.com.
Fields in the request body
- Hardware detailsbase64 of {cpuInfo, memoryInfo, gpuInfo}
CPU, memory and graphics card details that help recognise your machine.
- Stored emailuser@example.com (illustrative)
The account email held in the extension's storage.
- Stored password(value from user.store)
The password held in the extension's storage.
- Token and serverfa32f / auto
A fixed token string and the selected server name.
The code that does this
Request construction and POST
Info blob and body
const info = btoa(JSON.stringify({ cpuInfo, memoryInfo, gpuInfo }));const body = { ...userData, server: "auto", isPhone, info };POST
fetch(`${apiDomain}/api/sniper/access`, { method: "POST", headers: {"Content-Type": "application/json;charset=utf-8"}, body: JSON.stringify(body) });Stored account fields
const state = JSON.parse(store).state;return { email: state.email, password: state.password, token: "fa32f", server: state.server };Destinations
- futexe.com
Primary API domain receiving the /api/sniper/access POST.
- futexe.ru
Fallback API domain used if the primary health check fails.
Observation
Static analysis finding. This behaviour was identified by reading the shipped extension code and has not yet been reproduced in a live run. The trigger conditions and the exact data sent are read from the code, not from an observed capture.
FUT EXE version history
4.36.16
Mar 4, 2026
4.37.10
Apr 11, 2026
4.48.4
Nov 11, 2026
Where FUT EXE sends data
- futexe.com
Found in its code · only this extension
Chrome Web Store listing
- Versions
- 4.48.4 latest of 3 seen since March 4, 2026
- Store rating
- 4.4 from 39 ratings
- Last updated
- November 11, 2026
- Size
- 208 KiB
- Privacy policy
- futexe.com
