OMIGOD SCX RunAsProvider ExecuteScript
Rule to detect the use of the SCX RunAsProvider ExecuteScript to execute any UNIX/Linux script using the /bin/sh shell. Script being executed gets created as a temp file in /tmp folder with a scx* prefix. Then it is…
Description
Rule to detect the use of the SCX RunAsProvider ExecuteScript to execute any UNIX/Linux script using the /bin/sh shell. Script being executed gets created as a temp file in /tmp folder with a scx* prefix. Then it is invoked from the following directory /etc/opt/microsoft/scx/conf/tmpdir/. The file in that directory has the same prefix scx*. SCXcore, started as the Microsoft Operations Manager UNIX/Linux Agent, is now used in a host of products including Microsoft Operations Manager, Microsoft Azure, and Microsoft Operations Management Suite.
Detection logic
Detection requirements
- Platform
- ContainersESXiIaaSLinuxmacOSNetwork DevicesWindows
The rule states no platform. This is derived from the 3 ATT&CK techniques it maps to.
- Log source product
- linux
- Log source category
- process_creation
Known benign triggers
- Legitimate use of SCX RunAsProvider ExecuteScript.
MITRE ATT&CK mappings
0 exclusive techniques.This is coverage no other published rule has; it is not this rule's total technique count.
References
| Reference | Cited by |
|---|---|
| github.com/Azure/Azure-Sentinel/pull/3059 | 2 |
| www.wiz.io/blog/omigod-critical-vulnerabilities-in-omi-azure | 2 |
From the source
- At source
- Open at source
- Upstream identifier
- 6eea1bf6-f8d2-488a-a742-e6ef6c1b67db
- Tagged by the source as
- attack.executionattack.initial-accessattack.privilege-escalation
Licence
- Published under
- Detection Rule License 1.1Read the licence
- Attribution
- Required
Authorship
- Published
- Aug 26, 2026
- Version
- 1