AccidentalGovernmentGovernmentMisdeliveryEmployee Data InvolvedCustomer Data InvolvedGovernment IDIdentity (basic)MediumContained

County of Stanislaus

bd_f61d31c6dd3aa9fa · schema v1 · pii pii-v1

Severity

Medium

Discovered

Jul 28, 2025

Filed

Oct 1, 2025

To disclose

9 weeks

Affected

Not disclosed

Linked

6 filings

Confidence

66%

Full breach record for County of Stanislaus →

Stanislaus County disclosed an inadvertent email disclosure of sensitive personal information, including Social Security numbers, for a limited number of individuals on July 28, 2025. The incident was caused by human error by a county employee. The county mitigated the issue, is retraining staff, and offering credit monitoring services.

J jump to incidentP pin to compareR raw source

Incident timeline

discovery → filing · 9 weeks / 65 days

Jul 28, 2025

Begins

Jul 28, 2025

Discovered

Oct 1, 2025

Filed

vs. sector median

2 wks faster

This filing is one of 6 about the same incident.View merged incident

Linked disclosures

Why this link?

Regulatory filings (5) · sorted by filing gap

Montana State AGbd_1c727528ee5ee2ab2025-10-01Candidate
Nebraska State AGbd_1e18886e01c0b15d2025-10-01Verified
Indiana State AGbd_a0f581e847ea15442025-10-01Verified
Massachusetts State AGbd_fce2d1a0136ec7b02025-10-01Verified

Show 1 more filing ↓

Vermont State AGbd_ff2316c528677cba2025-10-01Verified

Name: County of Stanislaus
norm: county of stanislaus

Name: County of Stanislaus
norm: county of stanislaus
Industry: Governmentllm

Discovered: Jul 28, 2025
Breach occurred: Jul 28, 2025
Undetected for: 0 daysoccurrence → discovery
Materiality determined: —
Notification sent: —
Affected individuals: Not disclosed
Data types: Government IDIdentity (basic)
Data elements: Social Security numberDate of birth
Attack vector: Unknown
Threat actor: Internal

During the incident: Immediately took steps to mitigate the issue
Offering complimentary access to Experian IdentityWorks
Changes made: Retraining our staff to prevent similar incidents from occurring in the future
Working with technology support to safeguard against future inadvertent disclosures
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 9 weeks(65 days from discovery to filing)
Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 6 filings · 6 states

View merged incident ↗

Montana State AGOct 1 · first

Nebraska State AGOct 1 · first

Indiana State AGOct 1 · first

Massachusetts State AGOct 1 · first

Vermont State AGOct 1 · first

California State AGOct 1 · first · this page

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Source URL: https://oag.ca.gov/ecrime/databreach/reports/sb24-612063
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: 891d1dd60830045aff783b50807daa282bde8294862b0d3a14845a0ff9955ee3

Linked disclosures

Regulatory filings (5) · sorted by filing gap

Reporting entityCounty of Stanislaus

Victim entityCounty of Stanislaus

Incidentdiscovered Jul 28, 2025

Stated responseImmediately took steps to mitigate the issue

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenanceoag.ca.gov