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

North Atlantic States Carpenters Benefit Funds — August 2025 breach

Clustered 8 filings across 8 jurisdictions · filing window Feb 1, 2026 → Feb 13, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 filings

States

8

Affected · reported

110,435

First → last filing

Feb 1, 2026 → Feb 13, 2026

Merge confidence

100%

incident inc_c6b7dc81d05d4114 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings. The filings describe unauthorized access. Intrusion Aug 18, 2025, discovered Aug 18, 2025 — the first regulatory filing landed 167 days later (flagged late). 110,435 individuals reported across the linked filings. Data reported: Government ID, Financial account, Health (basic), and 3 more. Notifications rolled out on a 12-day schedule across 8 filings beginning Feb 1, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
167days

Discovered → first regulatory filing

Discovery variance
148days

Range of discovered_at dates across filings

Filing span
12days

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 clocksVermont✗ VT AG >45 bdayMaine✓ ME AG ≤30d · 29dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 18, 2025breach begins
Aug 18, 2025discovered · members disagree
notification delay · 167 days
Feb 1, 2026first filing
Feb 13, 2026most 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. FEB 1IL AGIL AG noticefirst filing · no count statedday 0
  2. FEB 11NH AGNH AG notice7,444 NH residents+10d
  3. FEB 11MA AGMA AG noticeno count stated+10d
  4. FEB 11ME AGME AG notice2,063 ME residents+10d
  5. FEB 11IN AGIN AG noticestates nationwide total 110,435+10d
  6. FEB 11NE AGNE AG notice26 NE residents+10d
  7. FEB 11VT AGVT AG noticeno count stated+10d
  8. FEB 13TX AGTX AG noticemost recent · states nationwide total 110,435+12d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 18, 2025
NH AG
Discovered
Aug 18, 2025NH AG + NE AG + VT AGJan 13, 2026IL AG + ME AG + TX AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
IL AG + NH AG + MA AG +4
Attack vector
Unauthorized Access
NH 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)

110,435

Sum of filed state slices

10,249· 9.3% of stated

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

US110,435
NH7,444
ME2,063
TX567
IN149
NE26

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

12 days

Cadence

~1 / 1.7d

vs. multi-state median

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