Clustered 3 filings across 3 jurisdictions · filing window Apr 24, 2025 → Jun 10, 2025. View entity profile → Other incidents for this victim →
incident inc_a6140da57f344469 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Health (basic) · Identity (basic) · Financial account
FEDERAL IN VT
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jun 18, 2024
When the intrusion reportedly occurred, per the linked filings
Jun 18, 2024
Reported by VERMONT AG filing
Apex Global Solutions reported a data breach to the Indiana Attorney General. The breach occurred on 2024-06-18 and was reported on 2025-04-24. 1 Indiana residents were affected. 420 individuals affected in total.
Affected (this filing): 420
Apex Global Solutions, LLC (NY, Business Associate) reported to HHS on 2025-06-10 a Hacking/IT Incident affecting 14,741 individuals. Breached information was located on Desktop Computer and Laptop. PHI involved included clinical, demographic, and financial information. The covered entity notified HHS, affected individuals, and the media, and provided substitute notice. Credit monitoring services were offered; additional administrative, technical, and security safeguards were implemented in response.
Affected (this filing):
Apex Global Solutions, LLC notified consumers of unauthorized access to systems containing PII, PHI, and financial data between June 18 and July 2, 2024. The incident was discovered in June 2024 and investigation completed March 2025. Affected data included names, SSNs, DOBs, health insurance info, and financial account numbers. AGS engaged third-party specialists, secured systems, and offered credit monitoring.
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.