DisclosureLens
Leak SiteState AGConfirmed13 filings · 11 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedakirahigh sensitivity
Merged incident · 13 filings

Wakefield Terrace Associates Limited Partnership — January 2025 breach

Clustered 13 filings across 12 jurisdictions · filing window Nov 30, 2023 Dec 18, 2025. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

13 filings

States

11

Affected · reported

371,577

First → last filing

Nov 30, 2023 Dec 18, 2025

Merge confidence

100%

incident inc_dba969b5b2bc4318 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings and 2 unverified claims. The filings describe unauthorized access. Intrusion Jan 14, 2025–Sep 24, 2025, discovered Jan 17, 2025 — the first regulatory filing landed 288 days later (flagged late). 371,577 individuals reported across the linked filings. Data reported: Government ID, Health (basic), PII, and 2 more. Notifications rolled out on a 749-day schedule across 11 filings beginning Nov 30, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
288days

Discovered → first regulatory filing

Discovery variance
250days

Range of discovered_at dates across filings

Leak precedence
702days 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
749days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delayno SEC 8-K in this cluster.

Regulatory clocksLeak gap Leak >180dOregon OR AG >45dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jan 14, 2025breach begins
Jan 17, 2025discovered · members disagree
notification delay · 288 days
Nov 1, 2025first filing
Dec 18, 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. NOV 30Leak siteakira postfirst filing · attacker claim · unverifiedday 0
  2. JAN 17Leak siteakira postattacker claim · unverified+414d
  3. NOV 1IL AGIL AG noticeno count stated+702d
  4. NOV 7MT AGMT AG notice26,624 MT residents+708d
  5. NOV 7NE AGNE AG notice81 NE residents+708d
  6. NOV 7NH AGNH AG notice40 NH residents+708d
  7. NOV 7MA AGMA AG notice131 MA residents+708d
  8. NOV 7IN AGIN AG noticestates nationwide total 371,577+708d
  9. NOV 7VT AGVT AG noticeno count stated+708d
  10. NOV 7ME AGME AG notice41 affected+708d
  11. NOV 10SC AGSC AG notice18,933 SC residents+711d
  12. NOV 12TX AGTX AG noticestates nationwide total 371,577+713d
  13. DEC 18OR AGOR AG noticemost recent · states nationwide total 371,577+749d
  14. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jan 17, 2025
NE AG
Discovered
Jan 17, 2025MT AG + NE AG + NH AG +2Sep 24, 2025IL AG + ME AG + TX AGfilings disagree on discovery
Data types
Health (basic) · Identity (basic) · Government ID · PHI · PII
IL AG + NE AG + NH AG +6
Attack vector
Unauthorized Access
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)

371,577

Sum of filed state slices

48,262· 13.0% of stated

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

US371,577
MT26,624
SC18,933
TX2,286
MA131
IN126
NE81
ME41
NH40

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 claim2 members

Attacker assertion only. Establishes: claim date, group, alleged victim.

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

749 days

Cadence

~1 / 62.4d

vs. multi-state median

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