All incidents View linkage analytics →Get the evidence package — $7.99 what’s inside →

Confirmed3 filings · 3 statesUnverified claimConfirmedEnforcedlow sensitivity

Merged incident · 3 filings

VF Outdoor, LLC — account takeover notices

Clustered 3 filings across 3 jurisdictions · filed Nov 5, 2020. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

3 filings

States

Affected · reported

34,582

First → last filing

Nov 5, 2020

Merge confidence

100%

incident inc_1ba1c053a09f4574 · merged by deterministic · confidence 100%

Account takeover notices. VF Outdoor, LLC notified customers of unauthorized access to their accounts. Merged as one incident: 3 regulatory filings. Account access Oct 8, 2020–Oct 9, 2020, discovered Oct 9, 2020 — the first regulatory filing landed 27 days later. 34,582 individuals reported across the linked filings. Data reported: Identity (basic), Credentials, and Behavior. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay

27days

Discovered → first regulatory filing

Discovery variance

0days

Range of discovered_at dates across filings

Filing span

0days

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 clocksCalifornia✓ CA 60-day OK · 27dOregon✓ OR AG ≤45dFull clock table in Litigation Timeline

Incident timeline

Oct 8, 2020account access begins

Oct 9, 2020discovered

notification delay · 27 days

Nov 5, 2020first filing

—watching for filings

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing in this incident

NOV 5CA AGCA AG noticefirst filing · no count statedauto-linkedday 0
NOV 5OR AGOR AG noticestates nationwide total 34,582day 0
NOV 5DE AGDE AG noticemost recent · states nationwide total 34,582auto-linkedday 0
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Account access window: Oct 8, 2020 – Oct 9, 2020
Discovered: Oct 9, 2020· 1d undetected
Data types: Behavior · Credentials · Identity (basic)
Attack vector: Unauthorized Access

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)

34,582

Sum of filed state slices

59· 0.2% of stated

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

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

0 days

Cadence

~1 / 0d

vs. multi-state median

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