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

Nuna Baby Essentials, Inc. — September 2024 breach

Clustered 12 filings across 12 jurisdictions · filing window Feb 1, 2025 → Feb 21, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

12 filings

States

12

Affected · reported

16,676

First → last filing

Feb 1, 2025 → Feb 21, 2025

Merge confidence

100%

incident inc_fa691a2d86014e95 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 12 regulatory filings. The filings describe unauthorized access. Intrusion Sep 8, 2024–Dec 6, 2024, discovered Dec 6, 2024 — the first regulatory filing landed 57 days later (flagged late). 16,676 individuals reported across the linked filings. Data reported: Identity (basic), Financial account, Financial credentials, and 2 more. Notifications rolled out on a 20-day schedule across 12 filings beginning Feb 1, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
57days

Discovered → first regulatory filing

Discovery variance
59days

Range of discovered_at dates across filings

Filing span
20days

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 bdayWashington⏱ WA AG >30dMaryland⏱ MD AG >30dOregon✓ OR AG ≤45dMaine✓ ME AG ≤30d · 18dFull clock table in Litigation Timeline

Sensitive data

authenticationfinancial_credentials

Incident timeline

Sep 8, 2024breach begins
Dec 6, 2024discovered · members disagree
notification delay · 57 days
Feb 1, 2025first filing
Feb 21, 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. FEB 1IL AGIL AG noticefirst filing · no count statedday 0
  2. FEB 21WA AGWA AG notice681 WA residents+20d
  3. FEB 21MD AGMD AG notice269 MD residents+20d
  4. FEB 21NH AGNH AG notice103 NH residents+20d
  5. FEB 21IN AGIN AG noticestates nationwide total 16,676+20d
  6. FEB 21VT AGVT AG noticeno count stated+20d
  7. FEB 21MA AGMA AG notice483 MA residents+20d
  8. FEB 21OR AGOR AG noticestates nationwide total 16,676+20d
  9. FEB 21CA AGCA AG noticeno count stated+20d
  10. FEB 21NE AGNE AG notice66 NE residents+20d
  11. FEB 21MT AGMT AG notice63 MT residents+20d
  12. FEB 21ME AGME AG noticemost recent · states nationwide total 16,676+20d
  13. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Sep 8, 2024 – Dec 6, 2024
WA AG
Discovered
Dec 6, 2024IL AG + WA AG + MD AG +5Feb 3, 2025OR AG + ME AGfilings disagree on discovery
Data types
Authentication · Financial account · Financial credentials · Identity (basic) · PCI
WA AG + MD AG + NH AG +6
Attack vector
Unauthorized Access
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)

16,676

Sum of filed state slices

1,945· 11.7% of stated

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

US16,676
WA681
MA483
MD269
IN207
NH103
ME73
NE66
MT63

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

20 days

Cadence

~1 / 1.8d

vs. multi-state median

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