HackingGovernmentGovernmentTargetedIdentity (basic)LowContained

City of Lakewood

bd_f4ef5f35a4a17a5a · schema v1 · pii pii-v1

Severity

Low

Discovered

Dec 20, 2022

Filed

Oct 10, 2023

To disclose

42 weeks

Affected

10state residents only

Linked

5 filings

Confidence

65%

Full breach record for City of Lakewood →

The City of Lakewood notified affected individuals of unauthorized network access occurring between November 14 and December 20, 2022. The incident involved an unknown individual viewing or downloading files containing names and other personal information. The City engaged federal law enforcement, conducted a comprehensive review, and offered complimentary credit monitoring and identity theft protection services to affected individuals.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 36 days

discovery → filing · 42 weeks / 294 days

Nov 14, 2022

Begins

Dec 20, 2022

Discovered

Oct 10, 2023

Filed

vs. sector median

+31 wks slower

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

Linked disclosures

Why this link?

Ransomware claims (1)

Leak Sitealphvbd_20fe521404a4a5e72023-02-22 · +230dCandidate

Regulatory filings (3) · sorted by filing gap

Indiana State AGbd_40b9d54d5dd3171c2023-10-10Candidate
Maine State AGbd_5d9fb71de9cd4a422023-10-10Verified
Washington State AGbd_eb80bed60e9e9db62023-10-10Verified

Name: City of Lakewood
norm: city of lakewood
Domain: cityoflakewood.us
Industry: government_public

Name: City of Lakewood
norm: city of lakewood
Domain: cityoflakewood.us
Industry: government_public
Industry: Governmentllm

Discovered: Dec 20, 2022
Breach occurred: Nov 14, 2022 – Dec 20, 2022
Undetected for: 36 daysoccurrence → discovery
Materiality determined: —
Notification sent: Oct 10, 2023
Affected individuals: 10state-resident count only
Data types: Identity (basic)
Attack vector: Unauthorized Access
MITRE ATT&CK: T1078 Valid AccountsT1119 Automated Collection
Threat actor: External
Regulator citations: corresponded with federal law enforcement

During the incident: Launched an investigation into the nature and scope of the event
Corresponded with federal law enforcement
Conducted a comprehensive review of the impacted files
Offering you access to 12/24 months of complimentary monitoring and identity theft protection services through IDX
Reviewing and enhancing our technical safeguards
Enhancing our information security policies and procedures
Changes made: Reviewing and enhancing our technical safeguards
Enhancing our information security policies and procedures
Source: Quoted from the filing itself, not independently verified.

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

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 4 filings · 4 states

View merged incident ↗

Indiana State AGOct 10 · first

Maine State AGOct 10 · first

Washington State AGOct 10 · first

Montana State AGOct 10 · 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://dojmt.gov/wp-content/uploads/OCP/Consumer-notification-letter-760.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Oct 10, 2023
Raw hash: 00e41f7cd0cfe18bb9caf7ae5914bc2adbe2b75060c346d465305aaa281e6d1c

Linked disclosures

Ransomware claims (1)

Regulatory filings (3) · sorted by filing gap

Reporting entityCity of Lakewood

Victim entityCity of Lakewood

Incidentdiscovered Dec 20, 2022

Stated responseLaunched an investigation into the nature and scope of the event

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov