Currently viewing ATT&CK v7.2 which was live between July 8, 2020 and October 26, 2020. Learn more about the versioning system or see the live site.
Register to stream the next session of ATT&CKcon Power Hour November 12

Data Destruction

Adversaries may destroy data and files on specific systems or in large numbers on a network to interrupt availability to systems, services, and network resources. Data destruction is likely to render stored data irrecoverable by forensic techniques through overwriting files or data on local and remote drives.[1][2][3][4][5][6] Common operating system file deletion commands such as del and rm often only remove pointers to files without wiping the contents of the files themselves, making the files recoverable by proper forensic methodology. This behavior is distinct from Disk Content Wipe and Disk Structure Wipe because individual files are destroyed rather than sections of a storage disk or the disk's logical structure.

Adversaries may attempt to overwrite files and directories with randomly generated data to make it irrecoverable.[4][5] In some cases politically oriented image files have been used to overwrite data.[2][3][4]

To maximize impact on the target organization in operations where network-wide availability interruption is the goal, malware designed for destroying data may have worm-like features to propagate across a network by leveraging additional techniques like Valid Accounts, OS Credential Dumping, and SMB/Windows Admin Shares.[1][2][3][4][6]

ID: T1485
Sub-techniques:  No sub-techniques
Tactic: Impact
Platforms: Linux, Windows, macOS
Permissions Required: Administrator, SYSTEM, User, root
Data Sources: File monitoring, Process command-line parameters, Process monitoring
Impact Type: Availability
Version: 1.0
Created: 14 March 2019
Last Modified: 27 March 2020

Procedure Examples

Name Description
APT38

APT38 has used a custom secure delete function to make deleted files unrecoverable.[16]

BlackEnergy

BlackEnergy 2 contains a "Destroy" plug-in that destroys data stored on victim hard drives by overwriting file contents.[9][10]

Kazuar

Kazuar can overwrite files with random data before deleting them.[12]

Lazarus Group

Lazarus Group has used a custom secure delete function to overwrite file contents with data from heap memory.[17]

Olympic Destroyer

Olympic Destroyer overwrites files locally and on remote shares.[6]

PowerDuke

PowerDuke has a command to write random data across a file and delete it.[13]

Proxysvc

Proxysvc can overwrite files indicated by the attacker before deleting them.[14]

RawDisk

RawDisk was used in Shamoon to write to protected system locations such as the MBR and disk partitions in an effort to destroy data.[3][5]

Sandworm Team

Sandworm Team has used the BlackEnergy KillDisk component to overwrite files on Windows-based Human-Machine Interfaces. [18][19]

SDelete

SDelete deletes data in a way that makes it unrecoverable.[8]

Shamoon

Shamoon attempts to overwrite operating system files and disk structures with image files.[1][2][3] In a later variant, randomly generated data was used for data overwrites.[5][11]

StoneDrill

StoneDrill has a disk wiper module that targets files other than those in the Windows directory.[4]

Xbash

Xbash has destroyed Linux-based databases as part of its ransomware capabilities.[15]

Mitigations

Mitigation Description
Data Backup

Consider implementing IT disaster recovery plans that contain procedures for taking regular data backups that can be used to restore organizational data.[7] Ensure backups are stored off system and is protected from common methods adversaries may use to gain access and destroy the backups to prevent recovery.

Detection

Use process monitoring to monitor the execution and command-line parameters of binaries that could be involved in data destruction activity, such as SDelete. Monitor for the creation of suspicious files as well as high unusual file modification activity. In particular, look for large quantities of file modifications in user directories and under C:\Windows\System32\.

References