This rule detects the presence of Mingw-w64 GCC V3X compiler artifacts, which adversaries often use to compile native Windows executables from C/C++ source code to establish a foothold or deploy custom tooling. Proactively hunting for these signatures allows the SOC team to identify potentially stealthy, custom-built malware or backdoors that may lack distinct behavioral indicators or known hash values in the Azure Sentinel environment.
rule MingWin32_GCC_V3X: PEiD
{
strings:
$a = { 55 89 E5 83 EC 08 C7 04 24 ?? 00 00 00 FF 15 ?? ?? 40 00 E8 ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? 55 ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? 00 }
condition:
$a at pe.entry_point
}
This YARA rule can be deployed in the following contexts:
This rule contains 1 string patterns in its detection logic.
mingw32-gcc toolchain to generate Windows executables.
javac.exe or ant.exe, or filter by command-line arguments containing -o and .exe extensions in developer-specific directories (e.g., C:\Users\*\.m2\repository\).gcc.exe or g++.exe as part of a Docker container or virtual machine setup for cross-compilation.
C:\jenkins\workspace\, C:\agent\_work\), or filter by service accounts associated with build agents (e.g., svc-build, ci-runner).C:\Program Files\Epic Games\, C:\Program Files\Unity\) or where the working directory contains keywords like Plugins, Mods, or NativeCode.git.exe, svn.exe) or a build system (`make