CodeRED Emergency Alert System Crippled by 'Inc Ransom' Attack, Disrupting US Public Safety

Inc Ransom Attack on OnSolve Disables CodeRED Emergency Alert System Across the United States

HIGH
November 26, 2025
6m read
RansomwareCyberattackData Breach

Related Entities

Threat Actors

Products & Tech

Full Report

Executive Summary

A significant ransomware attack attributed to the Inc Ransom group has crippled the OnSolve CodeRED emergency notification system, a platform used by hundreds of local government and law enforcement agencies across the United States. The attack, which involved both data encryption and exfiltration, has forced the vendor to decommission the affected legacy platform, leading to widespread service disruptions. This incident highlights the vulnerability of critical public safety infrastructure to cyberattacks and the severe real-world consequences, as municipalities are left without a primary tool for issuing urgent alerts for events like natural disasters, active threats, and missing person reports. The attackers claim to have stolen user data after a ransom negotiation for $100,000 failed, escalating the incident from disruption to a significant data breach.


Threat Overview

The attack was initiated on November 1, 2025, when the Inc Ransom group claims to have first gained access to OnSolve's network. The ransomware payload was deployed on November 10, encrypting systems and disrupting the legacy CodeRED platform. On November 22, Inc Ransom publicly listed OnSolve on its data leak site, claiming responsibility and stating that negotiations with the vendor had failed.

The primary impact is the loss of a critical public communication channel for numerous communities. Local governments in states including Massachusetts, Colorado, Texas, Florida, and California have publicly acknowledged the outage. The compromised data includes sensitive Personally Identifiable Information (PII) of registered users, such as names, physical addresses, email addresses, phone numbers, and hashed passwords. Crisis24, OnSolve's parent company, has confirmed the data exfiltration and is in the process of migrating customers to a new, unaffected platform, but the transition has been disruptive.

Technical Analysis

The attack follows a typical double-extortion ransomware model. While the exact initial access vector has not been disclosed, it likely involved common methods such as phishing, exploitation of a public-facing vulnerability, or compromised credentials.

MITRE ATT&CK Techniques Observed or Inferred:

Impact Assessment

The operational impact is severe. The inability to issue emergency alerts poses a direct risk to public safety. For example, a community could be unable to warn residents of a fast-moving wildfire, a chemical spill, or an active shooter situation. This erodes public trust in emergency services and local government. Financially, OnSolve faces costs related to incident response, platform migration, potential regulatory fines for the data breach, and loss of revenue as frustrated customers consider alternative providers. Affected municipalities must scramble to find and implement replacement notification systems, incurring unexpected costs and creating a temporary gap in their emergency response capabilities. The breach of user PII also exposes affected individuals to risks of identity theft, phishing, and other forms of fraud.

IOCs

No specific Indicators of Compromise (IOCs) such as file hashes or C2 domains were provided in the source articles.

Cyber Observables for Detection

Security teams should hunt for TTPs associated with Inc Ransom and similar ransomware groups:

Type Value Description
command_line_pattern vssadmin.exe delete shadows /all /quiet Command to delete Volume Shadow Copies to prevent recovery.
process_name wmic.exe Often used for reconnaissance and lateral movement.
network_traffic_pattern Unusual large outbound data transfers to cloud storage providers or unknown IPs. Potential data exfiltration activity.
log_source Windows Security Event Logs Monitor for Event ID 4625 (failed logons) and 4624 (successful logons) from unusual sources.
file_name *.inc_ransom Default file extension used by Inc Ransom for encrypted files.

Detection & Response

  • EDR/XDR: Deploy and monitor EDR solutions to detect ransomware behaviors such as rapid file encryption, deletion of shadow copies (D3-PA: Process Analysis), and suspicious process execution from tools like PsExec or WMI.
  • Network Monitoring: Implement D3-NTA: Network Traffic Analysis to baseline normal traffic patterns and alert on anomalous outbound data flows that could indicate exfiltration. Pay close attention to traffic from critical servers to unfamiliar destinations.
  • Log Analysis: Centralize and analyze logs from critical systems. Look for patterns of failed and successful logins from unusual geo-locations or at odd hours. Monitor for the creation of new administrative accounts.
  • Canary Files: Place decoy files (honeypots) on file shares. Configure alerts to trigger if these files are accessed or encrypted, providing an early warning of a ransomware attack in progress (D3-DO: Decoy Object).

