DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed11 records · 8 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedsilentransomgrouphigh sensitivity
Merged incident · 11 records

Greenberg Traurig, P.A. — August 2026 breach

Clustered 11 records across 8 jurisdictions: 10 filings and 1 leak-site claim · filing window Sep 8, 2026 → Oct 2, 2026 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

11 records

States

8

Affected · reported

150,000

First → last dated filing

Sep 8, 2026 → Oct 2, 2026

Merge confidence

100%

incident inc_a5a632a2d59c4333 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings and 1 unverified claim. Intrusion Aug 26, 2026, discovered Aug 26, 2026. 150,000 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 2 more. Notifications rolled out on a 24-day schedule across 9 dated filings beginning Sep 8, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
0days

Range of discovered_at dates across filings

Filing span
24days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksCalifornia✗ CA AG copy >15d · 23dSouth Carolina✓ SC CRA notice dueOregon✓ OR AG ≤45dTexas✓ TX AG ≤30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 26, 2026breach begins
Aug 26, 2026discovered
Sep 8, 2026first dated filing
Oct 2, 2026most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing and leak-site claim in this incident

  1. SEP 1MA AGMA AG noticefiling day not on record · 97 MA residents—
  2. SEP 2Leak sitesilentransomgroup postfirst record · attacker claim · unverifiedday 0
  3. SEP 8IN AGIN AG noticestates nationwide total 150,000+6d
  4. SEP 8VT AGVT AG notice10 VT residents+6d
  5. SEP 8NH AGNH AG notice13 NH residents+6d
  6. SEP 9CA AGCA AG noticeno count stated+7d
  7. SEP 9SC AGSC AG notice2,516 SC residents+7d
  8. SEP 9OR AGOR AG noticestates nationwide total 150,000+7d
  9. SEP 11TX AGTX AG noticestates nationwide total 150,000+9d
  10. OCT 1CA AGCA AG noticeno count stated+29d
  11. OCT 2TX AGTX AG noticemost recent · states nationwide total 150,000+30d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 26, 2026
IN AG
Discovered
Aug 26, 2026
MA AG + NH AG + SC AG +3
Data types
Employment · Financial account · Identity (basic) · Government ID · PII
MA AG + NH AG + CA AG +3

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)

150,000

Sum of filed state slices

4,570· 3.0% of stated

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

US150,000
SC2,516
TX1,839
MA97
IN95
NH13
VT10

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 filing10 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 Sep 14, 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

24 days

Cadence

~1 / 3d

vs. multi-state median

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