Suspicious Office VBA Object Model Access Enabled via Registry (via registry_set)

PremiumReviewedSigma · Medium · v1
Category
registry_set
Author
HuntRule
Published
2026-10-26
Updated
2026-10-26

ATT&CK techniques

Persistence → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Priv Esc

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule detects a Word macro enabling programmatic access to the VBA object model by setting AccessVBOM in the Office Security registry key. This technique is used in the Double-Tap campaign linked to APT28 to allow further malicious VBA execution and lower macro security. Enabling AccessVBOM is a strong indicator of malicious document activity because legitimate users rarely toggle this setting.

Related detections9 linkedT1112 — drag to rearrange
Suspicious PowerShell Payload Staging in HKCU Printers Registry Key
Suspicious Rootkit Configuration Registry Keys (via registry_set)
Suspicious Disabling of Chromium App-Bound Encryption via Policy Registry Key (via registry_set)
Windows reg.exe Registry Tampering of Internal Tool and Explorer Policy Settings (T1112)
Suspicious Disabling of Restricted Admin Mode via Registry (via registry_set)
Malicious WDigest UseLogonCredential Enabled for Cleartext Credential Theft (via registry_set)
Suspicious ClickFix RunMRU Entry Recording LOLBIN Command from Run Dialog
Suspicious Access to Chrome Encrypted Preference MAC Registry Values (via registry_set)
Suspicious Flax Typhoon Network Level Authentication Disabled via Registry (via registry_set)
Suspicious Office VBA Object Model Access Enabled via Registry (via registry_set)
Pivot detection · T1112 · 9 related

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