DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
State AGConfirmed4 filings · 2 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 4 filings

CommerceV3 — November 2021 breach

Clustered 4 filings across 2 jurisdictions · filing window Jun 16, 2023 → Jul 21, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

4 filings

States

2

Affected · reported

not comparable

First → last filing

Jun 16, 2023 → Jul 21, 2023

Merge confidence

100%

incident inc_a7a5db095b244247 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings. The filings describe hacking. Intrusion Nov 24, 2021–Dec 14, 2022, discovered May 3, 2023 — the first regulatory filing landed 44 days later. Data reported: PII, Financial account, Financial credentials, and 1 more. Notifications rolled out on a 35-day schedule across 4 filings beginning Jun 16, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
44days

Discovered → first regulatory filing

Discovery variance
40days

Range of discovered_at dates across filings

Filing span
35days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

financial_credentials

Incident timeline

Nov 24, 2021breach begins
May 3, 2023discovered · members disagree
notification delay · 44 days
Jun 16, 2023first filing
Jul 21, 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. JUN 16MT AGMT AG noticefirst filing · 34 MT residentsday 0
  2. JUN 29MT AGMT AG notice2 MT residents+13d
  3. JUL 5SC AGSC AG notice5,001 SC residents+19d
  4. JUL 21MT AGMT AG noticemost recent · 223 MT residents+35d
  5. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 24, 2021 – Jul 1, 2022
MT AG
Discovered
May 3, 2023SC AGJun 6, 2023MT AGJun 7, 2023MT AGJun 12, 2023MT AGfilings disagree on discovery
Data types
Financial account · Financial credentials · Identity (basic) · PII
MT AG + SC AG
Attack vector
Third-Party / Supply Chain
MT AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing4 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
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

35 days

Cadence

~1 / 11.7d

vs. multi-state median

4.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.