Malicious Encoded PowerShell: Detecting, Decoding & Modeling
The challenges and insights from dealing with this PS one-liner I usually start with a bit of motivational words but in this case I'm simply quoting the nice Threat Detection report Red Canary team (now, ZScaler ) published this year: "PowerShell's versatility and ubiquitousness minimize the need for adversaries to customize payloads or download overtly malicious tools on a target system." Note: Consider jumping to "How to detect encoded commands in logs?" for the technical discussion, regex...