Static

Engineer was so sick of office pranks, he 'wiped' his antagonist's disk

First reported by The Register ·

The signal ●○○○ Compiled by AI from The Register, the single source so far
Why you might care

Office computer access has been restricted to prevent similar retaliatory data destruction.

What happened

An electrical engineering student, who goes by "Joe," detailed an act of revenge against a prank-loving colleague, "TF," at an Australian mobile carrier in the late 1990s. The office was rife with practical jokes, but TF's habit of startling Joe by roaring in his ear prompted Joe to plan a memorable retaliation. Joe waited until his final week on the job, with TF away at a conference, to execute his plan. He wrote a program using a Borland C compiler that mimicked an MS-DOS disk format operation, including flashing disk activity lights and writing junk data. The program was set to run via autoexec.bat but was programmed to delay its actual prank execution until a month after Joe's departure. Weeks later, Joe received a call from a colleague confirming the prank's success, with TF having been extremely alarmed by the apparent disk wipe.

What it means

This anecdote highlights the historical casualness around data security and access controls in the late 1990s, particularly in less formalized IT environments. The ease with which Joe could write and deploy a disk-wiping simulation, and have it persist through an autoexec.bat file, underscores a time before robust auditing, user privilege management, and strict access protocols were commonplace in many workplaces. It also points to a less regulated era where IT policies were likely more focused on functionality than on potential misuse, even for something as destructive as a simulated disk format.

While the story is an amusing anecdote about workplace pranks, it implicitly showcases the evolving landscape of digital security and workplace conduct. The actions described, though intended as a harmless prank simulation, would today trigger significant disciplinary action and likely legal consequences due to modern data protection laws and IT security policies. This historical context serves as a stark reminder of how far corporate IT security practices have come, emphasizing the importance of employee training, ethical conduct, and the technical safeguards now in place to prevent and detect unauthorized system access or data manipulation.

AI-written summary. May contain errors.

Engineer