Crisis24 Breach Incident Score: Analysis & Impact (CRI5871558112725)

In this Rankiteo incident briefing, we review the Crisis24 breach identified under incident ID CRI5871558112725.

The analysis begins with a detailed overview of Crisis24's information like the linkedin page: https://www.linkedin.com/company/crisis24, the number of followers: 71897, the industry type: Security and Investigations and the number of employees: 2157 employees

After the initial compromise, the video explains how Rankiteo's incident engine converts technical details into a normalized incident score. The incident score before the incident was 768 and after the incident was 662 with a difference of -106 which is could be a good indicator of the severity and impact of the incident.

In the next step of the video, we will analyze in more details the incident and the impact it had on Crisis24 and their customers.

City of Worcester recently reported "Cyberattack on CodeRED by Crisis24 Disrupts AlertWorcester Emergency Notification System", a noteworthy cybersecurity incident.

The City of Worcester announced that its automated emergency notification system, AlertWorcester (powered by third-party system CodeRED by Crisis24), is unavailable due to a cyberattack.

The disruption is felt across the environment, affecting AlertWorcester (CodeRED by Crisis24) and legacy CodeRED environment, and exposing names, addresses and email addresses.

In response, teams activated the incident response plan, moved swiftly to contain the threat with measures like decommissioning of legacy CodeRED environment, and began remediation that includes rebuilding system on new infrastructure and restoring from March 31, 2025 backups, and stakeholders are being briefed through public advisory by City of Worcester and password change recommendations for users.

The case underscores how ongoing (system rebuild in progress; stolen data not yet found online), and recommending next steps like Users should change passwords if reused across other platforms, Organizations should ensure backup integrity and test restoration procedures and Multi-factor authentication (MFA) should be enforced for emergency notification systems, with advisories going out to stakeholders covering City of Worcester public announcement.

Finally, we try to match the incident with the MITRE ATT&CK framework to see if there is any correlation between the incident and the MITRE ATT&CK framework.

The MITRE ATT&CK framework is a knowledge base of techniques and sub-techniques that are used to describe the tactics and procedures of cyber adversaries. It is a powerful tool for understanding the threat landscape and for developing effective defense strategies.

Rankiteo's analysis has identified several MITRE ATT&CK tactics and techniques associated with this incident, each with varying levels of confidence based on available evidence. Under the Initial Access tactic, the analysis identified Valid Accounts (T1078) with moderate to high confidence (70%), supported by evidence indicating legacy CodeRED environment decommissioned post-breach, implying possible credential abuse and Exploit Public-Facing Application (T1190) with moderate confidence (60%), supported by evidence indicating legacy CodeRED environment targeted; no patch/vulnerability details but implies web-facing exploit. Under the Credential Access tactic, the analysis identified Unsecured Credentials: Credentials In Files (T1552.001) with moderate to high confidence (85%), supported by evidence indicating passwords stolen from CodeRED user profiles (likely stored in databases/files) and OS Credential Dumping (T1003) with moderate confidence (50%), supported by evidence indicating legacy system compromise *may* involve credential dumping (no direct evidence). Under the Collection tactic, the analysis identified Data from Local System (T1005) with high confidence (95%), supported by evidence indicating names, addresses, email addresses, phone numbers, and passwords exfiltrated from CodeRED. Under the Exfiltration tactic, the analysis identified Exfiltration Over Alternative Protocol: Exfiltration Over Unencrypted/Obfuscated Non-C2 Protocol (T1048.003) with moderate to high confidence (70%), supported by evidence indicating stolen data being sold by the hackers (implies transfer out via non-C2 channels) and Automated Exfiltration (T1020) with moderate confidence (60%), supported by evidence indicating large-scale data theft (PII/credentials) suggests automated collection/exfiltration. Under the Impact tactic, the analysis identified Data Encrypted for Impact (T1486) with high confidence (90%), supported by evidence indicating ransomware attack forced decommissioning of legacy infrastructure, Data Destruction (T1485) with moderate to high confidence (70%), supported by evidence indicating system rebuild required; some user accounts will be missing implies partial data loss, and Inhibit System Recovery (T1490) with moderate confidence (60%), supported by evidence indicating failed ransom negotiations + system rebuild from backups suggests recovery interference. Under the Defense Evasion tactic, the analysis identified Indicator Removal: File Deletion (T1070.004) with moderate confidence (50%), supported by evidence indicating legacy environment decommissioned (possible attacker cleanup or post-exploitation) and Impair Defenses: Disable or Modify Tools (T1562.001) with lower confidence (40%), supported by evidence indicating no direct evidence, but ransomware often disables security tools (implied by successful encryption). Under the Persistence tactic, the analysis identified Account Manipulation: Additional Cloud Roles (T1098.003) with moderate confidence (50%), supported by evidence indicating legacy cloud environment (CodeRED) may have had persistent access via compromised accounts. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.