DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed8 filings · 6 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedblack_bastahigh sensitivity
Merged incident · 8 filings

GATES CORPORATION — February 2023 breach

Clustered 8 filings across 7 jurisdictions · filing window Jan 1, 2023 → Jul 7, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 filings

States

6

Affected · reported

11,090

First → last filing

Jan 1, 2023 → Jul 7, 2023

Merge confidence

100%

incident inc_358d64b24ad34fe3 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings and 2 unverified claims. Intrusion Feb 7, 2023–Feb 11, 2023, discovered Apr 30, 2023. 11,090 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 2 more. Notifications rolled out on a 187-day schedule across 6 filings beginning Jan 1, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
15days

Range of discovered_at dates across filings

Leak precedence
Noneclaim trailed by 41d

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
187days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksVermont✗ VT AG >45 bdayLeak gap⏱ Leak >90dMaine⏱ ME AG >30d · 53dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 7, 2023breach begins
Apr 30, 2023discovered · members disagree
Jan 1, 2023first filing
Jul 7, 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. JAN 1IL AGIL AG noticefirst filing · no count statedday 0
  2. FEB 11Leak siteblack_basta postattacker claim · unverified+41d
  3. APR 27Leak siteblack_basta postattacker claim · unverified+116d
  4. JUN 30IN AGIN AG noticestates nationwide total 11,090+180d
  5. JUL 7MT AGMT AG notice1 MT residents+187d
  6. JUL 7ME AGME AG noticestates nationwide total 11,090+187d
  7. JUL 7VT AGVT AG noticeno count stated+187d
  8. JUL 7NH AGNH AG noticemost recent · 68 NH residents+187d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 7, 2023
IN AG
Discovered
Apr 30, 2023MT AG + VT AG + NH AGMay 15, 2023IL AG + ME AGfilings disagree on discovery
Data types
Employment · Financial account · Identity (basic) · Government ID · PII
MT AG + ME AG + VT AG +1
Attack vector
Ransomware
MT AG

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)

11,090

Sum of filed state slices

106· 1.0% of stated

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

US11,090
NH68
IN34
ME3
MT1

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 claim2 members

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

Press / market report

No press coverage linked yet.

State AG / regulator filing6 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 Jun 24, 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

187 days

Cadence

~1 / 26.7d

vs. multi-state median

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