Baltimore ransomware attack disrupts city services and drives major recovery costs
In May 2019, the City of Baltimore suffered a ransomware attack that disrupted municipal services such as property transactions and city systems. Public-sector testimony and reporting described substantial recovery expenses and prolonged disruption, illustrating the financial and operational impact ransomware can have on local government. The incident is commonly associated in public reporting with the “RobbinHood” ransomware family.
First reported May 7, 2019Ransomwaremed overall confidence
T1486: The incident involved ransomware encryption leading to service disruption and recovery efforts.
Mitigations
Now
Maintain offline/immutable backups and regularly test restoresEnables recovery without paying ransom and reduces business downtime when systems are encrypted or wiped.
Soon
Segment networks and restrict administrative privilegesSlows attacker movement and limits the blast radius of ransomware deployment across the enterprise.
Later
Harden endpoints/servers with EDR and restrict remote admin toolsImproves detection and blocking of ransomware behaviors and common lateral-movement mechanisms used to deploy payloads.
Detection ideas
Detect mass file encryption or destructive file operations
Alert on rapid renames/overwrites across many directories, creation of ransom notes, and high-entropy writes by unfamiliar processes.
Data sources: EDR telemetry, File integrity monitoring, Windows Security Event Logs
Detect lateral movement and remote execution used for ransomware deployment
Look for PsExec/SMB service creation, remote scheduled tasks, or WMIC usage followed by execution of the same binary on multiple hosts.
Data sources: EDR telemetry, Windows Security Event Logs, Network flow logs
