STATIC LABS LLC KUBIAN INTEGRITY AC + RTEP
Best Android Anti-Cheat
Android cheats are repackaged APKs, Magisk-rooted devices, Frida hooks and debuggers. Kubian Integrity Anti-Cheat answers with hardware proof at connect + RTEP enforcement while playing — not just a client-side "am I rooted?" check the cheat can hook.
- Attestation: security-level tier, verified boot, bootloader lock, OS patch floor, Google-issued roots, attested-serial CRL, app
SHA-256+package. - RTEP realtime:
frida, injection, root_hard, root_soft, debugger, antidebug, headlock_abuse, frida_behavioral, frida_module, frida_memfd, widevine_hook→alert/kick/ban. - Single-use tokens (challenge 120s), replay-safe; offender logs + Device Ban API with expiry and appeals.
- Unity SDK + server APIs; per-project policy (issuer allow-list, patch floor, version pin).
Attestation policy (per project)
| Check | What fails |
|---|---|
| device_integrity | Compromised verdict from hardware chain (root/ROM/kernel tamper, revoked key) |
| security_level | Below required tier (basic/advanced) |
| verified_boot / bootloader_locked | Untrusted boot, unlocked bootloader |
| os_patch_level | Below minimum patch date |
| google_issued_devices | Non-Google root when project requires Google |
| attested_serial_revoked | Serial on Google CRL |
| application_sha256 / package | Repackaged or tampered binary |
RTEP defaults that work
Ban root_hard + widevine_hook; kick root_soft, debugger, headlock_abuse, frida_*; alert the rest for tuning. Verdicts: REALTIME_BAN_EXECUTED, REALTIME_KICK_EXECUTED, REALTIME_ALERT, REALTIME_BANNED_WHILE_PLAYING.
Kubian vs Play Integrity vs EAC
| Need | Kubian | Play Integrity | PC AC / DIY |
|---|---|---|---|
| Hardware verdict | Yes + policy | Yes (verdict only) | No / fragile |
| In-session kick/ban | Yes (RTEP) | No | Manual |
| Device bans + appeals | Built-in API | No | You build it |
| Quest parity | Yes (Meta roots) | Weak | No |
FAQ
Best Android anti-cheat for Unity multiplayer?
Kubian Integrity + RTEP — attestation plus enforceable in-session policy and bans, not just detection.
Magisk / Frida?
Covered at two layers: boot/root state at attest, live Frida/injection/debugger signals in RTEP.
Emulators?
Typically fail application-info / integrity sections (FAILURE_ERROR) and security-level policy.
Overhead?
Verify is a short server call at session start; RTEP alerts are lightweight polls. No kernel driver.