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

Retail Merchandising Services — November 2025 breach

Clustered 10 filings across 9 jurisdictions · filing window Mar 1, 2026 → Mar 17, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

9

Affected · reported

16,114

First → last filing

Mar 1, 2026 → Mar 17, 2026

Merge confidence

100%

incident inc_9d766a89006d4128 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. The filings describe unauthorized access. Intrusion Nov 24, 2025–Jan 7, 2026, discovered Jan 1, 2026 — the first regulatory filing landed 59 days later. 16,114 individuals reported across the linked filings. Data reported: Government ID, Financial account, Identity (basic), and 2 more. Notifications rolled out on a 16-day schedule across 10 filings beginning Mar 1, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
59days

Discovered → first regulatory filing

Discovery variance
55days

Range of discovered_at dates across filings

Filing span
16days

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 clocksMaine✓ ME AG ≤30d · 19dTexas✓ TX AG ≤30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Nov 24, 2025breach begins
Jan 1, 2026discovered · members disagree
notification delay · 59 days
Mar 1, 2026first filing
Mar 17, 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. MAR 1IL AGIL AG noticefirst filing · no count statedday 0
  2. MAR 16NE AGNE AG notice167 NE residents+15d
  3. MAR 16MA AGMA AG noticeno count stated+15d
  4. MAR 16IN AGIN AG noticestates nationwide total 16,114+15d
  5. MAR 16CA AGCA AG noticeno count stated+15d
  6. MAR 16VT AGVT AG noticeno count stated+15d
  7. MAR 16NH AGNH AG notice59 NH residents+15d
  8. MAR 16ME AGME AG noticestates nationwide total 16,114+15d
  9. MAR 16IN AGIN AG noticestates nationwide total 16,114+15d
  10. MAR 17TX AGTX AG noticemost recent · states nationwide total 16,114+16d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 24, 2025 – Jan 7, 2026
NE AG
Discovered
Jan 1, 2026NE AG + NH AGFeb 25, 2026IL AG + ME AG + TX AGfilings disagree on discovery
Data types
Financial · Financial account · Identity (basic) · Government ID · PII
IL AG + NE AG + VT AG +5
Attack vector
Unauthorized Access
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)

16,114

Sum of filed state slices

2,000· 12.4% of stated

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

US16,114
TX1,386
IN334
NE167
NH59
ME54

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

16 days

Cadence

~1 / 1.8d

vs. multi-state median

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