How to manually obfuscate PowerShell scripts

[@bleuforcedz6727]

Very informative video.. Thanks 🌹

[@gosasdark6489]

Πολυ καλή παρουσίαση, έμαθα πολλά. Μπράβο!

[@Z0nd4]

Thanks for share this knowledge!

[@HaxorTechTones]

Glad it was helpful!

[@v1s1t0rs]

Thanks Again for awesome content i am so glad i found you.

[@andreadistasi8842]

Great work! I'd like to get to know you and chat a bit sometimes.

[@K20-h8f]

thank you for sharing !!

[@andrewlawrence1328]

Awesome work!

[@overthinker1877]

good content ❤

[@HaxorTechTones]

Thanks for watching!

[@AltaBross]

nice sir

[@NerdBigBird]

❤

[@AltaBross]

i need your help

[@novianindy887]

Is it reversible?

[@nyshone]

Interesting. Whenever I run &(gcm invok*-exp*), I get: 'Value cannot be null.Parameter name: key'. I have to do it like this for it to not error: &((gcm invok*-exp*).nAmE). Powershell version 5.1.22621.963, Windows 11 22H2

[@HaxorTechTones]

Interesting indeed. I'll double check that, thanks!

[@nyshone]

@@HaxorTechTones I've tested it on Windows 10 VM as well and it seems like the short version of the command only works there. From Windows 11 (can't really say which version) it requires the .Name parameter as well. But the .Name seems to work in both Win10 and Win11 luckily.