The Missing File and the Smiling Intruder

JAMES WAS SMILING WEIRDLY WHEN HE LEFT MY CUBICLE TONIGHT

I saw the flicker of his phone screen reflected in the dark office window as he stood by my desk, long after everyone else had left. He paused, framed by the faint glow coming from the server room down the hall. The only sound was the low hum of distant machines.

My gut twisted. I thought he’d gone home hours ago; he always left before me. Why was he lingering? When I got back to my workspace, something felt off, a faint chemical smell hung in the air near my keyboard.

Then I saw it. A key project file, vital for tomorrow’s deadline, was gone. Not moved, just deleted. My stomach dropped like a stone hitting concrete. Only one person had been this close.

I found him by the elevators, pulling on his jacket, that unsettling smirk playing on his lips. “Did you… did you touch anything on my computer?” My voice was barely a whisper, raw with panic. He turned slowly, his eyes catching the faint light from the lobby.

He gave me that tight, unsettling smile and said, “Just checking something for you. Making sure everything’s perfect.” His breath smelled strongly of stale coffee and cheap mints as he spoke. The cold plastic of the mouse felt slick under my shaking hand as I rushed back. The bright glare of my monitor felt hostile.

Then my screen went black and the message read: ‘System Corrupted. Good luck.’

👇 Full story continued in the comments…The screen went black, the stark white text mocking me. ‘System Corrupted. Good luck.’ My hands flew to the tower, fumbling for the power button, praying for a reset to make it all disappear. Nothing. The hum from the server room suddenly felt sinister, like it was laughing at my helplessness. Hours of work, critical data, tomorrow’s presentation – all gone. The chilling smile James had given me replayed in my mind. He didn’t just delete a file; he nuked my machine.

Panic surged, hot and acidic in my throat. I grabbed my phone, dialing the emergency IT line, my fingers trembling. “My computer… it’s dead! System corrupted, a message… and a project file is gone!” I stammered, trying to piece together coherent sentences for the calm, late-night voice on the other end. He asked questions I couldn’t answer – was anyone else near my desk? What did I see? My mind flashed back to James, the phone screen flicker, the lingering smell.

Within minutes, a security guard and a senior IT technician, Ken, arrived, their faces serious. They looked at my dead screen, sniffed the air around my cubicle, and Ken started examining the tower and peripherals. “Definitely tampered with,” Ken murmured, pointing at something near the USB ports. “Looks like some kind of quick-acting corrosive residue here. And… the smell? Did you notice this before?” The chemical smell was stronger now that they were pointing it out, faintly acrid.

Security was already checking the exit logs and reviewing camera footage. James’s name came up immediately. He was still listed as ‘present’ in the system, but the guard confirmed he’d swiped out just after I saw him at the elevator. “Wait,” the guard said, looking closer at the footage from the 12th floor lobby. “He re-entered the building a little while later. Came back up? What the…”

Just then, a notification pinged on Ken’s tablet. “Found him,” he said grimly. “Security has him trying to access the main server room on the 7th floor. Says he was ‘checking ventilation’.”

They escorted me down. James was sitting in a small security office, looking far less smug now, flanked by two guards. When he saw me, his jaw tightened. “Just a little prank,” he mumbled, avoiding my gaze. “Got carried away.”

“A prank?” I echoed, my voice rising. “You deleted a vital file, corrupted my system, maybe damaged my hardware, and tried to access the server room? On deadline day? That’s not a prank, James, that’s sabotage!”

Ken spoke up. “The residue on her machine… and you were trying to get into the server room. What exactly were you trying to do, James?”

He finally looked up, his eyes darting between us. “Okay, fine! You’re always getting the best projects, always staying late… I just wanted to mess you up, slow you down. I deleted the file, then ran a script that corrupted her OS. The smell… it was from this.” He pulled a small, almost empty spray bottle from his pocket. “Just something to… make it look worse, I don’t know!” His voice was tight with desperation. “I was going to the server room to see if I could… I don’t know, maybe plant something else, make it look like an external hack. I didn’t think I’d get caught.”

My relief was immense, mixed with cold fury. It wasn’t random; it was malicious. Ken, meanwhile, had already started working. “Alright, the system corruption isn’t irreversible if he just ran a script. We can try a clean install and maybe recover the data from a partition James missed, or our nightly backup. The file though… you deleted it?”

James nodded, slumped in the chair. “Yeah. Sent it to the recycle bin, then emptied it. It’s gone.”

“Not necessarily,” Ken said, a flicker of determination in his eyes. “Sometimes residual data lingers. And we have system restore points, shadow copies… it’ll take time, but we’ll try everything.”

I left James with security and went back upstairs with Ken. The next few hours were a blur of diagnostics, data recovery attempts, and tense silence broken only by the click of keys and the hum of the server room that now sounded like hope instead of menace.

Just before dawn, Ken leaned back, rubbing his eyes. “Got it,” he said, a tired smile spreading across his face. “Found a shadow copy of the drive from before the corruption. The file… it was there. Restored it and your system from backup. You’re back online. A few things might be slightly out of date, but the project file is safe.”

A wave of exhaustion and profound relief washed over me. I looked at the resurrected document on my screen, pristine and terrifyingly important. James’s sabotage had failed. By the time the first rays of sun hit the office windows, the project file was secure on a network drive, and the story of James’s late-night escapade was spreading quietly through the company grapevine. He wouldn’t be smiling weirdly in this office ever again.