Windows Registry Modification: OracleOciLib/OracleOciLibPath Under MSDTC for oci.dll Redirection

Alerts on MSDTC MTxOCI registry changes to OracleOciLib/OracleOciLibPath that may redirect oci.dll loading to attacker-controlled locations.

FreeReviewedSigma · High · v1
Product
windows
Category
registry_set
Author
Swachchhanda Shrawan Poudel (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2026-01-24
Updated
2026-07-30

ATT&CK techniques

Execution → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Priv Esc

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule flags registry value changes targeting the MSDTC MTxOCI keys for OracleOciLib and OracleOciLibPath. Adversaries can use these modifications to redirect how oci.dll is loaded, supporting DLL hijacking and defense-impairment by pointing to unexpected locations. It relies on registry set telemetry that includes the TargetObject path and Details content, specifically looking for deviations from expected oci.dll and %SystemRoot%\System32-based values.

Related detections9 linkedT1112 — drag to rearrange
Windows Registry: DHCP Server Callout DLL and Enable Parameters Installation
Windows DNS ServerLevelPluginDll Registry Installation
Windows: Detect dnscmd.exe setting ServerLevelPluginDll to install DNS plugin DLL
DLL Side-Loading via Signed Binary Loading Known Malicious Helper DLL
Malicious Enabling of Restricted Admin Mode via Registry by UAT-8837
Suspicious Enabling of Remote Desktop via fDenyTSConnections Registry by DeadLock Ransomware
Malicious Service DLL Hijack for Persistence via Lotus Blossom
Suspicious Loopback Proxy Server Configured via Registry (via registry_set)
Malicious WDigest Credential Caching Enabled via Registry (via registry_set)
Windows Registry Modification: OracleOciLib/OracleOciLibPath Under MSDTC for oci.dll Redirection
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.