GLOBALClaimed by EverestFirst sightinglinked via multi-signal match · 100%
Posted to leak site Aug 8, 2025bd_3b7be1c9afbd45db
La Perouse Is your One-Stop-Shop for complete revenue cycle management. Let us help you focus on what you do best.
Clustered 3 filings across 3 jurisdictions · filing window Aug 8, 2025 → May 28, 2026. View entity profile → Other incidents for this victim →
incident inc_c580528ea4e34bf0 · 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.
CA NV
Leak Site · HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
May 27, 2025 → Jul 9, 2025
When the intrusion reportedly occurred, per the linked filings
Jul 8, 2025
Reported by CALIFORNIA AG filing
La Perouse Is your One-Stop-Shop for complete revenue cycle management. Let us help you focus on what you do best.
La Perouse, LLC (a Business Associate, NV) reported to HHS OCR on 2025-09-02 a Hacking/IT Incident affecting 501 individuals. Breached information was located on a Network Server. A business associate was present. No further detail was provided in the web description.
Affected (this filing): 501
La Perouse LLC, a patient billing services provider, notified the California Attorney General of a data breach affecting patient information. On July 8, 2025, the company discovered unauthorized access to a third-party billing platform account. An attacker copied files containing names and other personal information. The breach window is May 27, 2025, to July 9, 2025. La Perouse engaged forensic investigators, secured its own networks, and implemented additional safeguards with the vendor. Affected individuals are offered 12 months of 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.