ucla.edu Domain Breach Exposure Report
Risk Score
Massive event volume or critical assets compromised.
AI Findings Summary
The telemetry indicates a significant exposure event for ucla.edu, with a risk score of 100. Over the reporting period, there were 160,140 historical data breaches and 5,990 infostealer events. The majority of these events, 96.4%, are attributed to historical data breaches, while 3.6% are active infostealer logs. The timeline shows a sharp increase in employee and client events starting in September 2025, with notable peaks in January and February 2026. Malware families like Acreed, Redline, and LummaC2 are prevalent, suggesting active compromise and data exfiltration attempts. Targeted services include core ucla.edu domains and authentication services like shibboleth-idp, indicating potential compromise of identity and access management infrastructure. The data also points to combolist sources and database dumps as significant leak repository classifications, suggesting credential stuffing and large-scale data leakage.
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
107,456 compromised employee accounts pose an infrastructure risk, while 58,674 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.