<feed xmlns="http://www.w3.org/2005/Atom"><title>powershellmanager</title><id>https://evotec.xyz/de/tags/powershellmanager/index.atom.xml</id><updated>2020-08-28T15:39:28.0000000Z</updated><subtitle>Evotec Main Website</subtitle><link href="https://evotec.xyz/de/tags/powershellmanager" /><link href="https://evotec.xyz/de/tags/powershellmanager/index.atom.xml" rel="self" type="application/atom+xml" /><entry><title>Restoring (Recovering) PowerShell Scripts from Event Logs</title><id>https://evotec.xyz/de/blog/restoring-recovering-powershell-scripts-from-event-logs</id><link href="https://evotec.xyz/de/blog/restoring-recovering-powershell-scripts-from-event-logs" /><updated>2020-08-28T15:39:28.0000000Z</updated><summary>A few days ago, I was asked to take a look at PowerShell Malware. While I don’t know much about malware, my curiosity didn’t let me skip on this occasion, and I was handed over WindowsPowerShell.evtx file. Ok, that’s not what I expected! I wanted PowerShell .ps1 files that I can read and assess? Well, you play with the cards you were dealt with. What I was handed over was PowerShell Event Log. PowerShell writes whatever you execute, and it thinks it is risky, to Windows PowerShell Operation Event Log.</summary><category term="event log" /><category term="get-events" /><category term="powershell" /><category term="powershellmanager" /><category term="pseventviewer" /><category term="Windows" /></entry></feed>