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

The UPS Store, Inc. — September 2019 breach

Clustered 11 filings across 6 jurisdictions · filing window Nov 26, 2019 → Jan 24, 2020. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

6

Affected · reported

17,094

First → last filing

Nov 26, 2019 → Jan 24, 2020

Merge confidence

100%

incident inc_b3a728feda3f4e14 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. The filings describe a phishing attack. Intrusion Sep 29, 2019–Jan 13, 2020, discovered Oct 18, 2019 — the first regulatory filing landed 39 days later. 17,094 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 5 more. Notifications rolled out on a 59-day schedule across 11 filings beginning Nov 26, 2019. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
39days

Discovered → first regulatory filing

Discovery variance
66days

Range of discovered_at dates across filings

Filing span
59days

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 clocksMassachusetts✓ MA credit monitoring dueCalifornia✓ CA 60-day OK · 29dFull clock table in Litigation Timeline

Sensitive data

authenticationidentity_government

Incident timeline

Sep 29, 2019breach begins
Oct 18, 2019discovered · members disagree
notification delay · 39 days
Nov 26, 2019first filing
Jan 24, 2020most 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. NOV 26WA AGWA AG noticefirst filing · 506 WA residentsday 0
  2. NOV 27MA AGMA AG notice87 MA residents+1d
  3. NOV 27MT AGMT AG notice2 MT residents+1d
  4. NOV 27CA AGCA AG noticeno count stated+1d
  5. DEC 2NH AGNH AG notice3 NH residents+6d
  6. JAN 20WA AGWA AG notice963 WA residents+55d
  7. JAN 20MA AGMA AG notice115 MA residents+55d
  8. JAN 20CA AGCA AG noticeno count stated+55d
  9. JAN 20MT AGMT AG notice70 MT residents+55d
  10. JAN 21IN AGIN AG noticestates nationwide total 17,094+56d
  11. JAN 24NH AGNH AG noticemost recent · 13 NH residents+59d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 11, 2019 – Oct 22, 2019
WA AG
Discovered
Oct 18, 2019WA AGOct 22, 2019NH AGNov 1, 2019MT AGDec 18, 2019WA AGDec 23, 2019CA AG + MT AG + NH AGfilings disagree on discovery
Data types
Authentication · Financial account · Health (basic) · Identity (basic) · Government ID · PCI · PHI · PII
WA AG + MT AG + CA AG +2
Attack vector
Phishing
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)

17,094

Sum of filed state slices

1,461· 8.5% of stated

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

US17,094
WA963
IN300
MA115
MT70
NH13

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

59 days

Cadence

~1 / 5.9d

vs. multi-state median

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