Fort Bend County Libraries

A Feb. 24, 2025, cyberattack disrupted Fort Bend County Libraries’ network, catalog and public computer services. The system rebuilt infrastructure and moved its catalog to the cloud, with a September relaunch. Government-records reporting documented a ransom note; the library later reported no evidence patrons’ sensitive information was stolen.
Malware that encrypts systems or data, typically accompanied by a ransom demand.
Authorized users could not access required data because of the incident, even when the data was not encrypted, deleted, or destroyed.
A primary service, system, platform, or operational capability became entirely unavailable.
A service, system, platform, or operational capability remained available only in part or with significant limitations.
Services remained available but with reduced performance, reliability, functionality, capacity, or responsiveness.
Services or systems experienced recurring, unstable, or temporary periods of unavailability.
Internal or external network connectivity was unavailable or materially impaired.
The organization lost or materially restricted internet connectivity.
Email sending, receiving, access, or related messaging functions were unavailable or materially impaired.
Telephone, voice-over-IP, call-center, or related voice communication services were 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.
A specific application or software platform became unavailable or unusable.
Business, financial, customer, administrative, or operational transactions could not be completed 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.
Services continued but with longer processing, response, delivery, or completion times.
The disruption caused an accumulation of unprocessed requests, cases, orders, records, appointments, or other work.
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.
Employees or contractors were unable to perform normal duties because systems, data, facilities, or communications were unavailable.
Customers, residents, patients, students, vendors, or members of the public faced access restrictions or could not use services normally.
The victim received a demand for payment in exchange for restoring access, decrypting systems, preventing disclosure, or stopping another threatened action.
The actor directly contacted the victim through a ransom note, email, chat portal, telephone call, messaging platform, or other communication channel.
A dedicated portal, chat system, or communication channel was used for ransom negotiation or victim instructions.
A cyberattack discovered Feb. 24, 2025, disrupted Fort Bend County Libraries in Texas and led to a months-long rebuild of its network and library-management services. A March 10 local report described the cyber cause before the library’s March 12 public explanation. The library said it had engaged cybersecurity professionals and was working with county IT.
In July reporting based on government records, ABC13 described a ransomware incident and a Texas Department of Information Resources report documenting a ransom note with instructions to use a private communications portal. The note claimed files had been encrypted and important data copied. That allegation is distinct from an independently established finding of data theft; no named perpetrator is established.
The outage affected the website, catalog, account access, email, some phones and public computer and printing services. Branches continued lending physical materials and offering programs. A replacement website and restored digital resources provided partial alternatives, but core catalog functions remained unavailable.
The director’s July 11 update described restoring backup data and importing transactions recorded offline. Public Wi-Fi had returned, with possible interruptions during equipment upgrades, while the catalog, account management and holds tracking remained unavailable. Some databases and lending of hotspots and Launchpads were also restricted.
The library’s relaunch announcement scheduled the new network and cloud-based catalog for Sept. 2. It warned that workstation and printing replacement would continue and described a backlog of new materials whose records could not be uploaded during the outage. September 13 reporting confirmed services were back online and relaunch events had occurred. ABC13 reported $5.8 million in rebuilding expenditures, including equipment, software and staffing; this is reported recovery spending, not a ransom amount.
The disruption concerned the library network, rather than proof of a countywide government-network outage. KPRC’s May 12 reporting identified an exception: the University of Houston–Sugar Land library computer system operated separately and was unaffected.
Confidence is high in the cyber cause and operational disruption. Ransomware is assessed with high confidence from records-based reporting, but the underlying forensic report and ransom note have not been independently inspected. The library said in July that forensic analysis found no evidence patrons’ sensitive information was accessed or stolen. This finding does not erase the documented availability loss or independently resolve every allegation in the ransom note.
The incident is assessed as resolved following confirmed service relaunch. The exact date all replacement equipment and processing backlogs returned to normal is unknown; no precise end date is assigned. The August 13 relaunch notice documents the latest dated service limitations in the reviewed record.
The initial access route, ransomware family, demand amount, payment outcome and complete technical findings remain unverified. The 2021 cryptomining incident and attacks at other library systems are separate events.

