How to manually obfuscate PowerShell scripts
Help the project grow with a Star or by following me on Github:
⭐ Repository ➡ github.com/t3l3machus/PowerSh...
⚡️ Please subscribe and connect:
GitHub ➡ github.com/t3l3machus
Twitter ➡ / t3l3machus
Linkedin ➡ / t3l3machus
💚 Respect on HackTheBox:
app.hackthebox.com/profile/87301
Пікірлер: 18
Great work! I'd like to get to know you and chat a bit sometimes.
Πολυ καλή παρουσίαση, έμαθα πολλά. Μπράβο!
Thanks Again for awesome content i am so glad i found you.
Very informative video.. Thanks 🌹
Awesome work!
Thanks for share this knowledge!
@HaxorTechTones
Жыл бұрын
Glad it was helpful!
thank you for sharing !!
nice sir
❤
good content ❤
@HaxorTechTones
Жыл бұрын
Thanks for watching!
более старая версия злодея, пожалуйста, я спрашивал вас раньше, И я спрашивал вас, прежде чем вы сказали, что скоро добавите его, но так и не сделали :(
i need your help
Is it reversible?
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.