DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteState AGConfirmed10 filings · 8 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedblack_bastahigh sensitivity
Merged incident · 10 filings

ANDY FRAIN SERVICES, INC. — October 2024 breach

Clustered 10 filings across 9 jurisdictions · filing window Oct 23, 2024 → May 13, 2025. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

10 filings

States

8

Affected · reported

100,964

First → last filing

Oct 23, 2024 → May 13, 2025

Merge confidence

100%

incident inc_c4d33f0245d24dba · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings and 1 unverified claim. Intrusion Oct 23, 2024, discovered Oct 23, 2024 — the first regulatory filing landed 190 days later (flagged late). 100,964 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 2 more. Notifications rolled out on a 202-day schedule across 9 filings beginning Oct 23, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
190days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
190days 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
202days

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 >180dMaine✗ ME AG >90d · 198dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Oct 23, 2024breach begins
Oct 23, 2024discovered
notification delay · 190 days
May 1, 2025first filing
May 13, 2025most 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. OCT 23Leak siteblack_basta postfirst filing · attacker claim · unverifiedday 0
  2. MAY 1IL AGIL AG noticeno count stated+190d
  3. MAY 1IL AGIL AG noticeno count stated+190d
  4. MAY 5NE AGNE AG noticeno count stated+194d
  5. MAY 5IN AGIN AG noticestates nationwide total 100,964+194d
  6. MAY 9WA AGWA AG notice1,046 WA residents+198d
  7. MAY 9ME AGME AG noticestates nationwide total 100,964+198d
  8. MAY 12NH AGNH AG notice34 NH residents+201d
  9. MAY 12CA AGCA AG noticeno count stated+201d
  10. MAY 13MA AGMA AG noticemost recent · 1,107 MA residents+202d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 23, 2024
IN AG
Discovered
Oct 23, 2024
IL AG + WA AG + ME AG +2
Data types
Employment · Financial account · Identity (basic) · Government ID · PII
IL AG + NE AG + WA AG +4
Attack vector
Unauthorized Access
NE 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)

100,964

Sum of filed state slices

6,160· 6.1% of stated

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

US100,964
IN3,894
MA1,107
WA1,046
ME79
NH34

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 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 Aug 23, 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

202 days

Cadence

~1 / 22.4d

vs. multi-state median

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