HackingData ExfiltratedCustomer Data InvolvedIDENTITY_BASICLowContained
Alexes Hazen MD, PLLC
bd_88b63ad0ae769d41 · schema v1 · pii pii-v1
Full breach record for Alexes Hazen MD, PLLC →Alexes Hazen, MD, PLLC notified Massachusetts and Rhode Island residents of unauthorized access to computer systems between June 23, 2025, and January 20, 2026. The incident may have exposed patient names. The practice offered credit monitoring and identity restoration services via Experian. Approximately 5 Rhode Island residents were identified as potentially impacted.
Massachusetts clock✗ MA AG >90d49 weeks discovery → filing
⚠ occurrence dateThe stored discovery date equals the breach OCCURRENCE date. Detection is normally later, so this OVERSTATES the delay — a 'late' verdict here may not be real.
This filing is one of 2 about the same incident.View merged incident
Linked disclosures
Why this link?Regulatory filings (1) · sorted by filing gap
- bd_95f9aa44b8241cd6Vermont State AGfiled 2026-06-08(7d gap)Verified
Source provenance
- Source URL
- https://www.mass.gov/doc/2026-927-alexes-hazen-md-pllc/download
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
- Filed at
- Jun 1, 2026
- Raw hash
- 33cff3cc205e3e444a04595d76faf3dee80c1f39f8891879aa94472cde19f133
Reporting entity
- Name
- Alexes Hazen MD, PLLCnorm: alexes hazen md
- Domain
- alexeshazenmd.com
Victim entity
- Name
- Alexes Hazen MD, PLLCnorm: alexes hazen md
- Domain
- alexeshazenmd.com
Incident
- Discovered
- Jun 23, 2025
- Materiality determined
- Jun 8, 2026
- Notification sent
- Jun 8, 2026
- Affected individuals
- Not disclosed
- Data types
- IDENTITY_BASIC
- Attack vector
- Unauthorized Access
- MITRE ATT&CK
- T1190 Exploit Public-Facing Application
- Threat actor
- External
- Regulator citations
- Notified regulatory bodies
- Initial access
- exploit_public_facing
Compliance
- Time to disclose
- 49 weeks(343 days from discovery to filing)
- Compliance flags
- MA AG >90d
- Discovery-date grounding
- occurrence dateThe stored discovery date equals the breach OCCURRENCE date. Detection is normally later, so this OVERSTATES the delay — a 'late' verdict here may not be real.
Extraction provenance
- Status
- No extraction artifact recorded for this disclosure.