The Union Labor Life Insurance Company reported to HHS on 2017-10-19 a Unauthorized Access/Disclosure affecting 664 individuals. Breached information located on Email.
Affected (this filing): 664
Clustered 2 filings across 2 jurisdictions · filing window Oct 19, 2017 → Oct 27, 2017. View entity profile → Other incidents for this victim →
incident inc_5e97d0748b734283 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
Government ID · Identity (basic) · Health (basic)
CA MD
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jun 22, 2017
Reported by CALIFORNIA AG filing
Jun 27, 2017
When the intrusion reportedly occurred, per the linked filings
Jun 27, 2017
Reported by HHS OCR filing
The Union Labor Life Insurance Company reported to HHS on 2017-10-19 a Unauthorized Access/Disclosure affecting 664 individuals. Breached information located on Email.
Affected (this filing): 664
On June 22, 2017, an unauthorized external user accessed an employee's Outlook email account at The Union Labor Life Insurance Company. The attacker sent spam emails with malicious links to contacts. A forensic review determined that the attacker may have viewed emails containing personal information, including names, SSNs, and PHI (claim numbers, diagnosis codes), of individuals. The company disabled the account, reset passwords, engaged forensic investigators, and offered 24 months of identity protection services.
About this clustering
DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.