🦫Oregon State AGFirst filing
Filed Sep 18, 2017bd_01042eb2a1c1134f
TRUEbenefits LLC reported a data breach to the Oregon Attorney General. The breach was reported on 2017-09-18. 20,476 individuals were affected.
Affected (this filing): 20,476
Clustered 2 filings across 2 jurisdictions · filed Sep 18, 2017. View entity profile → Other incidents for this victim →
incident inc_eabab76a0132445a · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
CA OR
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
May 19, 2017
When the intrusion reportedly occurred, per the linked filings
Jun 26, 2017
Reported by CALIFORNIA AG filing
TRUEbenefits LLC reported a data breach to the Oregon Attorney General. The breach was reported on 2017-09-18. 20,476 individuals were affected.
Affected (this filing): 20,476
TRUEbenefits LLC, an insurance brokerage, reported a security incident on May 19, 2017, involving unauthorized access to an employee's email account via a phishing scheme. The breach exposed names, Social Security numbers, and health plan details (diagnoses, claims, invoices) of clients and their dependents. TRUEbenefits secured the account, engaged forensic investigators, and offered two years of Experian IdentityWorks monitoring to affected individuals.
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.