vivibibi30/hyperpguard

Overview

HyperPGuard is an LSPosed module for HyperOS that intercepts privacy reporting from preinstalled system components. Instead of relying only on network filtering, it cuts reporting at four stages: the data source (privacy APIs), local storage (behaviour database writes and silent screen recording), IPC interfaces (XSOF Provider/AIDL), and network egress (URL, InetAddress and Socket hooks).

The target components include SystemHelper, the system security component, Security Center, Xiaomi Analytics, the installer, the app store, the ads component, the Xiaomi service framework, the carrier registration and DM components, system diagnostics, the trust service and the translation component. Per-app switches follow the LSPosed scope: apps outside the scope are not injected. Rules that would break system features are off by default and are labelled with their cost README.

It is intended for people who own and fully control a rooted HyperOS device and want to reduce telemetry without disabling whole components. The project is GPL-3.0, source is in src/, and the APK is built by build.sh without Gradle license.

Quick Start

1. Install the APK from the Releases page or the LSPosed module listing LSPosed module page.
2. Enable HyperPGuard in LSPosed. On first launch, the app requests all scopes; allow it, or tick scopes manually in LSPosed.
3. In the module, tap Restart on a target app card, or Restart all on the batch row, so the app reloads with the hooks.
4. Trigger a reporting action (for example, open Security Center or install an app), then tap View log. You should see attach <package> and X(...) entries; XSOF lines should read hooked without miss.

If only attach appears, turn on Record unblocked access, run for a while, and add the domains prefixed with ? to the custom rules, whose syntax is documented in the custom rules guide. After an upgrade, revisit LSPosed → Module → HyperPGuard → Scope, since newly added components are not selected automatically.

Constraints

• Requires Android 10–16 on HyperOS, LSPosed 2.2.x (libxposed API 100+), and root via KernelSU, Magisk or APatch for the restart and log features.
• Coverage is limited to identified channels; it does not represent all HyperOS network activity. Requests using native network stacks (Cronet and similar) bypass the Java-layer hooks.
• Method-layer hooks depend on class names and can report hook miss after component updates; the network and privacy-API layers keep working independently.
• Domain lists may miss addresses delivered by remote configuration; custom method-level rules change return values inside the target process and are the user's responsibility.
• com.mobiletools.systemhelper permissions are granted during first-time setup; the module blocks reporting but does not revoke granted permissions.
• Personal, non-commercial use on devices you own; the module makes no network requests unless you tap the update check, and it is provided as-is under GPL-3.0. See the disclaimer for the full terms.

HotRepo's take

HyperPGuard entered HotRepo's new-project list on 2026-11-11, with a Java-language snapshot showing 104 stars, 6 forks and 4 stars gained in a roughly 1.5-hour window; the star curve moved from 101 to 104 over the last hour sampled. It has no recorded GitHub all-language daily rank. What stands out is the documentation rather than the numbers: the README separates the four interception layers, lists which components are covered and which rules default to off, and records adaptation limits such as Cronet bypassing the Java hooks and hook miss after component updates. For a personal, AI-assisted project with an explicitly reduced release cadence, that level of boundary disclosure is the useful signal; the small star sample so far says little about adoption.