Detecting Windows file extension abuse
Attackers can make users run malicious code or persist on an endpoint by targeting file extensions that users are familiar with. For example, if users see that a file ends in .doc or .docx, they will assume that it is a Microsoft Word document and expect that double-clicking will open it using winword.exe. The user will typically also assume that the .docx file is safe. Attackers take advantage of this expectation by obfuscating the true file extension.
This use case helps you detect this type of abuse of file extensions and Windows file associations by searching for the execution of files with multiple extensions in the file name, a common technique used by attackers to obscure the true file extension.
Required data
- Normalized endpoint data that records process activity from your hosts. For information on installing and using the CIM, see the Common Information Model documentation.
How to use Splunk software for this use case
Next steps
These Splunk resources might help you understand and implement this use case: