AccidentalMisdeliveryCustomer Data InvolvedIDENTITY_BASICIDENTITY_GOVERNMENTMediumResolved
Counyt of Stanislaus
bd_ff2316c528677cba · schema v1 · pii pii-v1
Full breach record for Counyt of Stanislaus →County of Stanislaus notified Vermont AG of a July 28, 2025 incident where an employee inadvertently emailed a file containing full names and Social Security numbers to a limited number of individuals. The County offered 12 months of Experian IdentityWorks monitoring. No evidence of fraud was found.
Vermont clock✗ VT AG >45 bday9 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 5 about the same incident.View merged incident
Linked disclosures
Why this link?Regulatory filings (4) · sorted by filing gap
- bd_1c727528ee5ee2abMontana State AGfiled 2025-10-01Candidate
- bd_a0f581e847ea1544Indiana State AGfiled 2025-10-01Verified
- bd_d130f08a91377c02Maine State AGfiled 2025-10-01Verified
- bd_f61d31c6dd3aa9faCalifornia State AGfiled 2025-10-01Verified
Source provenance
- Source URL
- https://ago.vermont.gov/document/2025-10-01-county-stanislaus-data-breach-notice-consumers
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
- Filed at
- Oct 1, 2025
- Raw hash
- 60b937995c6ee3007bae1c586cba63b0eb3db4bb13a4009311e4b83da30f9aa2
Reporting entity
- Name
- Counyt of Stanislausnorm: counyt of stanislaus
Victim entity
- Name
- Counyt of Stanislausnorm: counyt of stanislaus
Incident
- Discovered
- Jul 28, 2025
- Materiality determined
- —
- Notification sent
- Oct 1, 2025
- Affected individuals
- Not disclosed
- Data types
- IDENTITY_BASICIDENTITY_GOVERNMENT
- Attack vector
- Unknown
- MITRE ATT&CK
- T1566.002 Spearphishing Link
Compliance
- Time to disclose
- 9 weeks(65 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.