DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteHHS OCRState AGConfirmed13 filings · 8 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedcontihigh sensitivity
Merged incident · 13 filings

Shutterfly, Inc. — December 2021 breach

Clustered 13 filings across 9 jurisdictions · filing window Dec 18, 2021 → Jun 6, 2022. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

13 filings

States

8

Affected · reported

52,777

First → last filing

Dec 18, 2021 → Jun 6, 2022

Merge confidence

100%

incident inc_1cb6a4d560c14134 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 12 regulatory filings and 1 unverified claim. Intrusion Dec 3, 2021–Dec 15, 2021, discovered Dec 13, 2021 — the first regulatory filing landed 5 days later (flagged late). 52,777 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 5 more. Notifications rolled out on a 170-day schedule across 12 filings beginning Dec 18, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
5days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
Noneclaim trailed by 28d

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
170days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksLeak gap✗ Leak >180dOregon✗ OR AG >45dMaine✗ ME AG >90d · 172dFull clock table in Litigation Timeline

Sensitive data

authenticationidentity_government

Incident timeline

Dec 3, 2021breach begins
Dec 13, 2021discovered
notification delay · 5 days
Dec 18, 2021first filing
Jun 6, 2022most 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 18IN AGIN AG noticefirst filing · states nationwide total 52,777day 0
  2. JAN 15Leak siteconti postattacker claim · unverified+28d
  3. FEB 22NH AGNH AG notice1 NH residents+66d
  4. FEB 25MA AGMA AG notice678 MA residents+69d
  5. FEB 28NH AGNH AG notice1 NH residents+72d
  6. MAR 22MT AGMT AG notice71 MT residents+94d
  7. MAR 23CA AGCA AG noticeno count stated+95d
  8. MAY 3HHS OCRHHS OCR noticestates nationwide total 2,641+136d
  9. MAY 26WA AGWA AG notice1,273 WA residents+159d
  10. MAY 26OR AGOR AG noticestates nationwide total 52,777+159d
  11. JUN 2CA AGCA AG noticeno count stated+166d
  12. JUN 3ME AGME AG noticestates nationwide total 52,777+167d
  13. JUN 6NH AGNH AG noticemost recent · states nationwide total 159+170d
  14. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 3, 2021
IN AG
Discovered
Dec 13, 2021· 10d undetected
NH AG + MT AG + CA AG +3
Data types
Authentication · Employment · Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
NH AG + MT AG + CA AG +4
Attack vector
Ransomware· Conti
NH 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)

52,777

Sum of filed state slices

3,928· 7.4% of stated

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

US52,777
IN1,678
WA1,273
MA678
NH158
MT71
ME70

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 claim1 member

Attacker assertion only. Establishes: claim date, group, alleged victim.

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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 22, 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

170 days

Cadence

~1 / 14.2d

vs. multi-state median

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