Mazoku is a narrowly targeted ARM64 Zygisk module for Call of Duty: Mobile 1.0.48 that intercepts specific ACE attestation paths and supplies backed copies of configured application libraries.
A Version-Specific Zygisk Instrument
Its process target, offsets, and supported game build are specific rather than a general anti-cheat compatibility layer.
Hard-Coded Target
The native module loads its runtime only in com.activision.callofduty.shooter.
Library Scope File
Targets are read from /data/adb/mazoku/spoof_target_libs.txt, which is created during installation.
ACE Update Check
The module action compares upstream ACE files and can mark Mazoku disabled when its packaged handling needs an update.
Documented Scope
- The repository identifies Call of Duty: Mobile 1.0.48 as the only currently supported application version.
- The release is built for ARM64 only.
- Installation must occur from a running Magisk or KernelSU manager; recovery installation is rejected.
- A working Zygisk implementation is required. KernelSU users therefore need a compatible Zygisk provider.
- The implementation depends on version-specific ACE objects, offsets, and response patches, so a game or backend update can invalidate it.
Repository-Documented Setup
- Disable other modules or modifiers affecting the target application before establishing a clean baseline.
- Install Mazoku from Magisk or KernelSU and review
/data/adb/mazoku/spoof_target_libs.txt. - Use the documented
?prefix to request a backed copy or!to require and verify an existing copy for a listed application library. - Reboot, start the supported game build, and inspect the target application's
files/.mazokudirectory. - Compare the generated block hashes before re-enabling any separate modification, and stop if the result does not match the expected library.
Explicit Limitations
The author states that Mazoku does not handle system libraries such as libc.so, does not conceal its own presence from the target process, and does not hide other modifiers exposed in that process. Those limits mean it should not be described as universal detection avoidance or as a durable solution for later application releases.