HackingGovernmentGovernmentStolen CredentialsCapture Stored DataData ExfiltratedData PublishedTargetedCustomer Data InvolvedIdentity (basic)Government IDFinancial accountMediumActive

City of Waynesboro

bd_5a04ce265669bcf2 · schema v1 · pii pii-v1

Severity

Medium

Discovered

Jan 10, 2023

Filed

Nov 30, 2023

To disclose

46 weeks

Affected

3state residents only

Linked

3 filings

Confidence

66%

Full breach record for City of Waynesboro →

The City of Waynesboro notified residents of a data breach where threat actors gained access to its IT environment starting December 20, 2022. The City became aware of unusual activity on January 10, 2023. Data potentially exposed includes names, SSNs, DOBs, passport numbers, and financial account information. The City engaged third-party experts and law enforcement.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 21 days

discovery → filing · 46 weeks / 324 days

Dec 20, 2022

Begins

Jan 10, 2023

Discovered

Nov 30, 2023

Filed

vs. sector median

+35 wks slower

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

Idaho State AGbd_8a0f4ea6342b7e8a2023-11-30Verified
Maine State AGbd_3a57289dcc1c4c752023-12-01 · +1dVerified

Name: City of Waynesboro
norm: city of waynesboro

Name: City of Waynesboro
norm: city of waynesboro
Industry: Governmentllm

Discovered: Jan 10, 2023
Breach occurred: Dec 20, 2022
Undetected for: 21 daysoccurrence → discovery
Materiality determined: —
Notification sent: Nov 30, 2023
Affected individuals: 3state-resident count only
Data types: Identity (basic)Government IDFinancial account
Data elements: Social Security numberDate of birth
Attack vector: Unauthorized Access
MITRE ATT&CK: T1078 Valid AccountsT1041 Exfiltration Over C2 ChannelT1486 Data Encrypted for Impact
Threat actor: ExternalFinancial
Regulator citations: Law enforcement was notified
Initial access: valid_credentials

During the incident: Engaged leading third-party cybersecurity experts to investigate the incident
Secured personal information
Protected the City’s network from additional compromise
Notified law enforcement
Commenced an investigation to determine the nature and scope of the incident
Engaged a leading strategic service provider to monitor our cybersecurity systems
Reviewed our system’s architecture
Implemented stronger policies to prevent future attacks
Changes made: Implemented additional security measures designed to further protect the privacy of our employees, residents and vendors
Fortified its network defenses to prevent future attacks
Source: Quoted from the filing itself, not independently verified.

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

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 3 filings · 3 states

View merged incident ↗

Idaho State AGNov 30 · first

Montana State AGNov 30 · first · this page

Maine State AG+1d

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://dojmt.gov/wp-content/uploads/OCP/Consumer-notification-letter-897.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Nov 30, 2023
Raw hash: 51e5bee470becb50cfb15f24874eb27af183446fcc69fd0e0d8676472db4e70e

Linked disclosures

Regulatory filings (2) · sorted by filing gap

Reporting entityCity of Waynesboro

Victim entityCity of Waynesboro

Incidentdiscovered Jan 10, 2023

Stated responseEngaged leading third-party cybersecurity experts to investigate the incident

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov