DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
State AGConfirmed16 filings · 7 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 16 filings

The Northwestern Mutual Life Insurance Company — October 2023 breach

Clustered 16 filings across 7 jurisdictions · filing window Feb 7, 2024 → Mar 8, 2024 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

16 filings

States

7

Affected · reported

62,656

First → last dated filing

Feb 7, 2024 → Mar 8, 2024

Merge confidence

100%

incident inc_6b5fb591615b4b4a · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 16 regulatory filings. Intrusion Oct 29, 2023–Nov 2, 2023, discovered Mar 1, 2023. 62,656 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and PII. Notifications rolled out on a 30-day schedule across 14 dated filings beginning Feb 7, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
341days

Range of discovered_at dates across filings

Filing span
30days

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 · 14dOregon✓ OR AG ≤45dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Oct 29, 2023breach begins
Mar 1, 2023discovered · members disagree
Feb 7, 2024first dated filing
Mar 8, 2024most 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

  1. FEB 1IL AGIL AG noticefiling day not on record · no count stated—
  2. FEB 1IL AGIL AG noticefiling day not on record · no count stated—
  3. FEB 7MA AGMA AG noticefirst filing · 31 MA residentsday 0
  4. FEB 7MT AGMT AG notice1 MT residentsday 0
  5. FEB 7IN AGIN AG noticestates nationwide total 887day 0
  6. FEB 7ME AGME AG noticestates nationwide total 887day 0
  7. FEB 16IN AGIN AG noticestates nationwide total 24,518+9d
  8. FEB 16ME AGME AG noticestates nationwide total 24,518+9d
  9. FEB 16MT AGMT AG notice103 MT residents+9d
  10. FEB 16MA AGMA AG notice475 MA residents+9d
  11. FEB 29MT AGMT AG notice389 MT residents+22d
  12. FEB 29ME AGME AG noticestates nationwide total 62,656+22d
  13. FEB 29OR AGOR AG noticestates nationwide total 62,656+22d
  14. FEB 29MA AGMA AG notice1,289 MA residents+22d
  15. MAR 1IN AGIN AG noticestates nationwide total 62,656+23d
  16. MAR 8NH AGNH AG noticemost recent · 344 NH residents+30d
  17. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 29, 2023
IN AG
Discovered
Mar 1, 2023IL AGNov 2, 2023MT AG + NH AGJan 24, 2024ME AGJan 29, 2024IL AG + ME AGFeb 5, 2024ME AG + OR AGfilings disagree on discovery
Data types
Identity (basic) · Government ID · PII
MT AG + NH AG
Attack vector
Third-Party / Supply Chain
MT 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)

62,656

Sum of filed state slices

3,735· 6.0% of stated

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

US62,656
IN1,397
MA1,289
MT389
NH344
ME316

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

30 days

Cadence

~1 / 2.3d

vs. multi-state median

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