ShuMei device fingerprint (boxId) | login field shumeiBoxId | None identified, live-tested (see Live validation against production):
empty/synthetic values are accepted without issue for a brand-new guest account; reconnecting into an
established account initially looked ShuMei-gated but turned out to be an unrelated
packageName/platform/appVersion identity mismatch against the access
token. Once that was fixed, reconnect worked, and it kept working against the shipped code after a later
security fix replaced part of the request with placeholders (August 2026; since the 1.0.370 follow-up the iOS ta fills lw_device_id/lw_airKey from the Login and lw_shumei_id from the cached shumeiId, or replays a captured ta; a live config-copy test is pending before the cron uses it: a copy without a shumeiId takes two runs, the first saving the pushed id and the second sending it, while a copy that already has one, such as a recapture with pcap -session-out, sends it from its first run). On 2026-10-04 a captured iOS session also
reconnected with shumeiBoxId sent empty, see Live validation against production.
No ShuMei-specific block was ever found. Fully decompiled (Obfuscator-LLVM strings reversed); the device-profile protocol is documented in ShuMei device fingerprint |
| Tencent ACE anti-cheat report | Not found on the game-server protocol at all, local IPC to Tencent’s own backend | None identified |
SecurityCode/OneCode/CoreV | login request, ~3 fields | None: plain MD5 with a hardcoded salt, fully reproducible |
packageSign (despite the name, not a cert hash, see Findings & further work) | login request | None: actually SHA1(packageName), a constant public string; trivially
reproducible without touching the APK’s real signature. The field that genuinely depends on the signing
cert is psh (see Identity, login & session), and the Go client reproduces the
Android formula correctly; 1.0.364 is signed with the same certificate, so that value is unchanged.
In iOS mode it sends the iOS app’s own formula, recovered from the iOS binary’s
rg_getPsh:; see Identity, login & session. Until 2026-10-18 iOS mode sent the
Android value, which the server accepted for weeks. |
libxlua.so CalcChatSign/AES/MD5 helpers | None in 1.0.364: the native chat branch in ChatNetManager:InitWebSocketInst is unreachable, so chat always uses the C# ChatService | None, resolved via direct ARM64 disassembly (see Findings & further work):
plain unkeyed MD5(MD5(appId+uid)+timestamp), byte-identical to the known C# formula, no custom
key material. Only the armeabi-v7a libxlua registers rg_websocket; arm64’s
luaopen_native registers only rg_sqlite, rg_async, cutils,
md5, base64, and crypt, and LuaEntry:__InitCModule(), the
only code that would expose the native socket, is never called (static-analysis-only) |
| TLS / certificate validation | All HTTPS traffic | None: no pinning evidence found anywhere. Standard chain validation everywhere except the XAssetPro bundle downloader, which disables certificate validation (see Startup, version-check & hot-update) |
| Google Play Integrity / SafetyNet | , | Not used at all in this build |