Hide Veil itself from target apps by default
An installed hooking module is as much a tell as a root manager, but Veil's own package wasn't in the hidden list, so any scoped app could find it with getPackageInfo or the installed-package lists. It's now a default alongside KernelSU and Magisk. DEFAULT_HIDDEN_PACKAGES only applies while no list has been saved, so a one-time migration adds Veil to an existing list the first time the settings screen opens; a flag stops it from re-adding Veil after a manual removal. Discovery is unaffected: the hooked process resolves Veil's provider through ActivityManager, not the hooked ApplicationPackageManager. Verified on device (Android 16, Vector) with Veil Probe: getPackageInfo for Veil now throws NameNotFoundException, the probe still registers, and every other hooked path stays hidden. Co-Authored-By: agent <agent@bdeshi.space>
This commit is contained in:
4 files changed
+22
-5
No files matched your search
@@ -35,7 +35,7 @@ Per app, per feature — anything not listed gets everything hidden by default.
|
||||
| USB / wireless debugging | `adb_enabled` / `adb_wifi_enabled` |
|
||||
| Developer options | Developer Options enabled state |
|
||||
| Mock location | Legacy pre-Marshmallow flag only |
|
||||
| Root / manager apps | Configurable package list (default: KernelSU, Magisk) |
|
||||
| Root / manager apps | Package list (default: KernelSU, Magisk, Veil itself) |
|
||||
| Build tags/type | Real build swapped for `release-keys` / `user` |
|
||||
|
||||
Doesn't cover native-level root/hook detection or remote attestation (Play Integrity,
|
||||
|
||||
Reference in new issue
Block a user