DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteState AGConfirmed6 filings · 4 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcednokoyawahigh sensitivity
Merged incident · 6 filings

Liveaction inc. — April 2023 breach

Clustered 6 filings across 5 jurisdictions · filing window May 22, 2023 → Oct 30, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

6 filings

States

4

Affected · reported

532

First → last filing

May 22, 2023 → Oct 30, 2023

Merge confidence

100%

incident inc_1cf1e82ff3034fb2 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings and 2 unverified claims. Intrusion Apr 13, 2023–May 22, 2023, discovered May 21, 2023 — the first regulatory filing landed 162 days later (flagged late). 532 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Health (basic), and 2 more. Notifications rolled out on a 161-day schedule across 4 filings beginning May 22, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
162days

Discovered → first regulatory filing

Discovery variance
1days

Range of discovered_at dates across filings

Leak precedence
161days before filing

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

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksMaine✗ ME AG >90d · 162dLeak gap⏱ Leak >90dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Apr 13, 2023breach begins
May 21, 2023discovered · members disagree
notification delay · 162 days
Oct 30, 2023first filing
—watching for filings

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. MAY 22Leak sitenokoyawa postfirst filing · attacker claim · unverifiedday 0
  2. MAY 22Leak sitesnatch postattacker claim · unverifiedday 0
  3. OCT 30MT AGMT AG notice1 MT residents+161d
  4. OCT 30MA AGMA AG notice4 MA residents+161d
  5. OCT 30ME AGME AG noticestates nationwide total 532+161d
  6. OCT 30NH AGNH AG noticemost recent · 6 NH residents+161d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 13, 2023
ME AG
Discovered
May 21, 2023ME AGMay 22, 2023MT AG + NH AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PII
MT AG + ME AG + NH 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)

532

Sum of filed state slices

12· 2.3% of stated

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

US532
NH6
MA4
MT1
ME1

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 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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 22, 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

161 days

Cadence

~1 / 32.2d

vs. multi-state median

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