DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
HHS OCRState AGConfirmed11 filings · 10 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 11 filings

Trionfo Solutions, LLC — December 2023 breach

Clustered 11 filings across 10 jurisdictions · filed May 22, 2024 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

10

Affected · reported

81,588

First → last dated filing

May 22, 2024

Merge confidence

100%

incident inc_35ce609e6691484e · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. Intrusion Dec 4, 2023–Dec 6, 2023, discovered Dec 4, 2023. 81,588 individuals reported across the linked filings. Data reported: Government ID, PII, Health (basic), and 1 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
29days

Range of discovered_at dates across filings

Filing span
0days

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 clocksWashington✗ WA AG >90dVermont✗ VT AG >45 bdayMaine⏱ ME AG >30d · 141dHIPAA✓ HHS notifiedMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 4, 2023breach begins
Dec 4, 2023discovered · members disagree
May 22, 2024first dated filing
—watching for filings

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. MAY 1IL AGIL AG noticefiling day not on record · no count stated—
  2. MAY 22WA AGWA AG noticefirst filing · 893 WA residentsday 0
  3. MAY 22HHS OCRHHS OCR noticestates nationwide total 81,588day 0
  4. MAY 22OR AGOR AG noticestates nationwide total 65,787day 0
  5. MAY 22ME AGME AG noticestates nationwide total 65,787day 0
  6. MAY 22MT AGMT AG notice5,609 MT residentsday 0
  7. MAY 22CA AGCA AG noticeno count statedday 0
  8. MAY 22NH AGNH AG notice20 NH residentsday 0
  9. MAY 22VT AGVT AG noticeno count statedday 0
  10. MAY 22MA AGMA AG notice823 MA residentsday 0
  11. MAY 22IN AGIN AG noticemost recent · states nationwide total 76,027day 0
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 4, 2023 – Dec 6, 2023
WA AG
Discovered
Dec 4, 2023IL AGDec 6, 2023WA AG + NH AG + VT AGJan 2, 2024ME AGfilings disagree on discovery
Data types
Health (basic) · Identity (basic) · Government ID · PII
WA AG + HHS OCR + NH AG +5
Attack vector
Ransomware
WA 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)

81,588

Sum of filed state slices

10,091· 12.4% of stated

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

US81,588
MT5,609
IN2,724
WA893
MA823
ME22
NH20

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

0 days

Cadence

~1 / 0d

vs. multi-state median

20.0× faster

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.