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

U.S. 1031 Exchange Services. Inc. — October 2025 breach

Clustered 9 filings across 6 jurisdictions · filing window Apr 23, 2026 → May 11, 2026 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

9 filings

States

6

Affected · reported

2,090

First → last dated filing

Apr 23, 2026 → May 11, 2026

Merge confidence

100%

incident inc_1d070615b1ea4b17 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. The filings describe unauthorized access. Intrusion Oct 6, 2025, discovered Oct 16, 2025 — the first regulatory filing landed 189 days later. 2,090 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 1 more. Notifications rolled out on a 18-day schedule across 8 dated filings beginning Apr 23, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
189days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
18days

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 · 189dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Oct 6, 2025breach begins
Oct 16, 2025discovered
notification delay · 189 days
Apr 23, 2026first dated filing
May 11, 2026most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing about this breach

  1. APR 23ME AGME AG noticefirst filing · states nationwide total 882day 0
  2. APR 23MA AGMA AG notice50 MA residentsday 0
  3. APR 23NE AGNE AG noticefiling day not on record · states nationwide total 882—
  4. APR 23NH AGNH AG noticestates nationwide total 882day 0
  5. APR 23IN AGIN AG noticestates nationwide total 882day 0
  6. APR 23IN AGIN AG noticestates nationwide total 1,290day 0
  7. MAY 8NH AGNH AG noticestates nationwide total 1,208+15d
  8. MAY 8ME AGME AG noticestates nationwide total 2,090+15d
  9. MAY 11VT AGVT AG noticemost recent · 4 VT residents+18d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 6, 2025
ME AG
Discovered
Oct 16, 2025· 10d undetected
ME AG + NE AG + NH AG
Data types
Financial account · Identity (basic) · Government ID · PCI
ME AG + MA AG + NE 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)

2,090

Sum of filed state slices

86· 4.1% of stated

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

US2,090
MA50
IN20
ME5
NH5
VT4
NE2

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

18 days

Cadence

~1 / 2.6d

vs. multi-state median

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