GHunt is an OSINT tool to extract information from any Google Account using an email.
It can currently extract:
- Owner's name
- Last time the profile was edited
- Google ID
- If the account is a Hangouts Bot
- Activated Google services (YouTube, Photos, Maps, News360, Hangouts, etc.)
- Possible YouTube channel
- Possible other usernames
- Public photos (P)
- Phones models (P)
- Phones firmwares (P)
- Installed softwares (P)
- Google Maps reviews (M)
- Possible physical location (M)
The features marked with a (P) require the target account to have the default setting of Allow the people you share content with to download your photos and videos on Picasa, or have used Picasa linked to their Google account.
More info here.
Those marked with a (M) require the Google Maps reviews of the target to be public (they are by default).
- 02/10/2020 : Since few days ago, Google return a 404 when we try to access someone's Google Photos public albums, we can only access it if we have a link of one of his albums.
Either this is a bug and this will be fixed, either it's a protection that we need to find how to bypass. - 03/10/2020 : Successfully bypassed. 🕺 (commit 01dc016)
It requires the "Profile photos" album to be public (it is by default)
You can build the Docker image with:
docker build --build-arg UID=$(id -u ${USER}) --build-arg GID=$(id -g ${USER}) -t ghunt .
Any of the scripts can be invoked through:
docker run -v $(pwd)/resources:/usr/src/app/resources -ti ghunt check_and_gen.py
docker run -v $(pwd)/resources:/usr/src/app/resources -ti ghunt hunt.py <email_address>
- Make sure you have Python 3.6.1+ installed. (I developed it with Python 3.8.1)
- Some Python modules are required which are contained in
requirements.txtand will be installed below.
This project uses Selenium and automatically downloads the correct driver for your Chrome version.
In the GHunt folder, run:
python -m pip install -r requirements.txtAdapt the command to your operating system if needed.
For the first run and sometimes after, you'll need to check the validity of your cookies.
To do this, run check_and_gen.py.
If you don't have cookies stored (ex: first launch), you will be asked for the 4 required cookies. If they are valid, it will generate the Authentication token and the Google Docs & Hangouts tokens.
Then, you can run the tool like this:
python hunt.py myemail@gmail.com- Log in to accounts.google.com
- After that, open the Dev Tools window and navigate to the Storage tab (Shift + F9 on Firefox) (It's called "Application" on Chrome)
If you don't know how to open it, just right-click anywhere and click "Inspect Element". - Then you'll find every cookie you need, including the 4 ones.
Regarding the collection of metadata from your Google Photos account:
Given that Google shows "X require access" on your Google Account Dashboard, you might imagine that you had to explicitly authorize another account in order for it to access your pictures; but this is not the case.
Any account can access your AlbumArchive (by default):
Here's how to check and fix the fact that you're vulnerable (wich you most likely are):
Go to https://get.google.com/albumarchive/ while logged in with your Google account. You will be automatically redirected to your correct albumarchive URL (https://get.google.com/albumarchive/). After that, click the three dots on the top left corner, and click on setting
Then, un-check the only option there:
On another note, the target account will also be vulnerable if they have ever used Picasa linked to their Google account in any way, shape or form. For more details on this, read PinkDev1's comment on issue #10.
For now, the only (known) solution to this is to delete the Picasa albums from your AlbumArchive.
This tool is based on Sector's research on Google IDs and completed by my own as well.
If I have the motivation to write a blog post about it, I'll add the link here !