This rule targets the execution of potentially obfuscated or packed executables that may indicate stealthy malware deployment or fileless attack techniques. Proactively hunting for these indicators helps the SOC team identify low-fidelity threats that might evade standard signature-based detections, ensuring early visibility into suspicious binary activity within the Azure environment.
rule EXEStealthv272
{
meta:
author="malware-lu"
strings:
$a0 = { EB 00 EB 2F 53 68 61 72 65 77 61 72 65 20 2D 20 }
condition:
$a0 at pe.entry_point
}
This YARA rule can be deployed in the following contexts:
This rule contains 1 string patterns in its detection logic.
dotnet.exe CLI tool during a standard .NET Core/5+ application build or publish process triggered by a CI/CD pipeline (e.g., Azure DevOps or GitHub Actions) on a build agent.
dotnet.exe, msbuild.exe, or vstest.console.exe, and the command line contains arguments like build, publish, or restore.kubectl command-line interface to deploy or manage Kubernetes workloads, where the binary is often distributed as a standalone executable that may match generic stealth or packing heuristics.
kubectl.exe or kubectl where the parent process is a known shell (cmd.exe, powershell.exe, bash.exe) and the command line starts with kubectl followed by standard verbs like apply, get, delete, or create.terraform.exe binary during infrastructure-as-code provisioning tasks, which is frequently downloaded as a standalone binary and may exhibit characteristics that trigger generic EXE stealth detections.
terraform.exe where the parent process is a shell or a CI/CD agent, and the command line contains standard Terraform commands such as plan, apply, init, or destroy.winget.exe (Windows Package Manager) tool to install or update software in a user session, which is a native Microsoft tool but may be flagged if its binary signature or path is not explicitly whitelisted in the YARA rule’s context.
winget.exe where the path is under `C:\Program Files\