This YARA rule targets specific memory patterns associated with the Imploder malware family, indicating potential in-memory execution or obfuscated code injection techniques. Proactively hunting for these signatures allows the SOC team to identify low-severity, stealthy threats that may evade traditional network-based detections before they establish persistence or escalate privileges.
rule Imploderv104BoBBobSoft
{
meta:
author="malware-lu"
strings:
$a0 = { 60 E8 A0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 36 [3] 2E [3] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00 80 00 00 00 00 4B 65 72 6E 65 6C 33 32 2E 44 }
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.
BobSoft suite (e.g., BobSoft Office or BobSoft DataSync) is a legacy enterprise application that uses a custom, non-standard update mechanism. When the BobSoftUpdater.exe service runs its scheduled monthly patch cycle, it may write temporary configuration blobs or use specific memory patterns that match the Imploderv104 signature.
Image is C:\Program Files\BobSoft\BobSoftUpdater.exe and ParentImage is services.exe or svchost.exe.Imploderv104 byte sequence (perhaps as part of a test corpus or a corrupted document), the YARA rule may match the AV process’s memory space or the temporary file handle.
Image is C:\Program Files\Trellix\Trellix.exe or C:\Program Files\CrowdStrike\FalconSensor.exe and the ProcessName is FalconSensor.exe or Trellix.exe.BobSoft client application. When they attach the debugger and step through the Imploderv104 module, the debugger process (devenv.exe or dbghelp.dll) may hold the module in memory in a way that triggers the YARA signature, especially if the rule is sensitive to debug flags or specific register states.
*