*Update: Evidence of False Positive ToS Bans tied to GCP Identity/Session Desync (Even with Native CLI)*
Hi everyone, just wanted to share a critical update on my investigation into the sudden 403 ToS bans impacting Paid/Ultra Tier users.
After migrating completely away from any third-party open-source CLIs and running **exclusively on the native official CLI**, the severe account instability and 403 ToS blocks persisted.
However, while doing a deep audit of my Google Cloud environment, I stumbled upon a major architectural anomaly that I believe is the actual root cause triggering the automated WAF/Anti-Abuse system.
It appears there is a severe “Session Bleed” or identity desynchronization occurring in the backend when a user operates a standard Consumer Account (e.g., standard Google account) alongside a Workspace/Cloud Identity organizational account in the same environment.
When the official native CLI attempts the OAuth handshake, the Application Default Credentials (ADC) or the active session token gets polluted with an inconsistent mix of organizational constraints and consumer tier limits.
**The Result:** The automated security backend reads this “schizophrenic” token state not as a legitimate Google Cloud UI/CLI bug, but erroneously flags it as a “Violative/Unauthorized Client” or an attempt to bypass ToS, triggering an immediate and silent 403 ban on the Gemini API.
This means many of us aren’t being banned for “abusing” the API or using “unauthorized tools.” We are victims of a False Positive generated by a session management bug within GCP’s own identity infrastructure crossing wires between our Consumer and Workspace profiles.
I am currently compiling a formal architecture vulnerability report for the Google Cloud VRP (Vulnerability Reward Program) regarding the underlying GCP Identity flaw. But the AI team needs to urgently halt these automated ToS bans on Paid Tier accounts until the Cloud Infrastructure team resolves this cross-account authorization bleed.
The collateral damage on legitimate developers is entirely unjustified.
-–
*(Note: I am holding back the exact reproduction steps of the GCP bug as it is being routed to the Cloud VRP, but this context is vital for the AI team to understand the false positives).*
.