DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteHHS OCRState AGConfirmed26 filings · 8 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedcl0phigh sensitivity
Merged incident · 26 filings

Brightline — January 2023 breach

Clustered 26 filings across 9 jurisdictions · filing window Mar 16, 2023 → May 26, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

26 filings

States

8

Affected · reported

473,467

First → last filing

Mar 16, 2023 → May 26, 2023

Merge confidence

100%

incident inc_063615a1fc464f7a · merged by deterministic · confidence 100%

Part of the FORTRA, LLC supply-chain incident (2023) — at least 12 organizations filed notifications naming this third party.
Confirmed breach. Merged as one breach: 25 regulatory filings and 1 unverified claim. The filings describe hacking. Intrusion Jan 30, 2023, discovered Feb 4, 2023 — the first regulatory filing landed 62 days later (flagged late). 473,467 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 3 more. Notifications rolled out on a 71-day schedule across 25 filings beginning Mar 16, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
62days

Discovered → first regulatory filing

Discovery variance
2days

Range of discovered_at dates across filings

Leak precedence
22days before filing

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.

Filing span
71days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksMaine✗ ME AG >90d · 93dVermont✗ VT AG >45 bdayOregon✗ OR AG >45dCalifornia✗ CA 60-day late · 62dWashington⏱ WA AG >30dLeak gap⏱ Leak >30dHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jan 30, 2023breach begins
Feb 4, 2023discovered · members disagree
notification delay · 62 days
Apr 7, 2023first filing
May 26, 2023most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. MAR 16Leak sitecl0p postfirst filing · attacker claim · unverifiedday 0
  2. APR 7HHS OCRHHS OCR noticestates nationwide total 199,753+22d
  3. APR 7ME AGME AG noticestates nationwide total 27,742+22d
  4. APR 7MT AGMT AG notice403 MT residents+22d
  5. APR 7HHS OCRHHS OCR noticestates nationwide total 7,411+22d
  6. APR 7HHS OCRHHS OCR noticestates nationwide total 473,467+22d
  7. APR 7HHS OCRHHS OCR noticestates nationwide total 21,830+22d
  8. APR 7DE AGDE AG noticeno count stated+22d
  9. APR 7HHS OCRHHS OCR noticestates nationwide total 7,672+22d
  10. APR 7HHS OCRHHS OCR noticestates nationwide total 31,440+22d
  11. APR 7HHS OCRHHS OCR noticestates nationwide total 4,044+22d
  12. APR 7VT AGVT AG noticeno count stated+22d
  13. APR 10WA AGWA AG notice26,333 WA residents+25d
  14. APR 12CA AGCA AG noticeno count stated+27d
  15. APR 13HHS OCRHHS OCR noticestates nationwide total 49,968+28d
  16. APR 17NH AGNH AG notice180 NH residents+32d
  17. APR 19VT AGVT AG noticeno count stated+34d
  18. APR 20HHS OCRHHS OCR noticestates nationwide total 180,694+35d
  19. APR 21CA AGCA AG noticeno count stated+36d
  20. MAY 2OR AGOR AG noticeno count stated+47d
  21. MAY 10HHS OCRHHS OCR noticestates nationwide total 28,975+55d
  22. MAY 10ME AGME AG noticestates nationwide total 28,975+55d
  23. MAY 10CA AGCA AG noticeno count stated+55d
  24. MAY 12CA AGCA AG noticeno count stated+57d
  25. MAY 17CA AGCA AG noticeno count stated+62d
  26. MAY 26HHS OCRHHS OCR noticemost recent · states nationwide total 8,432+71d
  27. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jan 30, 2023
ME AG
Discovered
Feb 4, 2023MT AG + DE AG + VT AG +4Feb 6, 2023ME AG + HHS OCRfilings disagree on discovery
Data types
Employment · Health (basic) · Identity (basic) · Government ID · PHI · PII
HHS OCR + CA AG + ME AG +5
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)

473,467

Sum of filed state slices

26,974· 5.7% of stated

94% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US473,467
WA26,333
MT403
NH180
ME58

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

Leak-site claim1 member

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing25 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

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

71 days

Cadence

~1 / 2.8d

vs. multi-state median

7.9× 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.