Leaking the phone number of any Google user
brutecat.com | blog | #privacy | #ipv6 | #enumeration | #google | #account-recovery | #rate-limit-bypass | #botguard
Summary
A Google username recovery endpoint allowed checking phone number ownership; rotating IPv6 addresses from a /64 subnet beat rate limits, and JS-form BotGuard tokens bypassed the captcha wall.
- Published
- Collected
--- id: 1189 title: "Leaking the phone number of any Google user" source_domain: brutecat.com source_url: "https://brutecat.com/articles/leaking-google-phones/" published_at: "2025-06-09 00:00" tags: ["privacy", "ipv6", "enumeration", "google", "account-recovery", "rate-limit-bypass", "botguard"] phying_url: "https://phying.com/item/1189" lang: en --- # Leaking the phone number of any Google user ## Summary A Google username recovery endpoint allowed checking phone number ownership; rotating IPv6 addresses from a /64 subnet beat rate limits, and JS-form BotGuard tokens bypassed the captcha wall. ## Intelligence Metadata - **Sources:** brutecat.com - **Published:** 2025-06-09 00:00 - **Original:** https://brutecat.com/articles/leaking-google-phones/ - **Phying News:** https://phying.com/item/1189