A lesser-known event log I recently found for tracking malicious AppX installations is the "Microsoft-Windows-AppXDeploymentServer/Operational". Here are a couple of ways how you can leverage it with some free SIGMA rules at the end. 🧵
EID 401 with ErrorCode "0x80073cff" (related to policy errors). This could indicate an attempt of installing unsigned packages that perhaps require sideloading to be enabled.
You can also use EID 400/401 with the field name "PackageFullName" similar to a hash. To potentially track known malicious package installations/attempts.
EDRs/AVs sometimes trust certain locations or perform certain behavior when met with unexpected weirdness. Here are some ideas to check/test for, the next time you have some alone time with your solution
1/🧵
-EDRs often times are configured to send telemetry via a pulling mechanism or via batches that can't exceed certain sizes per X time. Generating a lot of benign events before starting the attack could temporarily blind the EDR console
2/
-Execution from the AV install/data location (programfiles/programdata) could be whitelisted by default
-Files exceeding a certain size or executed from certain depths might not get scanned
-A full "C:\" partition could yield weird behavior for an EDR/AV
3/