google.co.jp Domain Breach Exposure Report
Risk Score
Massive event volume or critical assets compromised.
AI Findings Summary
The domain google.co.jp has experienced a significant number of security events over the past year, with a high volume of data breaches (2439) and active infostealer logs (1095). The majority of these events are attributed to "Combolist sources" (97.1%) within leak repositories, indicating credential stuffing or account takeover attempts. Malware families such as LummaC2 (46.6%) are prevalent, targeting Windows 11 operating systems. The exposure primarily affects clients (3035) and employees (499), with a notable concentration of events originating from Japan. The high risk score of 88 suggests a critical need for immediate attention to mitigate further compromise and protect sensitive information.
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
499 compromised employee accounts pose an infrastructure risk, while 3,035 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.