Analyst assessment
Lexington-Richland School District Five experienced a June 2025 ransomware incident that disrupted its network, delayed employee retention bonuses and affected summer instruction. The district’s official incident information identifies June 3 as the date unusual activity made network devices unavailable and attributes the attack to Interlock. The South Carolina district serves communities in Lexington and Richland counties, including Irmo and Chapin. Our initial reporting documented the resulting disruption.
The district later confirmed that an unauthorized external individual took files. Its consumer notice dated Aug. 29 said potentially affected information included names, driver’s license or state identification numbers, financial account information, dates of birth and Social Security numbers. The categories varied among individuals. Separately, the official FAQ says historical student records from 2010 were released; that finding does not establish that every current student’s information was taken.
Operational significance
The network disruption affected administrative payments and education services. WIS reported June 5 that internet outages delayed retention bonuses scheduled for June 6. These payments were bonuses rather than ordinary salary checks. The State’s account of the August town hall also documented delays to high school summer classes. The evidence supports material disruption without establishing that all campuses closed or that all instruction stopped.
At a July 21 board meeting, district officials said full network operations had returned June 26. Deployment of additional security measures to more than 5,000 devices continued afterward. That continuing work and the later breach investigation do not establish a continuing operational outage. Network restoration supports a resolved operational assessment, while the precise bonus payment date and resumption date for every affected class remain unverified.
The superintendent said the district received a ransom demand and declined to pay, according to The State. The amount was not disclosed. The South Carolina regulator’s filing entry records 30,944 affected South Carolina residents. That figure describes the state’s reporting scope rather than the nationwide number of people affected. The district offered credit monitoring; its notice reported no known misuse as of Aug. 29, which does not negate the confirmed theft and release of records.
Confidence and uncertainty
Confidence is high in the ransomware incident, operational disruption, file theft and the district’s attribution to Interlock because the district acknowledged them directly or through named reporting of its officials. The ransomware.live listing separately records a same-domain Interlock claim. The tracker’s discovery timestamp is not the intrusion date or a verified publication date for the original claim, and claimed data volumes remain unverified.
At the Aug. 26 town hall, the superintendent described investigators’ belief that phishing may have reached an employee. That account supports a qualified initial access assessment rather than a complete forensic reconstruction. The reviewed evidence does not identify a specific exploited vulnerability, establish a link to the separate PowerSchool incident or substantiate attribution to a foreign government.
Analytic gaps
The intrusion’s beginning before detection, detailed access sequence, exact volume of stolen information and full composition of the released files remain unresolved. Historical student records, information potentially affected in the notice and precautionary monitoring for current staff describe different evidence and populations. The exact date when every delayed payment and instructional activity returned to normal is also unverified; June 26 is the documented network restoration milestone. No single final date is assigned to all operational effects.
The district’s published public records responses say it withheld investigative records sought in October 2025, citing privilege and other exemptions, and directed readers to its incident FAQ. Those responses do not provide a public forensic reconstruction.