DisclosureLens
Leak SiteState AGConfirmed5 records · 4 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedqilinhigh sensitivity
Merged incident · 5 records

Shrader & Associates — April 2025 breach

Clustered 5 records across 4 jurisdictions: 4 filings and 1 leak-site claim · filed Jun 16, 2025 (dated filings only). View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

5 records

States

4

Affected · reported

525

First → last dated filing

Jun 16, 2025

Merge confidence

100%

incident inc_3a96bcb26be44907 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings and 1 unverified claim. The filings describe a ransomware attack. Intrusion Apr 8, 2025, discovered Apr 9, 2025 — the first regulatory filing landed 68 days later. 525 individuals reported across the linked filings. Data reported: Government ID, Health (basic), and Identity (basic). Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
68days

Discovered → first regulatory filing

Discovery variance
34days

Range of discovered_at dates across filings

Leak precedence
39days 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
0days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksLeak gap⏱ Leak >30dMaine⏱ ME AG >30d · 68dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Apr 8, 2025breach begins
Apr 9, 2025discovered · members disagree
notification delay · 68 days
Jun 16, 2025first dated filing
—watching for filings

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 and leak-site claim in this incident

  1. APR 8Leak siteqilin postfirst record · attacker claim · unverifiedday 0
  2. JUN 16IN AGIN AG noticestates nationwide total 525+69d
  3. JUN 16MA AGMA AG notice6 MA residents+69d
  4. JUN 16ME AGME AG noticemost recent · states nationwide total 525+69d
  5. JUN 16NE AGNE AG noticefiling day not on record · no count stated—
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 8, 2025
IN AG
Discovered
Apr 9, 2025ME AGMay 13, 2025NE AGfilings disagree on discovery
Data types
Health (basic) · Identity (basic) · Government ID
MA AG + ME AG + NE AG
Attack vector
Ransomware
ME 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)

525

Sum of filed state slices

27· 5.1% of stated

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

US525
IN18
MA6
ME3

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 claim1 member

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

0 days

Cadence

~1 / 0d

vs. multi-state median

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