SecOps SignalSecurity Intelligence Workspace
Collection Degraded30 / 46 Sources HealthyPublic Intel Only
KQL Library/Source hunting queryReference only
Record 3f40c0c5495dab6331d8bf7d · v1
Schema CheckedNot runtime validated

detect-cve-2019-1129-byebear-exploit

Source repository hunting query

Generation sourcesource-file · Limited verification
Attributionmicrosoft
Last updated12 Jul 2020, 05:23 PM IST
Last checked17 Oct 2026
View original guidance
Kusto query · 6 linesTable: DeviceProcessEvents · Microsoft Defender XDR / Sentinel
//Find possible use of ByeBear (CVE-2019-1129)DeviceProcessEvents | where ProcessCommandLine contains@"packages\Microsoft.MicrosoftEdge_8wekyb3d8bbwe"and ProcessCommandLine contains"/S /Q"and (ProcessCommandLine contains "rmdir" or ProcessCommandLine contains "del")

SecOps Signal does not execute queries against private telemetry. Paste the query into Microsoft Sentinel Log Analytics or Defender advanced hunting and review it first. Passed structure and schema checks; tenant execution is not verified.

Query anatomy

Static check against a reviewed column list

— This query has no final project stage to list.

“Listed” only means the column name appears in the reviewed list for that table. It does not confirm the column exists in your tenant's current schema, and per-column purposes are not recorded.

Hunting notes

MITRE ATT&CKNot mapped
Analytical purpose

Source repository hunting query

When to use

Review the source query and adapt it to your tenant before use.

Limitations

Schema checked only. This query has not been executed against a Sentinel or Defender tenant.