All incidents View linkage analytics →Get the evidence package — $7.99 what’s inside →

Confirmed11 filings · 8 statesUnverified claimConfirmedEnforcedhigh sensitivity

Merged incident · 11 filings

Graebel Companies, Inc. — December 2024 breach

Clustered 11 filings across 8 jurisdictions · filing window Nov 10, 2025 → Apr 3, 2026 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

Affected · reported

5,573

First → last dated filing

Nov 10, 2025 → Apr 3, 2026

Merge confidence

100%

incident inc_ba014e6df3594d39 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. The filings describe unauthorized access. Intrusion Dec 19, 2024–Dec 22, 2024, discovered Dec 19, 2024 — the first regulatory filing landed 326 days later. 5,573 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 3 more. Notifications rolled out on a 144-day schedule across 10 dated filings beginning Nov 10, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

326days

Discovered → first regulatory filing

Discovery variance

309days

Range of discovered_at dates across filings

Filing span

144days

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 clocksMaine⏱ ME AG >30d · 161dMassachusetts✓ MA credit monitoring dueTexas✓ TX AG ≤30dFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Dec 19, 2024breach begins

Dec 19, 2024discovered · members disagree

notification delay · 326 days

Nov 10, 2025first dated filing

Apr 3, 2026most recent dated filing

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

NOV 10ME AGME AG noticefirst filing · 15 ME residentsday 0
NOV 10NH AGNH AG notice18 NH residentsauto-linkedday 0
NOV 10IN AGIN AG noticestates nationwide total 5,573auto-linkedday 0
NOV 10VT AGVT AG noticeno count statedauto-linkedday 0
NOV 10MA AGMA AG notice92 MA residentsauto-linkedday 0
NOV 10NE AGNE AG noticefiling day not on record · 25 NE residentsauto-linked—
NOV 10MT AGMT AG notice11 MT residentsday 0
NOV 12TX AGTX AG noticestates nationwide total 5,573operator-confirmed+2d
APR 3ME AGME AG notice17 ME residentsauto-linked+144d
APR 3NH AGNH AG notice12 NH residentsauto-linked+144d
APR 3VT AGVT AG noticemost recent · 4 VT residentsauto-linked+144d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Dec 19, 2024 – Dec 22, 2024
Discovered: Dec 19, 2024NE AGDec 22, 2024NH AGOct 13, 2025TX AGOct 24, 2025ME AGfilings disagree on discovery
Data types: Employment · Financial account · Financial credentials · Identity (basic) · Government ID · PII
Attack vector: Unauthorized Access

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)

5,573

Sum of filed state slices

523· 9.4% of stated

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

US5,573

TX267

MA92

IN89

NE25

NH18

ME17

MT11

VT4

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

144 days

Cadence

~1 / 16d

vs. multi-state median

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