offensive-tools/osint/ghunt/SKILL.md
Google account OSINT tool — enumerate Google profile data, linked services, Calendar events, Maps reviews, YouTube activity, and photo metadata from an email address or Gaia ID. Use when you have a Gmail address and need to map the target's Google footprint: profile photo, account creation hints, linked Android apps, location history artifacts, and public activity.
npx skillsauth add aeondave/malskill ghuntInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Google account OSINT — profile, services, location artifacts, linked apps from Gmail address.
pip install ghunt
# First-time setup — authenticate with Google cookies
ghunt login
# Investigate a Gmail address
ghunt email [email protected]
# Investigate by Gaia ID (Google internal user ID)
ghunt gaia 123456789
# Investigate a Google Drive link
ghunt drive https://drive.google.com/file/d/FILEID/view
GHunt requires valid Google cookies from a logged-in browser session.
# Interactive login (opens browser URL to capture cookies)
ghunt login
# Or manually export cookies from browser
# Install "Cookie-Editor" extension (Firefox/Chrome)
# Export cookies from google.com as JSON → ghunt login --file cookies.json
Use a throwaway Google account for OPSEC — your account appears as a viewer in some cases.
| Command | Target | Output |
|---------|--------|--------|
| ghunt email <email> | Gmail address | Profile, Gaia ID, services |
| ghunt gaia <id> | Google Gaia ID | Same as email |
| ghunt drive <url> | Google Drive link | File metadata, owner |
| ghunt doc <url> | Google Docs link | Document metadata |
| ghunt calendar <id> | Calendar ID | Public events |
| ghunt play <email> | Gmail | Google Play reviews |
Whether the account has active:
Full email investigation:
ghunt email [email protected]
# Outputs: name, Gaia ID, profile photo URL, active services
Reverse image search profile photo:
# Get photo URL from ghunt output, then:
# yandex.com/images → search by image URL
# images.google.com → paste image URL
# tineye.com → reverse image search
Drive file owner identification:
# From a shared Google Drive link (e.g., from LinkedIn/email)
ghunt drive "https://drive.google.com/file/d/1BxiMVs0XRA5nFMdKvBdBZjgmUUqptlbs74OgVE2upms/view"
# Reveals: owner email, file name, creation date
Calendar public event scraping:
ghunt calendar [email protected]
JSON output for automation:
ghunt email [email protected] --json > ghunt_results.json
import json, subprocess
result = subprocess.run(
["ghunt", "email", "[email protected]", "--json"],
capture_output=True, text=True
)
data = json.loads(result.stdout)
print("Name:", data.get("name"))
print("Gaia ID:", data.get("gaia_id"))
print("Services:", [s for s, active in data.get("services", {}).items() if active])
The Gaia ID is Google's internal persistent user identifier:
# Search Gaia ID in Google URLs
https://plus.google.com/<GAIA_ID> # legacy, redirects
https://www.google.com/maps/contrib/<GAIA_ID>/reviews # Maps reviews
| File | When to load |
|------|--------------|
| references/google-osint.md | Google dorking, Drive/Doc metadata extraction, Maps review scraping, Gaia ID pivot |
data-ai
Scoped routing: Linux operator; hosts, sessions, users, services, packages, logs, containers, SSH, network paths, privilege evidence.
development
Offensive methodology for ICS/OT/SCADA environments in authorized industrial penetration testing and red team operations. Use when assessing PLCs, RTUs, HMIs, engineering workstations, historians, or field devices running Modbus, DNP3, EtherNet/IP, S7comm/S7+, Profinet, IEC 60870-5-104, BACnet, or OPC-UA. Covers passive OT network enumeration, protocol-level device interrogation, PLC coil/register read-write attacks, HMI session exploitation, historian and engineering workstation compromise, and safe escalation rules for critical infrastructure scope. Does not cover: general IT network exploitation (network-technique), physical hardware interfaces UART/JTAG/SPI (hardware-technique), wireless sensor network attacks (wireless-technique), RF/SDR signal analysis (hardware-ctf or wireless-technique), or CTF-framed ICS lab tasks (ics-ctf).
tools
Offensive methodology for authorized game security assessments, game client security research, and game-adjacent penetration testing in real-world engagements. Use when assessing game clients for cheating vulnerabilities, testing anti-cheat effectiveness, auditing game server protocols for score manipulation or economic fraud, reverse engineering game DRM or license validation, analyzing game save file protection, or assessing game mod/plugin security. Covers: process memory scanning and manipulation (Cheat Engine methodology), game binary reversing for license and DRM bypass, game network protocol analysis and packet replay, anti-cheat mechanism analysis, save file format reversing and tampering, speed hack and value injection techniques. Does NOT cover: CTF game challenges (game-ctf), game engine source code auditing (web-exploit-technique or vuln-search-technique for the backend), or general binary exploitation (pwn-ctf or reversing-technique).
development
Auth assessment: hardware/embedded methodology; UART/JTAG/SWD/SPI/I2C, firmware extraction, boot/debug paths, embedded OS evidence.