MalwareGovernmentGovernmentRansomwareRansom DemandedData EncryptedFinancial accountIdentity (basic)Government IDPHIPIIHealth (basic)MediumContained

Long Beach

bd_ea54c3cc7ffdfec8 · schema v1 · pii pii-v1

Severity

Medium

Discovered

Nov 14, 2023

Filed

Apr 14, 2025

To disclose

17 months

Affected

983state residents only

Linked

6 filings

Confidence

70%

Full breach record for Long Beach →

The City of Long Beach CA reported a ransomware incident on November 14, 2023, affecting 983 Washington residents. The City engaged external experts, notified law enforcement, and determined on March 18, 2025, that personal information was accessed. Notices were sent on April 14, 2025, offering credit monitoring.

J jump to incidentP pin to compareR raw source

Washington clock✗ WA AG >90d17 months 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.

Incident timeline

discovery → filing · 17 months / 517 days

Nov 14, 2023

Begins

Nov 14, 2023

Discovered

Apr 14, 2025

Filed

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_3f9f13ebade2c9412025-04-14Verified
Oregon State AGbd_5038cad4b88d3b6d2025-04-14Verified
HHS OCRbd_61d3957a1832b7682025-04-14Verified
California State AGbd_75f87927cd73e4182025-04-14Verified

Show 1 more filing ↓up to 4d gap

New Hampshire State AGbd_a3b3ec450935a9132025-04-18 · +4dVerified

Name: Long Beach
norm: long beach
Domain: cityoflongbeach.org
Industry: Government

Name: Long Beach
norm: long beach
Domain: cityoflongbeach.org
Industry: Government
Industry: Governmentllm

Discovered: Nov 14, 2023
Breach occurred: Nov 14, 2023
Undetected for: 0 daysoccurrence → discovery
Materiality determined: —
Notification sent: Apr 14, 2025
Affected individuals: 983state-resident count only
Data types: PIIIdentity (basic)
Data elements: NameSocial Security numberDriver's licence numberFinancial account numberDate of birthPassport numberHealth insurance IDMedical information
WA-stated cause: Cyberattack
WA-stated duration: lifecycle 0dexposure 0d
WA-stated discovery: Found while ongoingContained same day
Attack vector: Ransomware
MITRE ATT&CK: T1486 Data Encrypted for Impact
Threat actor: ExternalFinancial
Regulator citations: notified law enforcement

During the incident: Initiated a thorough and detailed technical investigation into the incident with the assistance of external information technology experts
Notified our community
Working very closely with leading, external cybersecurity professionals
Notified law enforcement
Notified the public of the incident through various public communications channels
Changes made: Offering a complimentary credit-monitoring service with Experian IdentityWorks
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 17 months(517 days from discovery to filing)
Compliance flags: WA AG >90d
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.

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 6 filings · 5 states

View merged incident ↗

Montana State AGApr 14 · first

Oregon State AGApr 14 · first

HHS OCRApr 14 · first

California State AGApr 14 · first

Washington State AGApr 14 · first · this page

New Hampshire State AG+4d

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/BreachA33013.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Apr 14, 2025
Raw hash: 0cb357e8dcc5f291090565d39d97341a1eca2615665606f7683710c73a82149d

Linked disclosures

Regulatory filings (5) · sorted by filing gap

Reporting entityLong Beach

Victim entityLong Beach

Incidentdiscovered Nov 14, 2023

Stated responseInitiated a thorough and detailed technical investigation into the incident with the assistance of external information technology experts

ComplianceWA AG >90d

Extraction provenanceno artifact recorded

Source provenanceagportal-s3bucket.s3.amazonaws.com