3 ms·

Idea: (never used Google Cloud, no idea of possible impediments) 1. Create throwaway account 2. Create throwaway project using throwaway account 3. Find e

Idea: (never used Google Cloud, no idea of possible impediments) 1. Create throwaway account 2. Create throwaway project using throwaway account 3. Find emails of possible Googlers using public bug tracker 4. Add Googlers' emails to throwaway project 5. Post messages to throwaway project describing the problem 6. Hopefully Googlers understand the issue and can forward the issue to get it resolved

deleted 4y ago
[deleted]
toast0 4y ago
7. Throwaway Google account gets locked for ToS (adding people without their permission) 8. Associated real Google accounts get locked for being associated with throwaway (unless you have really good OpSec) Might be worth a post on their bug bounty program though, assuming GCP is in scope https://bughunters.google.com/ https://bughunters.google.com/
- Ephil012 4y ago
  That’s a great idea. I’ll try reporting it on their bug bounty Edit: Reported it
015a 4y ago
Idea: 1. Create a throwaway account. 2. Add a bunch of professional developers' at big companies email addresses to the account. Just shoot in the dark: johnanderson@google.com, mikejohnson@airbnb.com, wandamaximov@apple.com, throw in a couple common email aliases as well like developers@twitter.com or mobileteam@airbnb.com 3. Publish a bunch of apps to the play store which clearly breaks their app store policies 4. Google has been known to automatically network-ban associated accounts and their play store apps if a play store account is found in violation of their policies.
- gpm 4y ago
  I'm sure this isn't a serious suggestion anyways... but if you were going to be malicious like this you ought to not include google.com accounts. They're likely treated differently. Also, harvesting actual emails from github is really easy.
- iJohnDoe 4y ago
  Actually, add @apple.com emails. They are a large GCP customer for iCloud. You could potentially bring down iCloud.
xyzzy_plugh 4y ago
You joke but this won't actually work as the GCP dashboard is already useless for Googlers as it often doesn't even load due to the sheer volume of projects.
deleted 4y ago
[deleted]

deleted 4y ago

[deleted]

toast0 4y ago

7. Throwaway Google account gets locked for ToS (adding people without their permission) 8. Associated real Google accounts get locked for being associated with throwaway (unless you have really good OpSec) Might be worth a post on their bug bounty program though, assuming GCP is in scope https://bughunters.google.com/ https://bughunters.google.com/

Ephil012 4y ago
That’s a great idea. I’ll try reporting it on their bug bounty Edit: Reported it

015a 4y ago

Idea: 1. Create a throwaway account. 2. Add a bunch of professional developers' at big companies email addresses to the account. Just shoot in the dark: johnanderson@google.com, mikejohnson@airbnb.com, wandamaximov@apple.com, throw in a couple common email aliases as well like developers@twitter.com or mobileteam@airbnb.com 3. Publish a bunch of apps to the play store which clearly breaks their app store policies 4. Google has been known to automatically network-ban associated accounts and their play store apps if a play store account is found in violation of their policies.

gpm 4y ago
I'm sure this isn't a serious suggestion anyways... but if you were going to be malicious like this you ought to not include google.com accounts. They're likely treated differently. Also, harvesting actual emails from github is really easy.
iJohnDoe 4y ago
Actually, add @apple.com emails. They are a large GCP customer for iCloud. You could potentially bring down iCloud.

xyzzy_plugh 4y ago

You joke but this won't actually work as the GCP dashboard is already useless for Googlers as it often doesn't even load due to the sheer volume of projects.

deleted 4y ago

[deleted]