MalwareGovernmentGovernmentRansomwareCapture Stored DataData ExfiltratedData EncryptedCustomer Data InvolvedTargetedAuthenticationEducationFinancial accountHealth (basic)Identity (basic)Government IDPHIHighContained

City of Lakewood

bd_eb80bed60e9e9db6 · schema v1 · pii pii-v1

Severity

High

Discovered

Dec 20, 2022

Filed

Oct 10, 2023

To disclose

42 weeks

Affected

24,219state residents only

Linked

5 filings

Confidence

70%

Full breach record for City of Lakewood →

The City of Lakewood, Washington, disclosed a ransomware incident affecting 24,219 residents. Unauthorized access occurred between Nov 14 and Dec 20, 2022. Data exposed included names, SSNs, driver's licenses, financial accounts, and health info. Notices sent Oct 10, 2023. Credit monitoring offered.

J jump to incidentP pin to compareR raw source

Leak gap clock✗ Leak >180d42 weeks discovery → filing

⚠ AG web formThe discovery date came from the AG web-form field, which is systematically later than the detection date stated in the letter. Treat the clock as indicative.

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
Montana State AGbd_f4ef5f35a4a17a5a2023-10-10Verified

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

Name: City of Lakewood
norm: city of lakewood
Domain: cityoflakewood.us
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: 24,219state-resident count only
Data types: Identity (basic)Government IDFinancial accountAuthenticationHealth (basic)
Data elements: NameSocial Security numberDriver's licence numberFinancial account numberDate of birthUnique private keyStudent ID numberPassport numberHealth insurance IDMedical information
WA-stated cause: Cyberattack
WA-stated duration: lifecycle 1-99dexposure 1-99d
WA-stated discovery: Found while ongoingContained same day
Attack vector: Ransomware
MITRE ATT&CK: T1486 Data Encrypted for ImpactT1041 Exfiltration Over C2 Channel
Threat actor: ExternalFinancial
Regulator citations: Communicated with federal law enforcement regarding the eventProviding written notice of this event to relevant state regulators

During the incident: Launched an investigation into the nature and scope of the event with the assistance of third-party forensic specialists
Conducted a comprehensive review of the impacted files
Communicated with federal law enforcement regarding the event
Providing access to credit monitoring services for one (1) year, through IDX, to individuals whose personal information was potentially affected by this event, at no cost to these individuals
Providing impacted individuals with guidance on how to better protect against identity theft and fraud
Providing written notice of this event to relevant state regulators, as necessary, and to the three major credit reporting agencies
Providing notice of this event on its website and to state-wide Washington media
Changes made: Working to implement additional safeguards and training to its employees
Reviewing and enhancing its technical safeguards
Reviewing and enhancing its 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: Leak >180dWA AG >90d
Discovery-date grounding: AG web formThe discovery date came from the AG web-form field, which is systematically later than the detection date stated in the letter. Treat the clock as indicative.

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

Montana State AGOct 10 · first

Washington 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://agportal-s3bucket.s3.amazonaws.com/databreach/BreachA26745.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: 79c949cd7039c4d86df250634e941be44f040297d67bbb42190ac7a7f310333a

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 with the assistance of third-party forensic specialists

ComplianceLeak >180d

Extraction provenanceno artifact recorded

Source provenanceagportal-s3bucket.s3.amazonaws.com