DisclosureLens
Leak SiteState AGConfirmed6 records · 4 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedakira
Merged incident · 6 records

Sunrise — April 2026 breach

Clustered 6 records across 4 jurisdictions: 4 filings and 2 leak-site claims · filing window Jul 28, 2026 → Jul 31, 2026. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

6 records

States

4

Affected · reported

4,516

First → last filing

Jul 28, 2026 → Jul 31, 2026

Merge confidence

100%

incident inc_d78da057cc294606 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings and 2 unverified claims. The filing describes unauthorized access. Intrusion Apr 23, 2026, discovered Jun 15, 2026 — the first regulatory filing landed 43 days later. 4,516 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and Financial account. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
43days

Discovered → first regulatory filing

Leak precedence
63days before filing

Days between the first sighting of the earliest-seen leak-site claim and the first regulatory filing. Measured from when the aggregator first saw the post, not the crew's own (often earlier) date. 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
3days

Time between earliest and latest filing

Not recorded for this incident

Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.

Regulatory clocksLeak gap⏱ Leak >30dFull clock table in Litigation Timeline

Incident timeline

Apr 23, 2026breach begins
Jun 15, 2026discovered
notification delay · 43 days
Jul 28, 2026first filing
Jul 31, 2026most recent filing

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

Member cascade — every filing and leak-site claim in this incident

  1. MAY 26Leak siteakira postfirst record · attacker claim · unverifiedday 0
  2. JUN 3Leak siteakira postattacker claim · unverified+8d
  3. JUL 28IN AGIN AG noticestates nationwide total 4,516+63d
  4. JUL 28CA AGCA AG noticeno count stated+63d
  5. JUL 29MA AGMA AG notice9 MA residents+64d
  6. JUL 31TX AGTX AG noticemost recent · states nationwide total 4,516+66d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 23, 2026
IN AG
Discovered
Jun 15, 2026· 53d undetected
TX AG
Data types
Identity (basic) · Financial account · Government ID
CA AG + MA AG + TX AG
Attack vector
Unauthorized Access
CA 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)

4,516

Sum of filed state slices

301· 6.7% of stated

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

US4,516
TX284
MA9
IN8

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

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