This hunt targets adversaries deploying the specific Nanocore Remote Access Trojan (RAT) to establish persistent command-and-control channels and exfiltrate sensitive data from Azure workloads. Proactively hunting for this signature in Azure Sentinel is critical because early identification of this high-severity threat allows the SOC team to isolate compromised endpoints before lateral movement or data theft occurs.
rule Nanocore_RAT_Sample_2 {
meta:
description = "Detetcs a certain Nanocore RAT sample"
author = "Florian Roth"
score = 75
reference = "https://www.sentinelone.com/blogs/teaching-an-old-rat-new-tricks/"
date = "2016-04-22"
hash1 = "51142d1fb6c080b3b754a92e8f5826295f5da316ec72b480967cbd68432cede1"
strings:
$s1 = "U4tSOtmpM" fullword ascii
$s2 = ")U71UDAU_QU_YU_aU_iU_qU_yU_" fullword wide
$s3 = "Cy4tOtTmpMtTHVFOrR" fullword ascii
condition:
uint16(0) == 0x5a4d and filesize < 40KB and all of ($s*)
}
This YARA rule can be deployed in the following contexts:
This rule contains 3 string patterns in its detection logic.
Here are 5 specific false positive scenarios for the Nanocore RAT detection rule in an enterprise environment, along with targeted filtering strategies:
Scenario: Software Deployment via SCCM/Intune
System account or specific service accounts (e.g., svc-scmsvc) running under the C:\Program Files\Microsoft Configuration Manager\bin\ directory path, specifically during the defined maintenance window (e.g., Sundays 02:00–06:00 UTC).Scenario: Automated Backup Verification Jobs
Task Scheduler (svchost.exe or taskscheduler.exe) where the parent process is identified as a known backup service (e.g., Veeam Backup & Replication, Commvault) and the command line arguments contain specific flags like -verify-only.Scenario: Third-Party DLP Agent Initialization