Xsolis, Inc. reported to HHS on 2026-06-05 a Hacking/IT Incident affecting 1396519 individuals. Breached information located on Network Server. Business Associate present: Yes.
Affected (this filing): 1,396,519
Clustered 5 filings across 4 jurisdictions · filing window Jun 5, 2026 → Jul 21, 2026. View entity profile → Other incidents for this victim →
incident inc_71898663ba1e43c2 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
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.
PHI · Health (basic) · Identity (basic)
CA IN TN WA
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jan 20, 2026
When the intrusion reportedly occurred, per the linked filings
Jan 22, 2026
Reported by CALIFORNIA AG, WASHINGTON AG filings
Xsolis, Inc. reported to HHS on 2026-06-05 a Hacking/IT Incident affecting 1396519 individuals. Breached information located on Network Server. Business Associate present: Yes.
Affected (this filing): 1,396,519
Xsolis, Inc. experienced a targeted phishing attack on January 22, 2026, resulting in unauthorized access to a limited portion of its environment. The incident potentially exposed protected health information (PHI) and personal data of patients, including minors, served by healthcare provider clients. Xsolis contained the incident, engaged forensic experts, notified law enforcement, and implemented security enhancements including password resets and increased monitoring. Identity monitoring services were offered to affected individuals.
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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.
Xsolis Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2026-01-20 and was reported on 2026-06-05. 154 Indiana residents were affected. 1,396,519 individuals affected in total.
Affected (this filing): 1,396,519
Xsolis, Inc. experienced a targeted phishing attack on January 22, 2026, resulting in unauthorized access to a limited portion of its environment. The incident potentially exposed protected health information (PHI) and personal data of patients, including minors, served by Xsolis's healthcare provider clients. Xsolis contained the incident, engaged forensic experts, notified law enforcement, and implemented remediation measures including password resets and enhanced monitoring. Identity monitoring services were offered to affected individuals.
Xsolis, Inc., a health sector entity reported a unauthorized access incident to the Washington Attorney General. The organization became aware of the incident on 2026-01-22 and filed notice on 2026-06-19. 24,711 Washington residents were affected. 148 days elapsed between awareness and notification. 2 days to identify the breach. 0 days to contain the breach.
Affected (this filing): 24,711