DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed13 filings · 10 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 13 filings

Nth Degree Investment Group — December 2024 breach

Clustered 13 filings across 10 jurisdictions · filing window Apr 1, 2025 → Jul 1, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

13 filings

States

10

Affected · reported

39,169

First → last filing

Apr 1, 2025 → Jul 1, 2025

Merge confidence

100%

incident inc_04454b06cf1442e7 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 13 regulatory filings. Intrusion Dec 12, 2024–Dec 20, 2024, discovered Dec 20, 2024 — the first regulatory filing landed 102 days later (flagged late). 39,169 individuals reported across the linked filings. Data reported: Government ID, Financial account, Health (basic), and 3 more. Notifications rolled out on a 91-day schedule across 13 filings beginning Apr 1, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
102days

Discovered → first regulatory filing

Discovery variance
145days

Range of discovered_at dates across filings

Filing span
91days

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 >90dTexas✗ TX AG >30dMaine✓ ME AG ≤30d · 24dMassachusetts✓ MA credit monitoring dueDate basis✓ Clock withheld · confirmation dateOregon✓ OR AG ≤45dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 12, 2024breach begins
Dec 20, 2024discovered · members disagree
notification delay · 102 days
Apr 1, 2025first filing
Jul 1, 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. APR 1IL AGIL AG noticefirst filing · no count statedday 0
  2. APR 17ME AGME AG noticestates nationwide total 25,730+16d
  3. APR 17IN AGIN AG noticestates nationwide total 39,169+16d
  4. APR 17NE AGNE AG noticeno count stated+16d
  5. APR 17CA AGCA AG noticeno count stated+16d
  6. APR 17MA AGMA AG notice983 MA residents+16d
  7. APR 17NE AGNE AG noticeno count stated+16d
  8. APR 22NH AGNH AG notice29 NH residents+21d
  9. JUN 25CA AGCA AG noticeno count stated+85d
  10. JUN 25OR AGOR AG noticestates nationwide total 36,169+85d
  11. JUN 25WA AGWA AG notice741 WA residents+85d
  12. JUN 30NH AGNH AG notice6 NH residents+90d
  13. JUL 1TX AGTX AG noticemost recent · states nationwide total 39,169+91d
  14. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 12, 2024 – Dec 20, 2024
ME AG
Discovered
Dec 20, 2024WA AGMar 24, 2025IL AG + ME AG + NH AG +1May 14, 2025NE AG + CA AG + OR AG +1filings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
IL AG + MA AG + WA AG +5
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)

39,169

Sum of filed state slices

5,074· 13.0% of stated

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

US39,169
TX2,655
MA983
WA741
IN653
NH29
ME13

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

91 days

Cadence

~1 / 7.6d

vs. multi-state median

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