County-operatedpubliclibrarysystemservesFortBendCounty; officialmission/branchdirectory/countygovernanceanddirectorstatementsestablishgeographicremit. Pairlibraryservice_areaandincidentimpacted_area withseparatesiteanchors. Overlaydoesnotclaimallcountyresidentslostinternet,allcountyofficeswerecompromised,orUH-SugarLand’sseparatecomputersystemwasaffected.
CincoRanch2620CommercialCenterBlvd andMissionBend8421AddicksClodineRoad exactCensusmatchesareunincorporatedCDPsitesinFortBend48157,notKaty/Houstonmunicipalities. FulshearBranch6350GMLibraryRoadisverifiedbyofficialbranchdirectorybutreturnednoCensusstreetmatch; conservativecountyanchorusedwithoutclaimingmunicipalcontainment. Thesephysicalsitesareseparatefromthecountygovernmentalserviceremitanddo notimplyallcountyfacilitieswereaffected. Official current branch directory: https://www.fortbendlibraries.gov/locations-hours ; incident impact supported by director/relaunch system statements. Branches remained open and programs continued.
PinnacleSeniorCenterLibrary5525HobbyRoad exactCensusmatchconfirmsHouston4835000withinFortBend48157. Reuseexistingcross-countyHoustonmunicipalitywithHarrisprimaryparent; geographicprofilenotesFortBendextension. No assertionofHarrisCountylibraryimpact. Official current branch directory: https://www.fortbendlibraries.gov/locations-hours ; incident impact supported by director/relaunch system statements. Branches remained open and programs continued.
MissouriCityBranch1530TexasParkway andSienna8411SiennaSpringsBoulevard exactCensusmatchesconfirmMissouriCity4848804/FortBend48157. No inferencefrompostalwordingalone. Official current branch directory: https://www.fortbendlibraries.gov/locations-hours ; incident impact supported by director/relaunch system statements. Branches remained open and programs continued.
AlbertGeorgeBranch9230GeneStreet exactCensusmatch confirmsNeedvillecity4850628/FortBend48157. Official current branch directory: https://www.fortbendlibraries.gov/locations-hours ; incident impact supported by director/relaunch system statements. Branches remained open and programs continued.
Administration1003GolfviewDrive; GeorgeMemorial1001GolfviewDrive; LawLibrary1422EugeneHeimannCircle. Exact Censusstreetmatches confirmRichmondcity4861892/FortBend48157. Library administrationandaffectedbranches representedby municipality, not facilityrecords. Official current branch directory: https://www.fortbendlibraries.gov/locations-hours ; incident impact supported by director/relaunch system statements. Branches remained open and programs continued.
FirstColony2121AustinParkway,SugarLand550EldridgeRoad andMamieGeorge320DullesAvenue exactCensusmatchesallconfirmSugarLand4870808/FortBend48157. MamieGeorgehasStaffordpostaladdressbutiswithintheSugarLandmunicipality. UH-SugarLandcomputer-systemexceptiondoesnotnegateaffectedotherSugarLandbranches; noUniversitycomputersattributedasaffected. Official current branch directory: https://www.fortbendlibraries.gov/locations-hours ; incident impact supported by director/relaunch system statements. Branches remained open and programs continued.
Ghost intake describing the library network disruption.
Early cyber reporting and replacement-site/catalog limitations.
Official acknowledgment, staged recovery, offline records and forensic no-evidence finding.
Official social post directing patrons to the March12 explanation.
Ongoing public-computer restrictions and the unaffected university-system exception.
Records-based reporting documents the ransom note and prolonged disruption.
Official relaunch plan, staged workstation replacement and materials backlog.
Service relaunch confirmed; records-based recovery spending reported.
Signed-in members can report an error, update, or missing source.