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

The National Wildlife Federation — February 2019 breach

Clustered 10 filings across 10 jurisdictions · filing window Mar 24, 2021 → Mar 29, 2021 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

10

Affected · reported

95,251

First → last dated filing

Mar 24, 2021 → Mar 29, 2021

Merge confidence

100%

incident inc_2cdc894f41b14bce · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. Intrusion Feb 6, 2019–Dec 10, 2020, discovered Dec 4, 2020. 95,251 individuals reported across the linked filings. Data reported: Identity (basic), Financial account, Financial credentials, and 1 more. Notifications rolled out on a 5-day schedule across 9 dated filings beginning Mar 24, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Discovery variance
35days

Range of discovered_at dates across filings

Filing span
5days

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 >90dMaine⏱ ME AG >30d · 75dSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

financial_credentials

Incident timeline

Feb 6, 2019breach begins
Dec 4, 2020discovered · members disagree
Mar 24, 2021first dated filing
Mar 29, 2021most 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. JAN 1IL AGIL AG noticefiling day not on record · no count stated—
  2. MAR 24WA AGWA AG noticefirst filing · 3,311 WA residentsday 0
  3. MAR 24CA AGCA AG noticeno count statedday 0
  4. MAR 24MA AGMA AG notice2,882 MA residentsday 0
  5. MAR 24MT AGMT AG notice518 MT residentsday 0
  6. MAR 24ME AGME AG noticestates nationwide total 95,251day 0
  7. MAR 24IN AGIN AG noticestates nationwide total 95,251day 0
  8. MAR 24OR AGOR AG noticestates nationwide total 95,251day 0
  9. MAR 24SC AGSC AG notice1,255 SC residentsday 0
  10. MAR 29NH AGNH AG noticemost recent · 838 NH residents+5d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 6, 2019 – Dec 10, 2020
WA AG
Discovered
Dec 4, 2020IL AG + WA AG + CA AG +2Jan 8, 2021ME AG + SC AGfilings disagree on discovery
Data types
Financial account · Financial credentials · Identity (basic) · PCI
WA AG + CA AG + MT AG +4
Attack vector
Third-Party / Supply Chain
WA 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)

95,251

Sum of filed state slices

11,626· 12.2% of stated

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

US95,251
WA3,311
MA2,882
IN2,004
SC1,255
NH838
ME818
MT518

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

5 days

Cadence

~1 / 0.6d

vs. multi-state median

1.2× faster

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.