CommentCrew-threat-apt1 detects potential adversary behavior involving suspicious comment creation or modification in Azure resources, which may indicate reconnaissance or persistent access. SOC teams should proactively hunt for this behavior to identify early-stage compromise attempts that evade traditional detection methods.
YARA Rule
rule APT1_WEBC2_BOLID
{
meta:
author = "AlienVault Labs"
info = "CommentCrew-threat-apt1"
strings:
$vm = "VMProtect" wide ascii
$http = "http://[c2_location]/[page].html" wide ascii
condition:
all of them
}
This YARA rule can be deployed in the following contexts:
This rule contains 2 string patterns in its detection logic.
Scenario: Scheduled system backup using Veeam Backup & Replication
Filter/Exclusion: process.name != "vbm.exe" OR process.name != "vagent.exe"
Scenario: Administrative task to update Microsoft SQL Server via SQL Agent job
Filter/Exclusion: process.name != "sqlservr.exe" OR process.name != "sqlagent.exe"
Scenario: User running PowerShell script to generate reports using Power BI
Filter/Exclusion: process.name != "powershell.exe" OR process.name != "mspaint.exe"
Scenario: IT team performing Windows Update via Group Policy or WSUS
Filter/Exclusion: process.name != "wuauclt.exe" OR process.name != "msiexec.exe"
Scenario: Database administrator using MySQL Workbench to perform routine maintenance
Filter/Exclusion: process.name != "mysql.exe" OR process.name != "mysql-workbench.exe"