DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed8 filings · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmedusahigh sensitivity
Merged incident · 8 filings

Anders Group, LLC — March 2024 breach

Clustered 8 filings across 6 jurisdictions · filing window Apr 25, 2024 → Jul 26, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 filings

States

5

Affected · reported

2,660

First → last filing

Apr 25, 2024 → Jul 26, 2024

Merge confidence

100%

incident inc_164c15a691f54b06 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Mar 30, 2024–Apr 3, 2024, discovered Apr 3, 2024 — the first regulatory filing landed 42 days later (flagged late). 2,660 individuals reported across the linked filings. Data reported: Government ID, Financial account, Identity (basic), and 1 more. Notifications rolled out on a 91-day schedule across 7 filings beginning Apr 25, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
42days

Discovered → first regulatory filing

Discovery variance
21days

Range of discovered_at dates across filings

Leak precedence
19days 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
91days

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 · 114dLeak gap⏱ Leak >90dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Mar 30, 2024breach begins
Apr 3, 2024discovered · members disagree
notification delay · 42 days
May 15, 2024first filing
Jul 26, 2024most 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. APR 25Leak sitemedusa postfirst filing · attacker claim · unverifiedday 0
  2. MAY 15MA AGMA AG notice31 MA residents+19d
  3. MAY 15IN AGIN AG noticestates nationwide total 2,660+19d
  4. MAY 15ME AGME AG noticestates nationwide total 2,660+19d
  5. MAY 15MT AGMT AG notice18 MT residents+19d
  6. MAY 15NH AGNH AG notice15 NH residents+19d
  7. JUL 26NH AGNH AG noticeno count stated+91d
  8. JUL 26ME AGME AG noticemost recent · states nationwide total 1,137+91d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 30, 2024
IN AG
Discovered
Apr 3, 2024MT AG + NH AG + ME AGApr 24, 2024ME AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PII
MA AG + MT AG + ME AG +1
Attack vector
Unauthorized Access
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)

2,660

Sum of filed state slices

131· 4.9% of stated

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

US2,660
IN52
MA31
MT18
ME15
NH15

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

91 days

Cadence

~1 / 13d

vs. multi-state median

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