DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteState AGConfirmed16 filings · 15 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedbrotherhoodhigh sensitivity
Merged incident · 16 filings

Motility Software Solutions, Inc. — August 2025 breach

Clustered 16 filings across 16 jurisdictions · filing window Sep 1, 2025 → Oct 10, 2025. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

16 filings

States

15

Affected · reported

766,670

First → last filing

Sep 1, 2025 → Oct 10, 2025

Merge confidence

100%

incident inc_4c46e8b6fe2d409b · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 15 regulatory filings and 1 unverified claim. The filings describe malware. Intrusion Aug 11, 2025–Aug 19, 2025, discovered Aug 19, 2025 — the first regulatory filing landed 13 days later. 766,670 individuals reported across the linked filings. Data reported: Government ID and Identity (basic). Notifications rolled out on a 39-day schedule across 15 filings beginning Sep 1, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
13days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
Noneclaim trailed by 40d

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

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 >30d · 42dWashington⏱ WA AG >30dVermont⏱ VT AG >14 bdayIowa✓ IA AG ≤5 bdaySouth Carolina✓ SC CRA notice dueMassachusetts✓ MA credit monitoring dueOregon✓ OR AG ≤45dTexas✓ TX CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 11, 2025breach begins
Aug 19, 2025discovered
notification delay · 13 days
Sep 1, 2025first filing
Oct 1, 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. SEP 1IL AGIL AG noticefirst filing · no count statedday 0
  2. SEP 29IN AGIN AG noticestates nationwide total 766,000+28d
  3. SEP 29CA AGCA AG noticeno count stated+28d
  4. SEP 29NE AGNE AG noticeno count stated+28d
  5. SEP 29MT AGMT AG notice1,071 MT residents+28d
  6. SEP 29NH AGNH AG notice17,068 NH residents+28d
  7. SEP 29DE AGDE AG noticeno count stated+28d
  8. SEP 29IA AGIA AG notice4,145 IA residents+28d
  9. SEP 30SC AGSC AG notice13,430 SC residents+29d
  10. SEP 30ME AGME AG noticestates nationwide total 766,670+29d
  11. SEP 30WA AGWA AG notice8,349 WA residents+29d
  12. SEP 30MA AGMA AG notice18,050 MA residents+29d
  13. SEP 30OR AGOR AG noticestates nationwide total 766,670+29d
  14. SEP 30VT AGVT AG noticeno count stated+29d
  15. OCT 1TX AGTX AG noticestates nationwide total 766,670+30d
  16. OCT 10Leak sitebrotherhood postmost recent · attacker claim · unverified+40d
  17. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 11, 2025
IN AG
Discovered
Aug 19, 2025· 8d undetected
IL AG + CA AG + NE AG +10
Data types
Identity (basic) · Government ID
IL AG + CA AG + NE AG +10
Attack vector
Ransomware
CA 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)

766,670

Sum of filed state slices

283,187· 36.9% of stated

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

US766,670
TX194,644
ME18,270
MA18,050
NH17,068
SC13,430
WA8,349
IN8,160
IA4,145
MT1,071

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

39 days

Cadence

~1 / 2.6d

vs. multi-state median

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