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

Catalyst Brands LLC — May 2026 breach

Clustered 9 filings across 9 jurisdictions · filing window Sep 4, 2026 → Sep 9, 2026 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

9

Affected · reported

187,341

First → last dated filing

Sep 4, 2026 → Sep 9, 2026

Merge confidence

100%

incident inc_c6b0a1e5d98e4126 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. The filings describe a third-party compromise. Intrusion May 20, 2026–Jun 10, 2026, discovered May 26, 2026. 187,341 individuals reported across the linked filings. Data reported: Government ID, Credentials, Financial account, and 3 more. Notifications rolled out on a 5-day schedule across 8 dated filings beginning Sep 4, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
71days

Range of discovered_at dates across filings

Filing span
5days

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 clocksWashington✗ WA AG >90dSouth Carolina✓ SC CRA notice dueDate basis✓ Clock withheld · confirmation dateTexas✓ TX CRA notice dueFull clock table in Litigation Timeline

Sensitive data

authenticationidentity_government

Incident timeline

May 20, 2026breach begins
May 26, 2026discovered · members disagree
Sep 4, 2026first dated filing
Sep 9, 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 about this breach

  1. SEP 1MA AGMA AG noticefiling day not on record · 2,798 MA residents—
  2. SEP 4VT AGVT AG noticefirst filing · 234 VT residentsday 0
  3. SEP 4SC AGSC AG notice2,234 SC residentsday 0
  4. SEP 4WA AGWA AG notice4,015 WA residentsday 0
  5. SEP 4IN AGIN AG noticestates nationwide total 187,341day 0
  6. SEP 4DE AGDE AG noticeno count statedday 0
  7. SEP 4CA AGCA AG noticeno count statedday 0
  8. SEP 4OR AGOR AG noticestates nationwide total 187,341day 0
  9. SEP 9TX AGTX AG noticemost recent · states nationwide total 187,341+5d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 20, 2026
MA AG
Discovered
May 26, 2026WA AG + DE AGAug 5, 2026OR AG + TX AGfilings disagree on discovery
Data types
Authentication · Credentials · Financial account · Identity (basic) · Government ID · PCI
MA AG + SC AG + DE AG +4
Attack vector
Third-Party / Supply Chain
MA 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)

187,341

Sum of filed state slices

37,815· 20.2% of stated

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

US187,341
TX24,403
IN4,131
WA4,015
MA2,798
SC2,234
VT234

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 claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

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

5 days

Cadence

~1 / 0.7d

vs. multi-state median

1.2× faster

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.