28 organizations
Ransomware attacks continue at an alarming pace, with daily reporting from March 17, 2026, documenting 28 new victims posted to various data leak sites. The LockBit ransomware group, despite recent law enforcement disruption, has maintained its high operational tempo, claiming six of the new victims. Other highly active groups during this period include APT73 and Medusa, each claiming four victims. The data shows a consistent focus on the Professional Services industry and organizations based in the United States. The attacks also impacted critical public services, with the Philippine government's Department of Public Works and Highways, Cape May County (U.S.), and the Florida East Coast Railway all appearing on leak sites, highlighting the indiscriminate and widespread nature of the ransomware threat.
The 24-hour snapshot reveals a vibrant and multi-faceted ransomware ecosystem. The key takeaways are:
Dpwh.gov.ph, Cape May County) and transportation entities (Florida East Coast Railway) underscores the persistent threat to essential services.The report also noted the use of advanced evasion techniques. The Warlock ransomware group was observed using "Bring Your Own Vulnerable Driver" (BYOVD) tactics. This involves using legitimate, but vulnerable, software drivers to gain kernel-level privileges, allowing the ransomware to disable or bypass security products like EDR and antivirus software. This technique is associated with T1562.001 - Disable or Modify Tools.
While specific TTPs for each of the 28 attacks are not detailed, the general ransomware attack chain typically involves the following stages:
For each of the 28 victims, the impact is severe, involving significant operational disruption, financial costs for recovery and remediation, and reputational damage. For victims like the Florida East Coast Railway, the disruption could impact supply chains. For government agencies like Dpwh.gov.ph and Cape May County, it disrupts public services and erodes citizen trust. The Professional Services firms face the added risk of litigation from clients whose data was exposed.
| Type | Value | Description | Context | Confidence |
|---|---|---|---|---|
| process_name | vssadmin.exe delete shadows |
A common command used by ransomware to delete volume shadow copies and prevent easy restoration. | Endpoint command line logging (Event ID 4688) | high |
| file_name | Ransom notes (e.g., Restore-My-Files.txt) |
The appearance of ransom notes in multiple directories is a definitive sign of an active infection. | File Integrity Monitoring, EDR | high |
| network_traffic_pattern | Large outbound data flows to unknown destinations | Indicates data exfiltration prior to encryption. | Netflow, Firewall logs, IDS/IPS | medium |
| event_id | 4625 | A high volume of failed login attempts (Event ID 4625) can indicate brute-force or password spraying attacks for lateral movement. | Windows Security Event Log | medium |
Enforcing MFA on all remote access points and privileged accounts is a critical defense against initial access and lateral movement.
Mapped D3FEND Techniques:
Segmenting networks can contain a ransomware outbreak and prevent it from spreading to critical systems.
Mapped D3FEND Techniques:
Patching internet-facing systems removes the initial access vectors that many ransomware groups exploit.
Mapped D3FEND Techniques:
Modern EDR and antivirus solutions can detect and block ransomware based on behavioral patterns, even for unknown variants.
To detect and respond to ransomware like LockBit or Medusa at an early stage, deploy File Content Rules via a File Integrity Monitoring (FIM) or EDR solution. Configure rules to monitor for the creation of files with known ransomware note filenames (e.g., Restore-My-Files.txt, !!!READ_ME!!!.txt). Also, create rules to detect the mass renaming of files with known ransomware extensions (e.g., .lockbit). Most importantly, create 'canary' files (e.g., _DO_NOT_TOUCH_THIS_FILE.docx) in key directories on file servers. Any modification to these canary files should trigger a high-priority alert and an automated response, such as isolating the host that made the change. This provides a high-fidelity, early warning that an encryption process has begun, allowing for rapid containment before widespread damage occurs.
To counter the 'Bring Your Own Vulnerable Driver' (BYOVD) technique used by groups like Warlock, organizations should implement Driver Load Integrity Checking. This can be achieved using advanced EDR solutions or application control technologies that are configured to enforce strict driver signing policies. Maintain an allowlist of known, legitimate drivers required for business operations. Any attempt to load a driver that is not on this list, or a driver that is known to be vulnerable, should be blocked and trigger an immediate security alert. This prevents the attacker from loading the vulnerable driver they need to escalate privileges and disable security controls, effectively breaking a critical link in their attack chain.

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.
Help others stay informed about cybersecurity threats