Google Cloud suspended my project for “possible hijacking” — no clear proof? So my project on Google Cloud just got suspended out of nowhere. Reason they gave: >"Associated with abusive activity consistent with hijacking" And then: * Maybe your API keys were exposed * Maybe service account leaked * Maybe third party used your project But the problem is… I didn’t expose any keys (at least not knowingly). And they didn’t give: * which key was compromised * what activity happened * when it happened Just a generic automated message. Now the account is suspended and I can’t even do anything inside the console. I’ve already: * Checked my code (no public keys) * Rotated credentials just in case But still no clarity on what actually triggered this. I saw someone mentioning that these flags are sometimes triggered by automated systems and even internally they’ve seen false positives. So now I’m wondering: 👉 Is this actually a real compromise? 👉 Or just a false flag? Has anyone here faced this before?…