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

Special Buys Clothing Inc. — September 2022 breach

Clustered 9 filings across 6 jurisdictions · filing window Dec 9, 2022 → Jan 30, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

6

Affected · reported

12,270

First → last filing

Dec 9, 2022 → Jan 30, 2023

Merge confidence

100%

incident inc_adf43ecf3b7e47dc · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. The filings describe unauthorized access. Intrusion Sep 27, 2022–Dec 28, 2022, discovered Oct 1, 2022 — the first regulatory filing landed 69 days later (flagged late). 12,270 individuals reported across the linked filings. Data reported: PCI, Financial account, PII, and 3 more. Notifications rolled out on a 52-day schedule across 9 filings beginning Dec 9, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
69days

Discovered → first regulatory filing

Discovery variance
37days

Range of discovered_at dates across filings

Filing span
52days

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 late · 75dMaine⏱ ME AG >30d · 32dFull clock table in Litigation Timeline

Sensitive data

financial_credentials

Incident timeline

Sep 27, 2022breach begins
Oct 1, 2022discovered · members disagree
notification delay · 69 days
Dec 9, 2022first filing
Jan 30, 2023most 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 9MA AGMA AG noticefirst filing · 90 MA residentsday 0
  2. DEC 9ME AGME AG noticestates nationwide total 7,000day 0
  3. DEC 9CA AGCA AG noticeno count statedday 0
  4. DEC 12NH AGNH AG notice15 NH residents+3d
  5. DEC 12IN AGIN AG noticestates nationwide total 7,000+3d
  6. DEC 13MT AGMT AG notice15 MT residents+4d
  7. JAN 19CA AGCA AG noticeno count stated+41d
  8. JAN 20ME AGME AG noticestates nationwide total 12,270+42d
  9. JAN 30NH AGNH AG noticemost recent · 24 NH residents+52d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Sep 27, 2022 – Nov 7, 2022
ME AG
Discovered
Oct 1, 2022CA AG + MT AGNov 7, 2022ME AG + NH AGfilings disagree on discovery
Data types
Credentials · Financial account · Financial credentials · Identity (basic) · PCI · PII
MA AG + MT AG + ME AG +2
Attack vector
Unauthorized Access
ME 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)

12,270

Sum of filed state slices

221· 1.8% of stated

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

US12,270
MA90
IN76
NH24
ME16
MT15

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

52 days

Cadence

~1 / 6.5d

vs. multi-state median

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