DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed17 filings · 12 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedcritical sensitivity
Merged incident · 17 filings

SITUSAMC HOLDINGS CORPORATION — November 2025 breach

Clustered 17 filings across 12 jurisdictions · filing window Jan 1, 2026 → Apr 6, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

17 filings

States

12

Affected · reported

662,701

First → last filing

Jan 1, 2026 → Apr 6, 2026

Merge confidence

100%

incident inc_2c0687192d394525 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 17 regulatory filings. The filings describe unauthorized access. Intrusion Nov 12, 2025–Nov 21, 2025, discovered Nov 12, 2025 — the first regulatory filing landed 50 days later (flagged late). 662,701 individuals reported across the linked filings. Data reported: Government ID, Minor, Financial account, and 3 more. Notifications rolled out on a 95-day schedule across 17 filings beginning Jan 1, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
50days

Discovered → first regulatory filing

Discovery variance
139days

Range of discovered_at dates across filings

Filing span
95days

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 clocksVermont✗ VT AG >45 bdayOregon✗ OR AG >45dWashington✗ WA AG >90dCalifornia✗ CA 60-day late · 142dMassachusetts⏱ MA AG >30dMaine✓ ME AG ≤30d · 29dTexas✓ TX AG ≤30dFull clock table in Litigation Timeline

Sensitive data

identity_governmentminor

Incident timeline

Nov 12, 2025breach begins
Nov 12, 2025discovered · members disagree
notification delay · 50 days
Jan 1, 2026first filing
Apr 6, 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. JAN 1IL AGIL AG noticefirst filing · no count statedday 0
  2. JAN 28VT AGVT AG noticeno count stated+27d
  3. JAN 28NE AGNE AG noticeno count stated+27d
  4. JAN 28MA AGMA AG notice11,444 MA residents+27d
  5. JAN 28CA AGCA AG noticeno count stated+27d
  6. FEB 20OR AGOR AG noticestates nationwide total 250+50d
  7. FEB 20CA AGCA AG noticeno count stated+50d
  8. FEB 20WA AGWA AG notice20,456 WA residents+50d
  9. MAR 10IN AGIN AG notice263 IN residents+68d
  10. MAR 10CA AGCA AG noticeno count stated+68d
  11. MAR 10IN AGIN AG notice263 IN residents+68d
  12. MAR 10MT AGMT AG notice1,340 MT residents+68d
  13. MAR 23OR AGOR AG noticestates nationwide total 658,333+81d
  14. APR 3CA AGCA AG noticeno count stated+92d
  15. APR 3ME AGME AG notice40 ME residents+92d
  16. APR 6NH AGNH AG notice51 NH residents+95d
  17. APR 6TX AGTX AG noticemost recent · states nationwide total 662,701+95d
  18. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 12, 2025 – Nov 19, 2025
VT AG
Discovered
Nov 12, 2025VT AG + NE AG + MA AG +5Feb 17, 2026OR AGMar 5, 2026ME AGMar 31, 2026IL AG + TX AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · Minor · PHI
IL AG + CA AG + WA AG +7
Attack vector
Unauthorized Access
VT 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)

662,701

Sum of filed state slices

70,421· 10.6% of stated

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

US662,701
TX36,827
WA20,456
MA11,444
MT1,340
IN263
NH51
ME40

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

95 days

Cadence

~1 / 5.9d

vs. multi-state median

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