Analyst assessment
Tarrant Appraisal District experienced a network disruption on March 21, 2024. Contemporary reporting described unusual network behavior and a protective system shutdown that made its website unavailable. In a district statement republished March 22 by Haslet, the victim confirmed ransomware and notification of the FBI and Texas authorities.
Operational significance
The incident disrupted appraisal information and public contact channels during property-appraisal season. Although the website returned in part within days, email and telephone service remained unavailable in initial reports.
Reporting on the April 22 board meeting said most systems had returned, but the dashboard and online protest functions were still expected later that week. The district offered in-person appraisal assistance. An April 26 follow-up reported essential services and the online protest function restored. The residential protest deadline moved from May 15 to May 24 to compensate for delayed access. This establishes recovery of those functions by April 26, without identifying the exact restoration day or proving every internal system had recovered. The incident is presumed resolved.
The board had approved $490,000 in security upgrades by April 22, according to the board-meeting coverage. These authorizations are distinct from a final tally of incident costs or a ransom payment.
Confidence and uncertainty
Confidence in ransomware involvement and service disruption is high. The April board-meeting report identifies Medusa, publication of compromised data and the district’s refusal to pay. It describes about 300 potentially affected people as an early estimate, rather than a final count. The ransom reportedly fell from $700,000 to $100,000.
The separate tracker listing’s alleged 217.79 gigabytes is an attacker claim, not an independently verified measurement. Its discovery timestamp does not establish original claim publication.
Analytic gaps
The entry method, final affected-person count, complete stolen-data inventory and exact restoration date remain unresolved. Security upgrades and replacement-system plans do not establish continuing outage. The earlier 2022 incident and preceding database failure are distinct events.