This hunt hypothesis targets adversaries executing NoodleCrypt ransomware variants that actively target and encrypt critical files within the environment. Proactively hunting for this behavior in Azure Sentinel is essential to identify early-stage encryption activities before they escalate into widespread data unavailability and operational disruption.
rule NoodleCryptv20
{
meta:
author="malware-lu"
strings:
$a0 = { EB 01 9A E8 3D 00 00 00 EB 01 9A E8 EB 01 00 00 EB 01 9A E8 2C 04 00 00 EB 01 }
$a1 = { EB 01 9A E8 ?? 00 00 00 EB 01 9A E8 [2] 00 00 EB 01 9A E8 [2] 00 00 EB 01 }
condition:
$a0 at pe.entry_point or $a1
}
This YARA rule can be deployed in the following contexts:
This rule contains 2 string patterns in its detection logic.
Here are 5 specific false positive scenarios for the NoodleCryptv20 detection rule, including suggested filters and exclusions:
Scenario: Automated Backup Encryption by Veeam Agent
.vbk and .vlt files) using AES-256. This process involves rapid file creation and modification patterns that mimic the initial encryption phase of NoodleCrypt ransomware, triggering the YARA rule on the VeeamService.exe process.VeeamService.exe (or AgentService.exe) running under the SYSTEM or specific service account context. Alternatively, exclude file paths matching C:\ProgramData\Veeam\BackupRepository\*.Scenario: Microsoft Defender Antivirus Cloud Protection Scan
Documents, Desktop). The heuristic engine creates temporary encrypted cache files and modifies file headers to verify integrity. These operations generate the specific byte sequences and entropy spikes that NoodleCryptv20 identifies as ransomware encryption behavior.Microsoft Defender Antivirus Service or process ID matches the known PID of MsMpEng.exe. Additionally, exclude file extensions commonly used by Defender’s temporary cache (e.g., .tmp, .cache).Scenario: Scheduled Database Maintenance via SQL Server Agent
sqlservr.exe process writing large, compressed binary