A GitHub project named google-ultra enables users to activate free trials of Google One AI Pro (5TB) by automating interactions with Google Play’s billing interface. The method does not involve server manipulation or APK modification. Instead, it leverages hidden subscription offers accessible only through the client-side BillingClient API — a behaviour documented in security research, not an official Google promotion.
The tool has drawn attention from technically skilled users in the UK, US, UAE, and Kazakhstan, particularly founders and IT specialists evaluating cloud cost optimisation. However, its use carries policy, operational, and legal risks that outweigh short-term benefits for most organisations.
How the tool works
The google-ultra project provides two methods to access a hidden 12-month free trial of Google One AI Pro (5TB):
- Web version (
web/index.html): A standalone HTML file run locally in a browser. Users log in to their Google account, add a payment method, and manually confirm the zero-cost subscription. - Script version (
pro.py): Requires a rooted Android device or the MuMu emulator with root enabled, plus Python 3.9+, Frida, and ADB. It automates the full flow: adding the account, switching Play Store profiles, querying offers viaqueryProductDetailsAsync, and launching the billing flow if a valid offer is found.
The script checks for two specific offers:
– 12months-eft (12 months free, $0/P1Y) for SKU g1.2tb.ai.subs_variant
– Fallback: eft-3mo (3 months free, $0/P3M) for SKU g1.play.2tb.ai
It avoids attempting Ultra-tier plans (20TB or 30TB), as these offers have been removed. While the script still includes code paths for them (--plan 5x, --plan 20x), they are inactive and will fail for nearly all users.
Crucially, the process relies on Google’s own BillingClient within the Google One app. No Xposed, APK edits, or server-side spoofing are used.
Eligibility and technical requirements
Success depends on strict account conditions:
- Account region: Must be set to the US. Accounts from other regions cannot access the offer.
- Payment method: A valid card must be linked. The web version requires manual input; the script pauses if no card is present, prompting the user to add one via the device.
- No prior Google One subscriptions: Even cancelled or expired subscriptions disqualify an account. Google Play tracks historical subscription activity, making requalification impossible.
Technically, users need:
– For script use: Rooted Android device (Magisk, KernelSU, APatch) or MuMu Player 12 (Windows) / MuMu Pro (Mac, Apple Silicon only) with root enabled.
– Python 3.9+, frida, and adb (via Android SDK platform-tools).
– On Mac: brew install android-platform-tools; on Windows: manually install platform-tools and add to PATH.
– USB debugging enabled on the device.
The project includes a wizard (start.command / start.bat) that automates environment checks, connects to MuMu if needed, and runs the process. Results are saved locally in ultra0-report/, including offer details and step-by-step logs.
Card details (number, expiry, CVC, name, ZIP) can be provided in a text file, formatted with ---- separators. If omitted, the script defaults to a dummy address in Portland, OR (97201), a location with no sales tax.
What it means for businesses
This is not a vulnerability in the traditional sense, but a demonstration of how client-side billing logic can expose unintended access paths. For founders and IT professionals, it underscores several critical points:
- Dependency risk: Cloud providers like Google control access dynamically. Offers can vanish overnight, as seen with the discontinued Ultra-tier trials. Relying on such mechanisms introduces instability.
- Cost vs. control: While AI Pro normally costs $19.99/month after trial, obtaining it via automation bypasses intended user flows. This may violate Google’s Terms of Service, risking account suspension — especially for business-critical data.
- Data sovereignty and compliance: Users in the UK, UAE, and Kazakhstan must use US-region accounts, potentially conflicting with local data residency expectations. Though the tool runs locally, storing data under a US account may complicate compliance with GDPR (UK), ADHICS (UAE), or Kazakhstan’s personal data laws.
- No scalability: The project explicitly prohibits commercial, bulk, or paid use. It is licensed under MIT for research only. Automated access is not supported by Google and cannot be operationalised reliably.
For IT teams, this highlights the importance of avoiding dependency on consumer-tier cloud perks. While the script itself does not transmit credentials, using non-standard methods on work devices increases audit and governance risks.
Proceed with caution
The project maintainers clearly state this is a security research effort, not a service. It is unaffiliated with Google and provided “as is” without warranty. Users assume all risks, including potential account bans.
Google has not commented on the tool. However, given that the AI Pro 5TB offer remains active in some accounts, enforcement could come at any time. Users are advised:
- Never use primary or business accounts.
- Cancel before the trial ends to avoid $19.99/month charges.
- Avoid any commercial use — it violates the project’s terms and likely Google’s policies.
- Treat this as a technical demonstration, not a cost-saving strategy.
As with all grey-area exploits, the short-term gain is outweighed by long-term risk — especially for organisations building on cloud infrastructure.