Third-party Backup Files Deleted via Unexpected Process
Identifies the deletion of backup files, saved using third-party software, by a process outside of the backup suite. Adversaries may delete Backup files to ensure that recovery from a ransomware attack is less likely.
Elastic rule (View on GitHub)
1[metadata]
2creation_date = "2021/10/01"
3integration = ["endpoint", "sentinel_one_cloud_funnel"]
4maturity = "production"
5updated_date = "2026/05/04"
6
7[rule]
8author = ["Elastic"]
9description = """
10Identifies the deletion of backup files, saved using third-party software, by a process outside of the backup suite.
11Adversaries may delete Backup files to ensure that recovery from a ransomware attack is less likely.
12"""
13false_positives = [
14 "Certain utilities that delete files for disk cleanup or Administrators manually removing backup files.",
15]
16from = "now-9m"
17index = ["logs-endpoint.events.file-*", "logs-sentinel_one_cloud_funnel.*"]
18language = "eql"
19license = "Elastic License v2"
20name = "Third-party Backup Files Deleted via Unexpected Process"
21note = """## Triage and analysis
22
23### Investigating Third-party Backup Files Deleted via Unexpected Process
24
25Backups are a significant obstacle for any ransomware operation. They allow the victim to resume business by performing data recovery, making them a valuable target.
26
27Attackers can delete backups from the host and gain access to backup servers to remove centralized backups for the environment, ensuring that victims have no alternatives to paying the ransom.
28
29This rule identifies file deletions performed by a process that does not belong to the backup suite and aims to delete Veritas or Veeam backups.
30
31#### Possible investigation steps
32
33- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
34- Identify the user account that performed the action and whether it should perform this kind of action.
35- Contact the account owner and confirm whether they are aware of this activity.
36- Investigate other alerts associated with the user/host during the past 48 hours.
37- Check if any files on the host machine have been encrypted.
38
39### False positive analysis
40
41- This rule can be triggered by the manual removal of backup files and by removal using other third-party tools that are not from the backup suite. Exceptions can be added for specific accounts and executables, preferably tied together.
42
43### Related rules
44
45- Deleting Backup Catalogs with Wbadmin - 581add16-df76-42bb-af8e-c979bfb39a59
46- Volume Shadow Copy Deleted or Resized via VssAdmin - b5ea4bfe-a1b2-421f-9d47-22a75a6f2921
47- Volume Shadow Copy Deletion via PowerShell - d99a037b-c8e2-47a5-97b9-170d076827c4
48- Volume Shadow Copy Deletion via WMIC - dc9c1f74-dac3-48e3-b47f-eb79db358f57
49
50### Response and remediation
51
52- Initiate the incident response process based on the outcome of the triage.
53- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
54- Consider isolating the involved host to prevent destructive behavior, which is commonly associated with this activity.
55- Perform data recovery locally or restore the backups from replicated copies (Cloud, other servers, etc.).
56- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
57- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
58- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
59"""
60
61setup = """## Setup
62
63This rule is designed for data generated by [Elastic Defend](https://www.elastic.co/security/endpoint-security), which provides native endpoint detection and response, along with event enrichments designed to work with our detection rules.
64
65Setup instructions: https://ela.st/install-elastic-defend
66
67### Additional data sources
68
69This rule also supports the following third-party data sources. For setup instructions, refer to the links below:
70
71- [SentinelOne Cloud Funnel](https://ela.st/sentinel-one-cloud-funnel)
72"""
73
74references = ["https://www.advintel.io/post/backup-removal-solutions-from-conti-ransomware-with-love"]
75risk_score = 47
76rule_id = "11ea6bec-ebde-4d71-a8e9-784948f8e3e9"
77severity = "medium"
78tags = [
79 "Domain: Endpoint",
80 "OS: Windows",
81 "Use Case: Threat Detection",
82 "Tactic: Impact",
83 "Resources: Investigation Guide",
84 "Data Source: Elastic Defend",
85 "Data Source: SentinelOne",
86]
87timestamp_override = "event.ingested"
88type = "eql"
89
90query = '''
91file where host.os.type == "windows" and event.type == "deletion" and
92 (
93 /* Veeam Related Backup Files */
94 (
95 file.extension : ("VBK", "VIB", "VBM") and
96 not (
97 process.executable : ("?:\\Windows\\*", "?:\\Program Files\\*", "?:\\Program Files (x86)\\*") and
98 (process.code_signature.trusted == true and process.code_signature.subject_name : ("Veeam Software Group GmbH", "Veeam Software AG"))
99 )
100 ) or
101 /* Veritas Backup Exec Related Backup File */
102 (
103 file.extension : "BKF" and
104 not process.executable : (
105 "?:\\Program Files\\Veritas\\Backup Exec\\*",
106 "?:\\Program Files (x86)\\Veritas\\Backup Exec\\*"
107 )
108 )
109 ) and
110 not (
111 process.name : ("MSExchangeMailboxAssistants.exe", "Microsoft.PowerBI.EnterpriseGateway.exe") and
112 (process.code_signature.subject_name : "Microsoft Corporation" and process.code_signature.trusted == true)
113 ) and
114 not file.path : (
115 "?:\\ProgramData\\Trend Micro\\*",
116 "?:\\Program Files (x86)\\Trend Micro\\*",
117 "?:\\$RECYCLE.BIN\\*"
118 )
119'''
120
121
122[[rule.threat]]
123framework = "MITRE ATT&CK"
124[[rule.threat.technique]]
125id = "T1485"
126name = "Data Destruction"
127reference = "https://attack.mitre.org/techniques/T1485/"
128
129[[rule.threat.technique]]
130id = "T1490"
131name = "Inhibit System Recovery"
132reference = "https://attack.mitre.org/techniques/T1490/"
133
134
135[rule.threat.tactic]
136id = "TA0040"
137name = "Impact"
138reference = "https://attack.mitre.org/tactics/TA0040/"
Triage and analysis
Investigating Third-party Backup Files Deleted via Unexpected Process
Backups are a significant obstacle for any ransomware operation. They allow the victim to resume business by performing data recovery, making them a valuable target.
Attackers can delete backups from the host and gain access to backup servers to remove centralized backups for the environment, ensuring that victims have no alternatives to paying the ransom.
This rule identifies file deletions performed by a process that does not belong to the backup suite and aims to delete Veritas or Veeam backups.
Possible investigation steps
- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
- Identify the user account that performed the action and whether it should perform this kind of action.
- Contact the account owner and confirm whether they are aware of this activity.
- Investigate other alerts associated with the user/host during the past 48 hours.
- Check if any files on the host machine have been encrypted.
False positive analysis
- This rule can be triggered by the manual removal of backup files and by removal using other third-party tools that are not from the backup suite. Exceptions can be added for specific accounts and executables, preferably tied together.
Related rules
- Deleting Backup Catalogs with Wbadmin - 581add16-df76-42bb-af8e-c979bfb39a59
- Volume Shadow Copy Deleted or Resized via VssAdmin - b5ea4bfe-a1b2-421f-9d47-22a75a6f2921
- Volume Shadow Copy Deletion via PowerShell - d99a037b-c8e2-47a5-97b9-170d076827c4
- Volume Shadow Copy Deletion via WMIC - dc9c1f74-dac3-48e3-b47f-eb79db358f57
Response and remediation
- Initiate the incident response process based on the outcome of the triage.
- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
- Consider isolating the involved host to prevent destructive behavior, which is commonly associated with this activity.
- Perform data recovery locally or restore the backups from replicated copies (Cloud, other servers, etc.).
- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
References
Related rules
- Backup Deletion with Wbadmin
- Modification of Boot Configuration
- Potential Secure File Deletion via SDelete Utility
- Potential System Tampering via File Modification
- Volume Shadow Copy Deleted or Resized via VssAdmin