Suspicious Run Key Persistence Pointing to Test Executable via Registry Set

ATT&CK techniques

Persistence → Priv Esc

Recon
Resource Dev
Initial Access
Execution
Persistence
- T1547.001Registry Run Keys / Startup Folder
Priv Esc
- T1547.001Registry Run Keys / Startup Folder
Defense Evasion
Cred Access
Discovery
Lateral Movement
Collection
C2
Exfiltration
Impact

What it detects

This rule detects a CurrentVersion Run key being set to launch an executable dropped inside a Test subdirectory which is the autostart persistence used by the BLOODALCHEMY backdoor. A run key value referencing this staging path indicates malware establishing boot persistence.

Reporting behind it

Related detections9 linkedT1547.001 — drag to rearrange

Suspicious PowerShell Persistence via Registry Run Key

Possible SHELBY Backdoor Persistence via Run Key Referencing AppData HTTPApi

Malicious WmRAT Persistence via vcswin Run Key (via registry_set)

Malicious PlugX Persistence via LMIGuardian Update Run Key (via registry_set)

Malicious axios NPM Supply Chain Persistence via MicrosoftUpdate Run Key

Malicious Registry Run Key Persistence Masquerading as MicrosoftUpdate

Malicious Run Key Persistence Referencing DLL in User Documents

PlugX Persistence via Run Key Named AAM Updatevlm

Suspicious Autorun Registry Persistence via sausageLoop Run Key

Suspicious Run Key Persistence Pointing to Test Executable via Registry Set

Pivot detection · T1547.001 · 9 related

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.

Full detection rule

Unlock this rule to view and copy it

The detection logic is included with a plan. Everything else — context, mappings and implementation details — stays free on this page.

Sign in for 3 free unlocks

Signing in gives you 3 unlocks to spend on any rule in the library. No card, and they do not expire.

Also included

Unlocked rules convert on this page — to Splunk SPL or Splunk — Raw Index SPL or Microsoft Sentinel KQL or Microsoft Sentinel ASIM ASIM KQL or Microsoft Defender XDR KQL or Elastic Security KQL or Elastic Security Lucene or Elastic Security ES|QL or CrowdStrike Falcon CQL or SentinelOne PowerQuery or Palo Alto Cortex XDR XQL or Carbon Black Cloud Platform Search or Carbon Black EDR Process Search or Google Security Operations UDM Search or IBM QRadar AQL or Sumo Logic Cloud SIEM Rules expression or Rapid7 InsightIDR LEQL or Graylog Search or OpenSearch Lucene or OpenSearch PPL PPL or Grafana Loki LogQL or SQLite SQL or Zircolite SQLite — with the log-source profile the engine picked, the field map it used, and everything it could not express. Converting a rule you have unlocked costs no further credit.

See it run on a free rule →Convert your own rule →