← Back to SOC feed Coverage →

detect Datper in memory

yara LOW Yara-Rules
community
This rule was pulled from an open-source repository and enriched with AI. Validate in a test environment before deploying to production.
View original rule at Yara-Rules →
Retrieved: 2026-07-03T11:00:00Z · Confidence: medium

Hunt Hypothesis

This hypothesis posits that adversaries are executing the Datper malware directly within memory to evade traditional disk-based detection mechanisms. Proactively hunting for this behavior in Azure Sentinel is critical because identifying these ephemeral processes early allows the SOC team to isolate potential lateral movement before the threat establishes persistence or exfiltrates sensitive data.

YARA Rule

rule Datper {
          meta:
            description = "detect Datper in memory"
            author = "JPCERT/CC Incident Response Group"
            rule_usage = "memory scan"
            reference = "https://blogs.jpcert.or.jp/en/2017/08/detecting-datper-malware-from-proxy-logs.html"

          strings:
            $a1 = { E8 03 00 00 }
            $b1 = "|||"
            $c1 = "Content-Type: application/x-www-form-urlencoded"
            $push7530h64 = { C7 C1 30 75 00 00 }
            $push7530h = { 68 30 75 00 00 }

          condition: $a1 and $b1 and $c1 and ($push7530h64 or $push7530h)
}

Deployment Notes

This YARA rule can be deployed in the following contexts:

This rule contains 5 string patterns in its detection logic.

References

False Positive Guidance

Here are 4 specific false positive scenarios for the detect Datper in memory rule, including suggested filters or exclusions tailored for an enterprise environment:

Original source: https://github.com/Yara-Rules/rules/blob/main/malware/MalConfScan.yar