Eyemart Express — February 2026 breach
Clustered 15 filings across 11 jurisdictions · filing window Feb 19, 2026 → Aug 4, 2026. View entity profile → Other incidents for this victim →
incident inc_b833c4116b944c8b · merged by deterministic · confidence 100%
Litigation Timing
Discovered → first regulatory filing
Range of discovered_at dates across filings
Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.
Time between earliest and latest filing
Not recorded for this incident
Materiality delta · SEC filing delay — no SEC 8-K in this cluster.
Sensitive data
identity_governmentIncident timeline
Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.
Member cascade — every filing about this breach
- FEB 19Leak sitepayoutsking postfirst filing · attacker claim · unverifiedoperator-confirmedday 0
- APR 17TX AGTX AG noticeno count stated+57d
- MAY 12OR AGOR AG noticestates nationwide total 250operator-confirmed+82d
- MAY 18HHS OCRHHS OCR noticestates nationwide total 25,000auto-linked+88d
- JUL 1IL AGIL AG noticeno count statedauto-linked+132d
- JUL 15NE AGNE AG noticeno count statedoperator-confirmed+146d
- JUL 21TX AGTX AG noticestates nationwide total 189,450operator-confirmed+152d
- JUL 24CA AGCA AG noticeno count statedauto-linked+155d
- JUL 24MA AGMA AG notice5 MA residentsauto-linked+155d
- JUL 24IA AGIA AG notice567 IA residentsauto-linked+155d
- JUL 24VT AGVT AG notice1 VT residentsauto-linked+155d
- JUL 24WA AGWA AG notice1,704 WA residentsoperator-confirmed+155d
- JUL 24NH AGNH AG notice36 NH residentsoperator-confirmed+155d
- AUG 4OR AGOR AG noticemost recent · states nationwide total 2,638auto-linked+166d
- Watching for additional filings — new sources merge into this incident automatically.
Roll-up facts — reconciled across members
- Breach window
- Feb 12, 2026 – Feb 13, 2026 TX AG
- Discovered
- Feb 13, 2026OR AG + NE AG + CA AG +3Mar 17, 2026TX AG + IL AG + WA AGfilings disagree on discovery
- Data types
- Employment · Financial · Financial account · Health (basic) · Identity (basic) · Government ID · PCI · PHI · PII TX AG + HHS OCR + CA AG +7
- Attack vector
- Unauthorized Access HHS OCR
Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.
Count reconciliation
per-state reported counts
Nationwide (stated in a filing)
189,450
Sum of filed state slices
47,773· 25.2% of stated
75% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.
State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.
Evidence ladder — rungs this incident occupies
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
No SEC filing or victim statement yet.
Merge provenance
- Method
- deterministic
- Confidence
- 1.00 · above the 0.85 auto-merge floor
- Reviewed
- operator-reviewed Aug 22, 2026 · at least one link edge was human-adjudicated
- Audit
- Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).
Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.
Filing velocity
Spread
172 days
Cadence
~1 / 12.3d
vs. multi-state median
21.5× slower
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. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.
The weekly clock on records like this one
The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.
Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.