There are easier ways to do this without actively scripting it. Just build something that relies on your account, rather than scripting to check it in order to destroy things. Then you claim ineptitude, rather than malicious intent. It’s the “I forgot to create a service account” excuse.
Badass and stupid at the same time. How could you even think a script that looks for a specific name wouldn’t connect you to this.
The script that would delete itself after activating would be easy enough to write. Even better would be to install someone’s else virus that would erase the company’s hard drives along with your script, the company would not even try to blame you.
He should’ve done something like that on top of a delay in the script to prevent it from potentially being associated with the deletion of his name in AD (assuming the company backs stuff like that up, which is questionable since one dev was able to do all this lmao).
The other issue is that the computer responsible for the infinite looping was associated with him. Since he had seemingly unlimited access to everything, should’ve either plopped it on some shared device with a separate user or just configured it to also delete itself once it noticed the AD name being gone.
Anyway, this entire scenario is both hilarious and makes me never, ever want to use Eaton products.
