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

Entertainment Partners

Clustered 5 filings across 5 jurisdictions · filing window Aug 11, 2023 → Aug 15, 2023. View entity profile → Other incidents for this victim →

✓ data types, discovery date agreeMerge100%

Determination

Confirmed

Members

5 filings

States

5

Affected · reported

8,121

First → last filing

Aug 11, 2023 → Aug 15, 2023

Merge confidence

100%

incident inc_7dab6b7dd5694e6d · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings. Discovered Jun 30, 2023 — the first regulatory filing landed 42 days later. 8,121 individuals reported across the linked filings. Data reported: Government ID and Identity (basic). Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
42days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
4days

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 >30dHawaii✓ HI CRA notice dueSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

? — ?breach window unknown
Jun 30, 2023discovered
notification delay · 42 days
Aug 11, 2023first filing
Aug 15, 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. AUG 11WA AGWA AG noticefirst filing · 2,758 WA residentsday 0
  2. AUG 11HI AGHI AG notice3,340 HI residentsday 0
  3. AUG 11MT AGMT AG notice281 MT residentsday 0
  4. AUG 11CA AGCA AG noticeno count statedday 0
  5. AUG 15SC AGSC AG noticemost recent · 1,742 SC residents+4d
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
—
Discovered
Jun 30, 2023
WA AG + HI AG + MT AG +2
Data types
Identity (basic) · Government ID
WA AG + HI AG + MT AG +2
Attack vector
Ransomware
WA AG

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

Affected residents by state

per-state reported counts

HI3,340
WA2,758
SC1,742
MT281

State AGs report only their own residents; teal bars show each state's reported slice.

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 filing5 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

4 days

Cadence

~1 / 1d

vs. multi-state median

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