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

Strategic Retail Partners (SRP) — February 2025 breach

Clustered 9 filings across 7 jurisdictions · filing window Feb 6, 2025 → Oct 9, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

6

Affected · reported

4,097

First → last filing

Feb 6, 2025 → Oct 9, 2025

Merge confidence

100%

incident inc_db64458b52074e3e · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings and 3 unverified claims. The filings describe unauthorized access. Intrusion Feb 3, 2025–Feb 6, 2025, discovered Feb 6, 2025 — the first regulatory filing landed 244 days later (flagged late). 4,097 individuals reported across the linked filings. Data reported: Government ID, Minor, Identity (basic), and 4 more. Notifications rolled out on a 245-day schedule across 6 filings beginning Feb 6, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
244days

Discovered → first regulatory filing

Discovery variance
188days

Range of discovered_at dates across filings

Leak precedence
244days before filing

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
245days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksMaine✗ ME AG >90d · 244dVermont✗ VT AG >45 bdayLeak gap✗ Leak >180dFull clock table in Litigation Timeline

Sensitive data

identity_governmentminor

Incident timeline

Feb 3, 2025breach begins
Feb 6, 2025discovered · members disagree
notification delay · 244 days
Oct 8, 2025first filing
Oct 9, 2025most 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. FEB 6Leak sitemedusa postfirst filing · attacker claim · unverifiedday 0
  2. FEB 6Leak sitemedusa postattacker claim · unverifiedday 0
  3. FEB 11Leak sitemedusa postattacker claim · unverified+6d
  4. OCT 8ME AGME AG notice17 ME residents+244d
  5. OCT 8VT AGVT AG noticeno count stated+244d
  6. OCT 8IN AGIN AG noticestates nationwide total 4,097+244d
  7. OCT 8MA AGMA AG notice25 MA residents+244d
  8. OCT 8NH AGNH AG notice6 NH residents+244d
  9. OCT 9TX AGTX AG noticemost recent · states nationwide total 4,097+245d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 3, 2025 – Feb 6, 2025
ME AG
Discovered
Feb 6, 2025ME AG + VT AG + NH AGAug 13, 2025TX AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · Minor · PHI · PII
ME AG + VT AG + NH 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)

4,097

Sum of filed state slices

384· 9.4% of stated

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

US4,097
TX271
IN65
MA25
ME17
NH6

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 claim3 members

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

Press / market report

No press coverage linked yet.

State AG / regulator filing6 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 26, 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

245 days

Cadence

~1 / 30.6d

vs. multi-state median

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