<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Powershell on Suspicious Bytes</title><link>/en/tags/powershell/</link><description>Recent content in Powershell on Suspicious Bytes</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 12 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="/en/tags/powershell/index.xml" rel="self" type="application/rss+xml"/><item><title>Triaging Suspicious PowerShell</title><link>/en/posts/triaging-suspicious-powershell/</link><pubDate>Tue, 12 May 2026 00:00:00 +0000</pubDate><guid>/en/posts/triaging-suspicious-powershell/</guid><description>&lt;p&gt;An encoded PowerShell command in your process logs is not automatically malicious,
but it always deserves a closer look. Here is how to triage one calmly.&lt;/p&gt;
&lt;h2 id="what-raises-the-flag"&gt;What raises the flag&lt;/h2&gt;
&lt;p&gt;Certain flag combinations are unusual for a legitimate script and common for
tradecraft:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;-EncodedCommand&lt;/code&gt; (base64 payloads)&lt;/li&gt;
&lt;li&gt;&lt;code&gt;-WindowStyle Hidden&lt;/code&gt; and &lt;code&gt;-NonInteractive&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;-ExecutionPolicy Bypass&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;blockquote&gt;
&lt;p&gt;Decoding a payload is reading, not running. Decode in an isolated environment and
never paste an unknown command back into a live shell.&lt;/p&gt;</description></item></channel></rss>