Windows PowerShell Process Implementing Manual Base64 Decoder: endpointEndpointNoneversion:5
The following analytic identifies Windows PowerShell processes that implement a manual Base64 decoder.
Threat actors often use Base64 encoding to obfuscate malicious payloads or commands within PowerShell scripts.
By manually decoding Base64 strings, attackers can evade detection mechanisms that look for standard decoding functions like using the "-enc" flag or the "FromBase64String" function.
This detection focuses on PowerShell processes that exhibit characteristics of manual Base64 decoding, such as the presence of specific string manipulation methods and bitwise operations.
Security teams should investigate any instances of such activity, especially if found in conjunction with other suspicious behaviors or on systems that should not be using PowerShell for such tasks.
Windows Cmd Command Line With Encoded Character Sequences: endpointEndpointNoneversion:1
The following analytic detects cmd.exe command lines that contain long sequences of encoded characters, such as decimal values (12;70;18;...), hexadecimal values (0x41,0x42,...), HTML entities, or Unicode and octal escapes.
This activity is significant because loaders, including ClickFix payloads that retrieve commands through finger, hide their next stage as an index list that cmd.exe decodes at runtime using delayed variable expansion before launching PowerShell.
If confirmed malicious, this could lead to execution of a hidden payload, such as a download cradle with an AMSI bypass.
CertUtil With Decode Argument: endpointEndpointNoneversion:15
The following analytic detects the use of CertUtil.exe with the 'decode' argument, which may indicate an attempt to decode a previously encoded file, potentially containing malicious payloads. This detection leverages data from Endpoint Detection and Response (EDR) agents, focusing on command-line executions involving CertUtil.exe. This activity is significant because attackers often use CertUtil to decode malicious files downloaded from the internet, which are then executed to compromise the system. If confirmed malicious, this activity could lead to unauthorized code execution, further system compromise, and potential data exfiltration.
Windows CMD Evasive Patterns Through Native Commands: endpointEndpointNoneversion:1
The following analytic detects cmd.exe being used to evade defenses with nothing but built-in commands, a pattern frequently seen in ClickFix-style social engineering and malware loader activity.
Adversaries abuse native cmd.exe features such as call combined with variable assignment to assemble commands piece by piece, hiding the real payload from static inspection and string-based detections.
They also chain native utilities such as timeout and del to erase the dropped executable shortly after it has run, which removes evidence and complicates forensic analysis.
Because these techniques need no additional tooling, they let attackers blend into routine command shell activity.
If confirmed malicious, this could indicate a staged loader concealing its intent or cleaning up after execution.