HackingDelayed DiscoveryPIIIDENTITY_BASICLowContained
David A. Nover, M.D., P.C.
bd_821c2b2055090b7b · schema v1 · pii pii-v1
Full breach record for David A. Nover, M.D., P.C. →David A. Nover, M.D., P.C. notified consumers of a data breach occurring on June 3, 2025, where unauthorized individuals viewed and copied personal information. The investigation was completed on October 29, 2025. Affected data includes PII. The practice retained forensic specialists and offers 12 months of credit monitoring. The exact number of affected individuals was not disclosed in the filing.
Vermont clock✗ VT AG >45 bday22 weeks discovery → filing
⚠ occurrence dateThe stored discovery date equals the breach OCCURRENCE date. Detection is normally later, so this OVERSTATES the delay — a 'late' verdict here may not be real.
This filing is one of 3 about the same incident.View merged incident
Linked disclosures
Why this link?Regulatory filings (2) · sorted by filing gap
- bd_21c76f7bfe6face5Montana State AGfiled 2025-11-03Candidate
- bd_92daaf66e905b4d3New Hampshire State AGfiled 2025-11-03Verified
Source provenance
- Source URL
- https://ago.vermont.gov/document/2025-11-03-david-nover-md-pc-data-breach-notice-consumers
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
- Filed at
- Nov 3, 2025
- Raw hash
- 22bac99c6f4e9bc29ab34da945ef38995da8ca42772670e1a9d6cfdbf6b1443a
Reporting entity
- Name
- David A. Nover, M.D., P.C.norm: david a nover md
Victim entity
- Name
- David A. Nover, M.D., P.C.norm: david a nover md
Incident
- Discovered
- Jun 3, 2025
- Materiality determined
- Nov 3, 2025
- Notification sent
- Nov 3, 2025
- Affected individuals
- Not disclosed
- Data types
- PIIIDENTITY_BASIC
- Attack vector
- Unauthorized Access
- MITRE ATT&CK
- T1078 Valid Accounts
- Threat actor
- External
Compliance
- Time to disclose
- 22 weeks(153 days from discovery to filing)
- Compliance flags
- VT AG >45 bday
- Discovery-date grounding
- occurrence dateThe stored discovery date equals the breach OCCURRENCE date. Detection is normally later, so this OVERSTATES the delay — a 'late' verdict here may not be real.
Extraction provenance
- Status
- No extraction artifact recorded for this disclosure.