This is an automated archive made by the Lemmit Bot.
The original was posted on /r/maliciouscompliance by /u/dvdmaven on 2025-03-09 01:04:46+00:00.
I was working at a major equipment manufacturer as a sys admin. One day, a salesman came charging into the admin area yelling about his report not printing. So I called up the spooler and saw a huge (140 MB) print job clogging the queue. This was back in the days of text-based everything, the report would have been thousands of pages long. I told him what the problem was and he told me to kill the big print job, as he HAD to get his report out. I killed it.
About 10 minutes later he was back saying his report had vanished. I said, you told me to kill it. Do you think I would have killed someone else's print job on your command? He got a bit upset, so I called up his keyboard logger (which he didn't know about). I looked at the SQL command and said, you were trying to print out every sale every person made for the last five years. He wanted me to fix it, but as a sys admin, I did not have access to do anything to the Oracle database except run the nightly backups. Go see a database admin.
Got a call from the lead database admin asking why the salesman had command line access to the database. I had no idea, but I called up the keyboard logger for the salesman and said, He's logged in as [DBA who left the company] Oops! The account was killed and the salesman got fired.