Is Game Killer safe?
Checked 2026-11-17.
Any APK that does not come from a store account you trust can be repackaged. I do not call the root editor safe, and I do not call the sandbox safe. The Play puzzle is a normal store game with ads, which is a different risk from a memory tool.
Permissions that show up in public listings
| android.permission.ACCESS_SUPERUSER | Requests superuser (root) access from the device's su manager | Full privileged control; a malicious build could do anything root can do | Yes — the su prompt can be refused, but the app then cannot edit other apps' memory | 2.70 | 1 source (Uptodown manifest) |
| android.permission.SYSTEM_ALERT_WINDOW | Draws the floating icon over the running game | May obscure another app’s UI; permission alone does not establish malicious behaviour | Yes — 'Display over other apps' can be switched off, which disables the floating icon | 2.70 (Uptodown listing) | 1 source (Uptodown listing) |
| android.permission.READ_PHONE_STATE | Reads phone state and device identifiers; sometimes used for licence or ad targeting | A game-value editor has no functional need for call state or device IDs | Yes — Android can deny it; the app may still run | 2.70 | 1 source (Uptodown manifest) |
| android.permission.ACCESS_COARSE_LOCATION | Approximate location, typically for ad targeting | No editing feature needs location; a common ad-SDK permission | Yes | 2.70 | 1 source (Uptodown manifest) |
| android.permission.ACCESS_COARSE_UPDATES | Not a standard Android platform permission; likely a vendor or legacy constant | Legacy/non-standard name in the listing; this name alone does not prove repackaging | Unknown — does not appear in stock Android permission lists | 2.70 | 1 source (Uptodown manifest) |
| android.permission.READ_EXTERNAL_STORAGE | Reads shared storage, e.g. to locate game data or save files | Broad read access to photos, downloads and documents | Yes — though the app may lose save-editing features | 2.70 | 1 source (Uptodown manifest) |
| android.permission.WRITE_EXTERNAL_STORAGE | Writes to shared storage, e.g. to patch a save file | Can modify or delete any user file the app can reach | Yes | 2.70 | 1 source (Uptodown manifest) |
| android.permission.GET_TASKS | Lists currently and recently running apps so the tool can pick a target process | Reveals everything the user runs; deprecated on modern Android | Deprecated — modern Android ignores it | 2.70 | 1 source (Uptodown manifest) |
| android.permission.INTERNET | Loads ads and update checks | An offline memory editor that needs the network is usually ad-funded | Yes — via network blocking, not the permission dialog | 2.70 | 1 source (Uptodown manifest) |
| android.permission.ACCESS_NETWORK_STATE | Checks connectivity before requesting ads | Low risk on its own; pairs with INTERNET | Not user-facing | 2.70 | 1 source (Uptodown manifest) |
| android.permission.ACCESS_WIFI_STATE | Reads Wi-Fi state for connectivity checks | Low risk; can reveal nearby network names on old Android | Not user-facing | 2.70 | 1 source (Uptodown manifest) |
| android.permission.MANAGE_EXTERNAL_STORAGE | Broad shared-storage access; the Reddit quotation does not establish why this specific build requests it | The single broadest storage permission; Google Play restricts it to file managers and similar apps | Yes — via Settings > Special app access > All files access | 5.x (quoted from a VirusTotal report on Reddit) | 1 source (Reddit quote of a VirusTotal manifest) |
| android.permission.READ_CALENDAR | None for a game tool | Reading the user's calendar has no plausible link to editing game values | Yes | 5.x (VirusTotal quote) | 1 source (Reddit quote of a VirusTotal manifest) |
| android.permission.BODY_SENSORS | None for a game tool | Health sensor access is the least plausible permission in the list | Yes | 5.x (VirusTotal quote) | 1 source (Reddit quote of a VirusTotal manifest) |
| android.permission.WRITE_CALL_LOG | None for a game tool | Restricted call-log write access; unexplained for a game tool, not itself a malware verdict | Yes — and Google Play policy restricts it heavily | 5.x (VirusTotal quote) | 1 source (Reddit quote of a VirusTotal manifest) |
| android.permission.ACCESS_BACKGROUND_LOCATION | None for a game tool | Location tracking while the app is not in use; hardest location permission to justify | Yes — Android 11+ requires a separate settings step | 5.x (VirusTotal quote) | 1 source (Reddit quote of a VirusTotal manifest) |
| android.permission.CAMERA | None documented; the Reddit quote lists it | Camera access from a value editor is unexplained | Yes | 5.x (VirusTotal quote) | 1 source (Reddit quote of a VirusTotal manifest) |
| Installed application list (launcher apps) | Reads installed app names and icons to build the icon puzzles | Reveals the full app inventory, but the official site says it never leaves the phone | No — without it the game has no puzzles | com.gamefun.killer (current) | 1 source (official puzzle-game site) |
| android.permission.VIBRATE | Haptic feedback on taps | None | Can be switched off in settings | com.gamefun.killer (current) | 1 source (official puzzle-game site) |
A Dec 2025 Reddit comment says the sandbox build asks for a much longer list, on the order of 28 permissions. The table labels each quoted sandbox permission as a Reddit report, not an inspected manifest, because the comment is one source and the sandbox page itself does not print the manifest. The Uptodown panel for 2.70 is a different file.
What I would check before installing
- Compare the package name on the download page with the row you meant to install.
- Read the permission sheet on that same page, not a screenshot from a forum.
- Leave Play Protect on. A page that tells you to turn it off is describing a risk, not removing it.
- Prefer the Play listing when you wanted the puzzle, because that package is actually on Play.
The sandbox page calls itself the place to get the app. Play returned not found for com.gk.speed.booster.tool. That gap is the reason this page exists. It is not a reason to skip the permission read.
Questions people ask
Is Game Killer safe to install?
A third-party APK is not something I will call safe. The root editor declares superuser and overlay. The sandbox is discussed on Reddit for broad file access. The Play puzzle is a different app with its own ad stack.
Is gamekillerapp safe, according to Reddit?
Threads disagree. A 24 Apr 2025 post mixes a working report with a question about file access. A 9 Dec 2025 post says not to use it and cites a long permission list. A 22 Jul 2026 post rejects it and complains about ads.
¿playmods.net o gamekillerapp.com?
A PlayMods search for the name returned no Game Killer entry on 17 Nov 2026. gamekillerapp.com does list a 5.4.2 page. Neither result is a safety certificate.
Sources
- Uptodown permissions — checked 2026-11-17. Read the declared permission names for 2.70.
- Reddit Apr 2025 — checked 2026-11-17. Research excerpt; review recheck returned HTTP 403, so this remains a single reported account. Read the thread title and the file-permission question.
- Reddit Dec 2025 — checked 2026-11-17. Research excerpt; review recheck returned HTTP 403, so this remains a single reported account. Read the rejection and the permission count claim.
- Reddit Jul 2026 — checked 2026-11-17. Research excerpt; review recheck returned HTTP 403, so this remains a single reported account. Read the rejection and the ad complaint.
- Puzzle safety page — checked 2026-11-17. Read the puzzle’s own permission and ad description.