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

Outdoor Smart! Inc — February 2024 breach

Clustered 9 filings across 9 jurisdictions · filing window Dec 19, 2025 → Jan 7, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

9

Affected · reported

19,864

First → last filing

Dec 19, 2025 → Jan 7, 2026

Merge confidence

100%

incident inc_e15efa85ca94427c · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. Intrusion Feb 15, 2024–Nov 4, 2025, discovered Nov 3, 2025 — the first regulatory filing landed 46 days later. 19,864 individuals reported across the linked filings. Data reported: Identity (basic), Financial account, PII, and 2 more. Notifications rolled out on a 19-day schedule across 9 filings beginning Dec 19, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
46days

Discovered → first regulatory filing

Discovery variance
31days

Range of discovered_at dates across filings

Filing span
19days

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 >30dVermont⏱ VT AG >14 bdayMaine✓ ME AG ≤30d · 15dCalifornia✓ CA 60-day OK · 31dFull clock table in Litigation Timeline

Sensitive data

financial_credentials

Incident timeline

Feb 15, 2024breach begins
Nov 3, 2025discovered · members disagree
notification delay · 46 days
Dec 19, 2025first filing
Jan 7, 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. DEC 19NE AGNE AG noticefirst filing · 2 NE residentsday 0
  2. DEC 19WA AGWA AG notice652 WA residentsday 0
  3. DEC 19MA AGMA AG notice32 MA residentsday 0
  4. DEC 19ME AGME AG noticestates nationwide total 19,864day 0
  5. DEC 19VT AGVT AG noticeno count statedday 0
  6. DEC 19IN AGIN AG noticestates nationwide total 19,864day 0
  7. DEC 19CA AGCA AG noticeno count statedday 0
  8. DEC 22NH AGNH AG notice31 NH residents+3d
  9. JAN 7TX AGTX AG noticemost recent · states nationwide total 19,864+19d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 15, 2024 – Nov 4, 2025
NE AG
Discovered
Nov 3, 2025NE AG + WA AG + VT AG +2Dec 4, 2025ME AG + TX AGfilings disagree on discovery
Data types
Financial account · Financial credentials · Identity (basic) · PCI · PII
NE AG + WA AG + VT AG +5
Attack vector
Misconfiguration
NE 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)

19,864

Sum of filed state slices

2,140· 10.8% of stated

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

US19,864
TX1,363
WA652
IN54
MA32
NH31
ME6
NE2

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

19 days

Cadence

~1 / 2.4d

vs. multi-state median

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