This hunt hypothesis identifies adversaries actively exploiting the critical SAP NetWeaver vulnerability (CVE-2025-31324) by analyzing forensic artifacts that indicate successful exploitation attempts within the environment. Proactively hunting for these specific indicators in Azure Sentinel is essential to rapidly detect and contain potential breaches before attackers can establish persistence or exfiltrate sensitive data from this high-value enterprise asset.
rule APT_SAP_NetWeaver_Exploitation_Activity_Apr25_2 : SCRIPT {
meta:
description = "Detects forensic artefacts related to exploitation activity of SAP NetWeaver CVE-2025-31324"
reference = "https://reliaquest.com/blog/threat-spotlight-reliaquest-uncovers-vulnerability-behind-sap-netweaver-compromise/"
author = "Florian Roth"
date = "2025-04-25"
score = 70
id = "3b7d3f94-88a9-5686-8a23-ac4040c0e6c1"
strings:
$x03 = "MSBuild.exe c:\\programdata\\" ascii wide
condition:
filesize < 20MB and 1 of them
}
This YARA rule can be deployed in the following contexts:
This rule contains 1 string patterns in its detection logic.
Here are 5 specific false positive scenarios for the SAP NetWeaver CVE-2025-31324 detection rule, along with suggested filters and exclusions:
Scenario: Scheduled SAP Security Patching Jobs (SWPM)
sapup service creates temporary forensic logs and modifies specific registry keys in the NetWeaver directory that mimic the exploitation signatures of CVE-2025-31324.SWPM.exe or saphostctrl running under the system account (NT AUTHORITY\SYSTEM) during a defined maintenance window (e.g., 02:00–04:00 UTC).Scenario: SAP Solution Manager (SolMan) Diagnostic Scans
10.20.30.x) and the detected process name contains “SolManAgent” or “SAPLogon”.Scenario: Third-Party Backup Agents (Veeam/Commvault)