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

Marquis Software Solutions, Inc. — August 2025 breach

Clustered 20 filings across 12 jurisdictions · filing window Nov 26, 2025 → Mar 23, 2026. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

20 filings

States

12

Affected · reported

not comparable

First → last filing

Nov 26, 2025 → Mar 23, 2026

Merge confidence

100%

incident inc_f895dc3732284236 · merged by human · confidence 100%

Part of the Marquis Software Solutions, Inc. supply-chain incident (2025) — at least 3 organizations filed notifications naming this third party.
Confirmed breach. Merged as one breach: 20 regulatory filings. Intrusion Aug 14, 2025–Sep 4, 2025, discovered Aug 14, 2025 — the first regulatory filing landed 104 days later (flagged late). Data reported: Government ID, Identity (basic), Financial account, and 1 more. Notifications rolled out on a 117-day schedule across 20 filings beginning Nov 26, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
104days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
117days

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 bdayWashington✗ WA AG >90dTexas✗ TX AG >30dMaine✗ ME AG >90d · 110dOregon✗ OR AG >45dIowa✓ IA AG ≤5 bdaySouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 14, 2025breach begins
Aug 14, 2025discovered
notification delay · 104 days
Nov 26, 2025first filing
Mar 23, 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. NOV 26VT AGVT AG noticefirst filing · no count statedday 0
  2. NOV 26WA AGWA AG notice269,773 WA residentsday 0
  3. NOV 26DE AGDE AG noticeno count statedday 0
  4. NOV 26IA AGIA AG notice10,720 IA residentsday 0
  5. NOV 26IN AGIN AG notice34,805 IN residentsday 0
  6. NOV 26MT AGMT AG notice49,948 MT residentsday 0
  7. NOV 26NH AGNH AG notice22 NH residentsday 0
  8. NOV 30SC AGSC AG notice223,447 SC residents+4d
  9. DEC 1NH AGNH AG notice62,000 NH residents+5d
  10. DEC 2TX AGTX AG notice354,289 TX residents+6d
  11. DEC 2CA AGCA AG noticeno count stated+6d
  12. DEC 2ME AGME AG notice42,784 ME residents+6d
  13. DEC 15OR AGOR AG noticestates nationwide total 13,169+19d
  14. DEC 26NH AGNH AG notice4 NH residents+30d
  15. FEB 11NH AGNH AG notice72 NH residents+77d
  16. FEB 11CA AGCA AG noticeno count stated+77d
  17. MAR 16CA AGCA AG noticeno count stated+110d
  18. MAR 16VT AGVT AG noticeno count stated+110d
  19. MAR 17ME AGME AG noticestates nationwide total 672,075+111d
  20. MAR 23NH AGNH AG noticemost recent · 83 NH residents+117d
  21. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 14, 2025 – Sep 4, 2025
WA AG
Discovered
Aug 14, 2025
VT AG + WA AG + DE AG +8
Data types
Financial account · Identity (basic) · Government ID · PII
VT AG + WA AG + DE 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.

Affected residents by state

per-state reported counts

US672,075
TX354,289
WA269,773
SC223,447
NH62,000
MT49,948
ME42,784
IN34,805
IA10,720

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 filing20 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 10, 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

117 days

Cadence

~1 / 6.2d

vs. multi-state median

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