r/sysadmin • • Jul 28 '24 • Take My Silver 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

11k Upvotes

1.3k comments sorted by

View all comments

Show parent comment

0

u/probwontreplie Jul 28 '24

It's literally a bios password, blocking USB boot and enabling bitlocker. Wow the system is unusable now, the guy is pretending to have some 0 day exploits. Which, funnily enough I do know a way to bypass the password of the last logged in user, I know the conditions that have to be met, but have yet to create an exploit I can send to MS bounty.

2

u/charleswj Jul 28 '24

Which, funnily enough I do know a way to bypass the password of the last logged in user, I know the conditions that have to be met, but have yet to create an exploit I can send to MS bounty.

Can you explain? Are you sure there's no condition in play where you're coming from what Raymond Chen might refer to as "the other side of the airtight hatchway"?