Mitigation

  • Backup and Recovery: Maintain immutable, offline backups of critical data and systems. Regularly test restoration procedures to ensure they are effective in a real-world incident.
  • Network Segmentation: Implement robust D3-NI: Network Isolation to separate critical infrastructure environments from corporate networks. Restrict east-west traffic to prevent attackers from moving laterally.
  • Access Control: Enforce the principle of least privilege. Implement strong password policies and mandate Multi-Factor Authentication (MFA) for all remote access, privileged accounts, and critical system logins.
  • Patch Management: Aggressively patch internet-facing systems and critical vulnerabilities, especially those known to be exploited by ransomware groups. Prioritize patching of VPN concentrators, firewalls, and remote access solutions.

Timeline of Events

1
November 1, 2025
Inc Ransom claims to have first gained access to OnSolve's systems.
2
November 10, 2025
Inc Ransom deploys file-encrypting ransomware on the CodeRED platform.
3
November 22, 2025
Inc Ransom lists OnSolve on its dark web leak site, claiming responsibility for the attack.
4
November 26, 2025
This article was published

MITRE ATT&CK Mitigations

Regularly patch software, especially on internet-facing systems, to prevent exploitation of known vulnerabilities.

Mapped D3FEND Techniques:

Segment networks to contain breaches and prevent lateral movement from less secure environments to critical systems.

Mapped D3FEND Techniques:

Enforce MFA on all remote access points, administrative accounts, and critical applications to prevent credential abuse.

Mapped D3FEND Techniques:

Implement strict controls over privileged accounts to limit their use and monitor for suspicious activity.

Mapped D3FEND Techniques:

D3FEND Defensive Countermeasures

In the context of the CodeRED ransomware attack, having a robust file restoration capability is the most critical recovery control. Organizations must implement a 3-2-1 backup strategy: three copies of data, on two different media, with one copy off-site and immutable or air-gapped. For a critical service like CodeRED, this means regular, automated backups of the application servers, databases, and user data. Restoration procedures must be tested quarterly at a minimum to validate data integrity and ensure recovery time objectives (RTOs) can be met. Since Inc Ransom also exfiltrates data, restoration alone is insufficient, but it is the only way to regain operational control without paying the ransom. The need to decommission the legacy platform suggests either backups were unavailable, corrupted, or the underlying infrastructure was too compromised to restore safely, underscoring the importance of testing and securing the backup environment itself.

To prevent an incident like the OnSolve breach from escalating, network isolation is a key strategic defense. The CodeRED platform should have been in a highly segmented network zone, isolated from the general corporate IT environment. This involves configuring firewalls and network access control lists (ACLs) to strictly limit communication to and from the CodeRED servers. Only specific, authorized systems should be able to communicate with the platform on designated ports and protocols. This would have made it significantly harder for attackers to move laterally from a potentially compromised entry point (like an employee workstation) to the critical emergency alert infrastructure. Post-incident, as Crisis24 migrates customers, they must build the new environment with a zero-trust architecture, assuming no implicit trust between network segments and enforcing strict verification for any access request.

The exfiltration of user data by Inc Ransom could have been detected or blocked with effective outbound traffic filtering. Critical servers, like those running CodeRED, should be subject to egress filtering rules that deny all outbound traffic by default, only allowing connections to known, legitimate destinations required for operations (e.g., specific update servers, partner APIs). By monitoring for large, unexpected data transfers or connections to suspicious IP ranges or cloud storage providers not used by the organization, security teams can create high-fidelity alerts for potential data theft. Implementing this on perimeter firewalls and web proxies can serve as a last line of defense to disrupt the 'double extortion' component of modern ransomware attacks, even if the initial intrusion is successful.

Sources & References

Article Author

Jason Gomes

Jason Gomes

• Cybersecurity Practitioner

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.

Threat Intelligence & AnalysisSecurity Orchestration (SOAR/XSOAR)Incident Response & Digital ForensicsSecurity Operations Center (SOC)SIEM & Security AnalyticsCyber Fusion & Threat SharingSecurity Automation & IntegrationManaged Detection & Response (MDR)

Tags

RansomwareInc RansomCodeREDOnSolveEmergency Alert SystemPublic SafetyData BreachDouble Extortion

📢 Share This Article

Help others stay informed about cybersecurity threats

Continue Reading