Everything on the download pages tells you to install the file. This page starts from the opposite end: given a file you already have, how do you know whether it is the original Game Killer, a repack of it, or a completely different app wearing the name?
The checker above does the arithmetic for you. It compares what you typed against the last recorded original release:
| Field | Original value |
|---|---|
| Package | cn.lm.sq |
| Version | 2.70 (Aug 2023) |
| Size | 308.58 KB |
| SHA-256 | 6d7078c57b34184063c190f87d4825445984c236cad250acdccfcd445738a054 |
How to get the three numbers
- Package name — open the APK in any APK analyser on Android, or run
aapt dump badging file.apk | head -1if you have the SDK. The package is on the first line. - Size — the file manager's properties pane, in KB. A "Game Killer" of 60,000 KB is not this tool.
- SHA-256 —
sha256sum file.apkon macOS/Linux,Get-FileHash file.apk -Algorithm SHA256in PowerShell, or any hash app on the phone. This is the check a repacker cannot fake: changing one byte changes the hash.
What each verdict means
- Matches the original. The file is the recorded 2.70 build. It still needs root, and it is still a memory editor with ban risk — "original" is not the same as "safe".
- Partial match. Something differs: an older version, a different size, or an unrelated package. Check the signature before you install anything.
- Not the original build. Most often this is one of the 60–70 MB toolbox apps (
com.gk.*packages) that trade on the same name. It is not a newer Game Killer.
Why the hash matters more than the name
Every site in this niche labels its file "Game Killer". Only one thing distinguishes the file from its label: content. A checksum is a fingerprint of content, so the moment you have the expected SHA-256, the filename, the screenshot and the "official" badge stop mattering.
If a page will not publish a checksum for the file it distributes, that is information too.
Limits of this check
The reference values describe one release. An older original build will not match the hash and may still be genuine — but older builds are also where most repacks hide, so "it's an older version" is not a reason to skip the signature check. And no hash check tells you whether granting root to a memory editor is a good idea for your device: that decision is on the safety page.