This detection identifies the presence of the HaspdongleAlladin malware, which adversaries may deploy to establish persistence or execute initial reconnaissance activities on endpoints. SOC teams should proactively hunt for this indicator in Azure Sentinel to uncover early-stage infections that might evade standard signature-based defenses and prevent potential lateral movement within the network.
rule HaspdongleAlladin
{
meta:
author="malware-lu"
strings:
$a0 = { 50 53 51 52 57 56 8B 75 1C 8B 3E [5] 8B 5D 08 8A FB [2] 03 5D 10 8B 45 0C 8B 4D 14 8B 55 18 80 FF 32 }
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.
Here are 3-5 specific false positive scenarios for the HaspdongleAlladin detection rule, along with suggested filters and exclusions tailored for an enterprise environment:
Scenario: Automated USB Dongle License Verification by Microsoft Office
HaspdTm.exe or AlladinService.exe frequently scans connected USB ports to validate licenses. This triggers the rule when the process enumerates device handles during peak login times.C:\Program Files\Aladdin\AlladinService.exe and C:\Program Files\Sentinel\haspdTm.exe from triggering this rule if the parent process is a known system service.Scenario: Scheduled IT Asset Inventory Scans
IvantiAgent.exe or LANDeskService.exe when they spawn child processes interacting with USB drivers between 01:00 and 05:00 local time.Scenario: Remote Desktop Session Initialization