City of Lubbock

Lubbock, Texas, took municipal systems offline after finding potentially malicious code on a computer on Aug. 12, 2025. Public services were restored, and the city later reported no evidence of a data breach or compromised resident information.
The incident is confirmed to be cyber-related, but the specific attack mechanism is unknown.
Authorized users could not access required data because of the incident, even when the data was not encrypted, deleted, or destroyed.
Internal or external network connectivity was unavailable or materially impaired.
A public-facing website was unavailable, disabled, or inaccessible.
A public, customer, employee, student, patient, vendor, or partner portal was unavailable or materially impaired.
Internal business, administrative, operational, or staff-facing systems were unavailable.
The organization could not process, receive, issue, reconcile, or record payments normally.
Staff, customers, patients, students, residents, or other users could not access records or case information normally.
The organization could not create, update, search, file, approve, transmit, or otherwise process records normally.
Public administrative, licensing, permitting, court, tax, records, benefits, or other government services were materially affected.
Staff or users had to rely on paper, telephone, in-person, offline, or other manual processes.
The organization redirected users to a different website, office, telephone number, email address, provider, or service channel.
The incident may involve extortion, but available evidence does not establish which extortion indicators were present.
Lubbock, Texas, took municipal systems offline on Aug. 12, 2025 after IT staff detected potentially malicious code on one computer. The city’s initial public statement identified a security concern. Its catastrophe record explicitly described a cyberattack beginning Aug. 12 that shut down systems and public-information resources.
The operational disruption is confirmed even though the later investigation found no evidence of a data breach. The broad shutdown was a precautionary city response; the record does not establish that an attacker disabled every system or achieved widespread compromise.
We reported Aug. 18 that residents were directed to make utility payments in person while restoration proceeded, and that public safety services continued. The outage also impaired public-records responses. The Aug. 12–18 suspension of public-information deadlines describes an administrative accommodation, not a measured duration of complete technical outage.
The full city statement published Aug. 19 said public-facing applications returned within the first 24 hours and all public access systems were available after days of work and scanning. Local reporting preserved a Wednesday update describing gradual network restoration and in-person utility payments. That supports continuing effects on Aug. 13 without treating an Aug. 18 republication or restoration forecast as a fresh outage observation.
Confidence is high in a cyber-related disruption because the city explicitly identified a cyberattack and documented its protective shutdown. The city reported no evidence of a breach and said it was confident resident information had not been exfiltrated or compromised. That is an attributed investigation finding, not independent verification of every forensic conclusion.
No reviewed evidence establishes ransomware, encryption, extortion, a named attacker, a ransom demand or payment. Available ransomware-lead searches for Lubbock and its current and legacy official domains returned no matching claim. The potentially malicious code remains unspecified; no malware family or entry method is established.
The precise intrusion time, nature of the detected code, full internal-system recovery sequence and response cost remain unestablished. Public applications returned quickly, but the city did not give an exact completion day for every recovery task.
The earlier fake-payment-window incident on the utility website, involving activity in December 2024–January 2025, is separate. Its reported affected-person count and card-data exposure are not assigned to the August shutdown. A later online allegation of card fraud supplies no verified causal link to this event.
Operations are resolved based on the affirmative Aug. 19 city statement that public access systems were fully available. Aug. 13 is the latest dated ongoing recovery observation supported by the reviewed chronology. The exact end remains unset because the city described systems as already restored by its announcement rather than giving a precise technical completion day.

Lubbock is the municipal administrative site anchor for the affected city systems. Preserves the existing municipality without creating a facility or asserting loss of emergency response or physical utility delivery.
Lubbock’s municipal jurisdiction supplies governmental service context for unavailable online transactions and public-records processing. This does not imply every resident or physical utility-delivery system was disrupted.
The city found potentially malicious code on one computer, took all systems offline, restored public applications within 24 hours and found no evidence of a data breach.
The city states a cyberattack began Aug. 12 and shut down systems and public-information resources; restoration was expected to take multiple days.
Signed-in members can report an error, update, or missing source.