This detection rule identifies the presence of the Trickbot Banking Trojan, which adversaries deploy to steal financial credentials and establish persistent command-and-control channels within the network. Proactively hunting for this threat in Azure Sentinel is critical because early identification allows the SOC team to isolate compromised endpoints before lateral movement occurs, thereby mitigating potential data exfiltration despite the rule’s current low severity classification.
rule MALW_trickbot_bankBot : Trojan
{
meta:
author = "Marc Salinas @Bondey_m"
description = "Detects Trickbot Banking Trojan"
strings:
$str_trick_01 = "moduleconfig"
$str_trick_02 = "Start"
$str_trick_03 = "Control"
$str_trick_04 = "FreeBuffer"
$str_trick_05 = "Release"
condition:
all of ($str_trick_*)
}
This YARA rule can be deployed in the following contexts:
This rule contains 5 string patterns in its detection logic.
Here are 4 specific false positive scenarios for the Detects Trickbot Banking Trojan rule in an enterprise environment, including suggested filters and exclusions:
Endpoint Protection Scanning of Legacy Archives
.zip or .tar.gz) containing historical banking transaction logs. These archives often contain obfuscated scripts that mimic the packing techniques of Trickbot, triggering the detection during routine daily scans.MsMpEng.exe or Cortex.sys) when scanning files with extensions .zip, .tar, and .gz located in the \\EnterpriseShare\LegacyData\BankingLogs directory path.Scheduled Software Updates via SCCM
ccmexec.exe process when the file hash matches known SCCM deployment packages or when the parent process is TaskScheduler running the specific job “Nightly_Banking_Client_Update”.IT Admin Deployment of Internal Banking Tools
.exe wrapper for a reporting dashboard) to finance department workstations. The