Cscript/Wscript Potentially Suspicious Child Process

detection:
  filter_main_rundll32_known_exports:
    CommandLine|contains:
      - 'UpdatePerUserSystemParameters'
      - 'PrintUIEntry'
      - 'ClearMyTracksByProcess'
    Image|endswith: '\rundll32.exe'
  selection_cli_script_main:
    Image|endswith:
      - '\cmd.exe'
      - '\powershell.exe'
      - '\pwsh.exe'
  selection_cli_script_option_mshta:
    CommandLine|contains|all:
      - 'mshta'
      - 'http'
  selection_cli_script_option_other:
    CommandLine|contains:
      - 'rundll32'
      - 'regsvr32'
      - 'msiexec'
  selection_cli_standalone:
    Image|endswith: '\rundll32.exe'
  selection_parent:
    ParentImage|endswith:
      - '\wscript.exe'
      - '\cscript.exe'
  condition: selection_parent and ( selection_cli_standalone or (selection_cli_script_main and 1 of selection_cli_script_option_*) ) and not 1 of filter_main_*

The rule’s detection, its selections and fields in order of name. The whole rule, with its references and false positives, is on SigmaHQ, by Nasreddine Bencherchali (Nextron Systems), Alejandro Houspanossian ('@lekz86'), under the Detection Rule License 1.1. CmdID evaluates it on a command line alone: a test on what a command line cannot show, such as the parent process or the user, is not met.

None of the everyday examples and documented commands on CmdID’s program pages trips it. To see whether a command line does, paste it into CmdID.