What Is Game Killer? The Original App, Package and Mechanism
Game Killer (八门神器) explained: package cn.lm.sq, version 2.70, how the memory scanner works, and why three different apps share the name.
Game Killer is the English name of 八门神器 ("Eight-door artifact"), an Android tool by the developer 枫影(尹湘中) that edits values inside another app's memory while that app runs. In practice it is used on games: change the number of coins, the number of lives, or a cooldown, and the game behaves as if that were always the value.
There is no Wikipedia article and no Google Play listing for it, which is exactly why the name has become a grab-bag. This page is the identity check: what the original build is, how to recognise it, and what it technically does.
The original build, by the numbers
These facts come from the Uptodown listing of the original app, which is the most stable public record of it:
| Field | Value |
|---|---|
| Name | Game Killer: Eight-door artifact |
| Developer | 枫影(尹湘中) |
| Package name | cn.lm.sq |
| Last version listed | 2.70 |
| Release date | 21 August 2023 |
| File size | 308.58 KB |
| Certificate signature | d818496eea12d6b9c528a46fcf89fc8b |
| Downloads on that listing | 11.45 million |
| Rating | 4.0 from 92 reviews |
| Minimum Android | 1.5 (historical) |
| Price / licence | Free, proprietary |
Two of those rows matter more than the rest. The package name is the app's real identity: two files with the same package name are the same app, and two files with different package names are different apps no matter what the filename says. The signature is the identity of whoever built the file: an APK signed with a different certificate than the author's is a repack, even if it installs and runs.
What it actually does
Game Killer is a memory scanner with a floating overlay. The mechanism is the same one used by every value editor of this kind:
- It attaches to the process of another app running on the same device.
- It scans that process's memory for a specific value you type in — the visible coin count, for example.
- It narrows the matches by asking you for the value again after it changed.
- It writes a new number into the surviving address.
Because this is a direct read and write into another process's address space, it needs root. On a stock phone, Android's sandbox prevents it, and no amount of "no root" branding changes that for the original build.
What it does not do
- It does not touch server-side values. If the game checks your balance with its server, the local number is only a display.
- It does not patch the game's code. It edits data, not instructions — which is why the effect often resets on the next sync or restart.
- It does not bypass anti-cheat. Modern games look at memory integrity and at the presence of debugging or overlay tools.
- It does not work on every app layout. Values that are stored as floats, encrypted, or split across structures are much harder to find than plain integers.
Why the name is confusing
Search "game killer apk" and you will find at least three things:
- The original 2.70 build, package
cn.lm.sq, around 309 KB. - Repacks of it, sometimes renamed, sometimes with added payloads.
- Different apps trading on the name — for example a 68 MB package called
com.gk.speed.booster.toolmarketed as "Game Killer v5.4.2" with sandbox, auto-clicker and speed-hack features. That is a speed-booster style toolbox, not the memory editor, and none of its version numbers relate to the original.
If a page mixes "root required memory editor" with "no root sandbox, 11 features, 68 MB", it is describing the second category. Useful to know before you compare tutorials that no longer match your file.
What the tool is genuinely good for
- Emulators and offline single-player games, where a wrong value costs you a save file and nothing else.
- Learning what memory editing is. The search-narrow-write loop is the concept behind every cheat tool; doing it once by hand makes the rest of the category legible.
- Small, old games that store everything locally and have no anti-cheat.
What to read next
- How to use Game Killer — the actual loop, with the failure cases.
- Is it safe — file-level and account-level risk.
- Getting the right build — verify package and signature before installing.
- Alternatives — what other tools do differently.