Tag
Defense Evasion via WSL Enablement using DISM
1 rule 1 TTPAdversaries may attempt to enable the Windows Subsystem for Linux (WSL) using the legitimate DISM utility to facilitate the execution of Linux-based tools and bypass Windows-specific security controls.
Potential Hijacking of Windows Subsystem for Linux via Registry Modification
1 rule 2 TTPsAdversaries can gain persistence and perform proxy execution by modifying the WSL InstallLocation registry key to redirect binary execution to malicious payloads.
Suspicious WSL Binary Hijack via Proxy Execution
1 rule 2 TTPsAdversaries can achieve stealthy code execution by modifying the Windows WSL InstallLocation registry key to redirect the System32 wsl.exe stub to a malicious binary.
Windows Subsystem for Linux Binary Hijacking
1 rule 2 TTPsAdversaries may modify the wsl.exe binary within its installation directory to facilitate proxy execution and achieve defense evasion.
Windows Subsystem for Linux Distribution Installation via Registry Modification
2 rules 3 TTPsDetects the installation of a new Windows Subsystem for Linux (WSL) distribution through registry modifications, which can be leveraged by attackers to evade security measures and execute malicious activities on Windows systems.
Windows Subsystem for Linux Enabled via Dism Utility
2 rules 1 TTPAdversaries may enable Windows Subsystem for Linux (WSL) via the Dism utility to evade detection by running Linux tools on Windows.
Windows Subsystem for Linux Distribution Installed via Registry Modification
2 rules 3 TTPsThis rule detects registry modifications indicative of a new Windows Subsystem for Linux (WSL) distribution installation, a technique adversaries may leverage to evade detection by utilizing Linux environments within Windows.
Windows Subsystem for Linux Enabled via Dism Utility
2 rules 1 TTPAdversaries may enable and use Windows Subsystem for Linux (WSL) using the Microsoft Dism utility to evade detection on Windows systems by running Linux applications and tools.
Potential Defense Evasion via WSL Child Processes
2 rules 2 TTPsAdversaries may attempt to evade detection by executing malicious commands or scripts through child processes spawned from the Windows Subsystem for Linux (WSL), potentially bypassing traditional Windows-based security monitoring.
Host File System Changes via Windows Subsystem for Linux
2 rules 2 TTPsThis rule detects file creation and modification on the host system from the Windows Subsystem for Linux (WSL), potentially indicating defense evasion by adversaries.
Execution via Windows Subsystem for Linux
2 rules 2 TTPsThis detection identifies attempts to execute programs from the Windows Subsystem for Linux (WSL) to evade detection by flagging suspicious executions initiated by WSL processes and excluding known safe executables.
Detection of Kali Linux Installation or Usage via Windows Subsystem for Linux (WSL)
2 rules 1 TTPAdversaries may attempt to install or use Kali Linux via Windows Subsystem for Linux (WSL) to avoid detection, potentially enabling them to perform malicious activities within a Windows environment while blending in with legitimate WSL usage.
Suspicious Execution via Windows Subsystem for Linux
2 rules 3 TTPsThis rule detects suspicious execution via the Windows Subsystem for Linux (WSL), which adversaries may leverage to execute Linux commands and bypass traditional Windows security measures.