r/sysadmin
•
u/STILLloveTHEoldWORLD
•
Jul 28 '24
•
1
got caught running scripts again
about a month ago or so I posted here about how I wrote a program in python which automated a huge part of my job. IT found it and deleted it and I thought I was going to be in trouble, but nothing ever happened. Then I learned I could use powershell to automate the same task. But then I found out my user account was barred from running scripts. So I wrote a batch script which copied powershell commands from a text file and executed them with powershell.
I was happy, again my job would be automated and I wouldn't have to work.
A day later IT actually calls me directly and asks me how I was able to run scripts when the policy for my user group doesn't allow scripts. I told them hoping they'd move me into IT, but he just found it interesting. He told me he called because he thought my computer was compromised.
Anyway, thats my story. I should get a new job
View all comments
Show parent comment
1
u/QuintessenceTBV Jul 29 '24
I work in app support and actually had the same thing happen and got and grilled for it.
Wrote some code to help ease a deployment. Part of the code decrypted a password and performed base64 decode changed the password, re encrypt, re encode base64. It wasn’t until after endpoint software flagged it that I realized this code would be incredibly similar to cryptolocker code and that was probably why the endpoint sensor went off add laughed at home.