DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteState AGConfirmed8 filings · 7 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedworldleakshigh sensitivity
Merged incident · 8 filings

Washington Prime Group Inc — July 2025 breach

Clustered 8 filings across 8 jurisdictions · filing window Aug 8, 2025 → Mar 9, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 filings

States

7

Affected · reported

7,497

First → last filing

Aug 8, 2025 → Mar 9, 2026

Merge confidence

100%

incident inc_0ea666fc551c411b · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Jul 30, 2025–Aug 9, 2025, discovered Aug 11, 2025 — the first regulatory filing landed 134 days later (flagged late). 7,497 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and Financial account. Notifications rolled out on a 213-day schedule across 7 filings beginning Aug 8, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
134days

Discovered → first regulatory filing

Discovery variance
105days

Range of discovered_at dates across filings

Leak precedence
137days 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
213days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksVermont✗ VT AG >45 bdayTexas✗ TX AG >30dLeak gap⏱ Leak >90dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jul 30, 2025breach begins
Aug 11, 2025discovered · members disagree
notification delay · 134 days
Dec 23, 2025first filing
Mar 9, 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. AUG 8Leak siteworldleaks postfirst filing · attacker claim · unverifiedday 0
  2. DEC 23IN AGIN AG noticestates nationwide total 7,322+137d
  3. DEC 23MT AGMT AG notice44 MT residents+137d
  4. DEC 23NH AGNH AG notice2 NH residents+137d
  5. DEC 23VT AGVT AG noticeno count stated+137d
  6. DEC 23MA AGMA AG notice6 MA residents+137d
  7. DEC 23NE AGNE AG notice39 NE residents+137d
  8. MAR 9TX AGTX AG noticemost recent · states nationwide total 7,497+213d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jul 30, 2025
IN AG
Discovered
Aug 11, 2025MT AG + NH AG + VT AG +1Nov 24, 2025TX AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID
MT AG + NH AG + VT AG +3
Attack vector
Unauthorized Access
MT 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)

7,497

Sum of filed state slices

780· 10.4% of stated

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

US7,497
TX508
IN181
MT44
NE39
MA6
NH2

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 filing7 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 Aug 23, 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

213 days

Cadence

~1 / 30.4d

vs. multi-state median

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