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

VARSITY BRANDS, INC. — May 2024 breach

Clustered 9 filings across 9 jurisdictions · filed Oct 14, 2024 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

9 filings

States

9

Affected · reported

65,669

First → last dated filing

Oct 14, 2024

Merge confidence

100%

incident inc_d462af38229c46a6 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. Intrusion May 22, 2024–May 24, 2024, discovered May 24, 2024. 65,669 individuals reported across the linked filings. Data reported: Government ID, Financial account, Health (basic), and 3 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
0days

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 >90dVermont✗ VT AG >45 bdayCalifornia✗ CA 60-day late · 143dMaine⏱ ME AG >30d · 143dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 22, 2024breach begins
May 24, 2024discovered
Oct 14, 2024first 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 about this breach

  1. OCT 1IL AGIL AG noticefiling day not on record · no count stated—
  2. OCT 14WA AGWA AG noticefirst filing · 934 WA residentsday 0
  3. OCT 14ME AGME AG noticestates nationwide total 65,669day 0
  4. OCT 14VT AGVT AG noticeno count statedday 0
  5. OCT 14IN AGIN AG noticestates nationwide total 65,669day 0
  6. OCT 14MA AGMA AG notice912 MA residentsday 0
  7. OCT 14MT AGMT AG notice84 MT residentsday 0
  8. OCT 14NH AGNH AG noticeno count statedday 0
  9. OCT 14CA AGCA AG noticemost recent · no count statedday 0
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 24, 2024
WA AG
Discovered
May 24, 2024
IL AG + WA AG + ME AG +4
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
WA AG + MA AG + ME AG +4
Attack vector
Ransomware
WA 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)

65,669

Sum of filed state slices

7,092· 10.8% of stated

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

US65,669
IN5,072
WA934
MA912
ME90
MT84

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
Reviewed
operator-reviewed Jun 12, 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.