google.es Domain Breach Exposure Report
Risk Score
Massive event volume or critical assets compromised.
AI Findings Summary
The domain google.es has experienced a high volume of events, primarily driven by historical data breaches (90.1%) and active infostealer logs (9.9%). A significant portion of these events are linked to combolist sources (97.2%), indicating potential credential stuffing or account takeover attempts. The timeline shows a surge in client-related events in March and April 2026, alongside a notable increase in employee-related events in September 2025 and February 2026. Malware families such as LummaC2 and Redline are prominently associated with these events. The exposure is prioritized due to the high risk score of 90 and the direct impact on both employees and clients, suggesting a broad compromise. Remediation should focus on strengthening authentication mechanisms, monitoring for credential stuffing attacks targeting google.es, and investigating the source of the infostealer logs and data breaches.
Total Events
Employee Affected Events
Client Affected Events
Free Community Account
Stop stolen credentials from logging in
Own this domain? Create a free Lunar account to see full exposure data and evidence.Disclaimer: This report was generated automatically using Lunar's telemetry data. If you own this domain or manage its cybersecurity, create a free Lunar Community account to view the underlying exposure data and evidence.
12-Month Events Timeline
Event volume by breach date, employee VS client
Infostealers VS Data Breaches
Live stealer logs VS data breaches
560 compromised employee accounts pose an infrastructure risk, while 4,653 leaked client credentials create regulatory liability.
Antivirus Distribution
Security Tools on Infected Endpoints
Malware Families Distribution
Distribution of Active Stealer Strains
Top Login URLs
Top exposed services found in the event results
Infostealer By Geography
Shows the distribution of Infostealer-related credential exposure events across different geographic regions. The location is determined by analyzing the metadata of the infected machines associated with each event.
Country Breakdown
Services Classification Distribution
Blast radius - closer to core = more critical infrastructure, size = credential volume
Operating System Distribution
Distribution of compromised endpoint builds
Leak Repository Classification
Where the exposed records currently reside
Disclaimer: This report includes AI-generated content. AI can make mistakes, so verify important findings independently before taking action.