GLOBALClaimed by QilinFirst sightinglinked via multi-signal match · 100%
Posted to leak site Jun 5, 2024bd_58ee69bf27d12283
“Next step healthcare” (nextstephc.com) was attacked by our team, stay tuned.
Clustered 4 filings across 3 jurisdictions · filing window Jun 5, 2024 → May 30, 2025. View entity profile → Other incidents for this victim →
incident inc_aff7d125c5174415 · merge_method human · confidence 100%
Discovered → first regulatory filing
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
Health (basic)
MA ME
Leak Site · HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
May 21, 2024 → Jun 5, 2024
When the intrusion reportedly occurred, per the linked filings
“Next step healthcare” (nextstephc.com) was attacked by our team, stay tuned.
“Next step healthcare” (nextstephc.com) was attacked by our team, stay tuned.
May 22, 2025
Reported by MAINE AG filing
Next Step Healthcare LLC reported an external system breach that occurred from May 21, 2024, to June 5, 2024. The breach was discovered on May 22, 2025. The incident affected 192 Maine residents, who were notified on May 29, 2025. The company offered 12 months of identity theft protection services through IDX.
Affected (this filing): 192
Next Step Healthcare LLC (Massachusetts) reported to HHS OCR on 2025-05-30 a Hacking/IT Incident affecting 12,090 individuals. Breached information was located on a Network Server. No business associate was identified as involved. No further details were provided in the public HHS breach portal entry.
Affected (this filing):
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.