That’s not me. I never touched a single terminal after they walked me out. It was a Tuesday when the first crack in the hull appeared, and by Thursday, I was standing in the lobby with a cardboard box, watching the fish in the big tank swim in circles like they knew something I didn’t. It wasn’t supposed to end like this.
I spent eleven years building that infrastructure, layer by layer, until the whole thing hummed like a precision instrument. But then Preston came in, all “disruption” and “synergy” and other words that mean absolutely nothing when a Chinese botnet is hammering your firewall at 3:00 a. m. He hired Chase, some kid who built a Discord server with 10,000 members and thought that made him qualified to touch tier-one systems.
I walked into Preston’s office, all glass, no privacy. A security nightmare. He had his feet up on the desk, rolling a stress ball between his fingers. “Karen, we’re going a different direction with security,” he said, smiling like he’d just discovered fire.
“Chase here is a digital native. He understands the vibe of the modern threat landscape. ”
“He wants to put RGB lighting on the server racks, Preston,” I said. “He asked if we could route the cooling exhaust to heat the break room floor because his feet get cold.
”
“See, that’s the creative thinking we need. ”
I looked at Chase, who was nodding along like he could actually parse the conversation. His hoodie had a cartoon cat on it. The cat was wearing sunglasses.
“If we trust each other, the hackers can’t get in,” Chase said. It was the stupidest sentence I had ever heard in the English language. Einstein would have wept. “Give me one more week,” I said.
“Let me just stabilize the heartbeat check, and then you can… vibe all you want. ”
“Effective immediately,” Preston said, and that was that. It didn’t take long for the first crack to appear. Chase started on a simple task, updating a firmware package on a non-critical cluster.
Within an hour, he’d accidentally rebooted a node that was holding the load balancer for the entire client-facing portal. “It’s a social experiment,” he told the help desk when they called, confused. I heard about it from a friend who still worked there. “Karen, you wouldn’t believe it,” she said over coffee, her eyes wide.
“He just plugged his laptop into the internal network and started hitting keys. It’s chaos. ”
I didn’t say much. I just nodded, took a sip of my Earl Grey, and reminded myself to buy more dandelion extract for the garden.
While I was clearing out my desk, the announcement went out. Mandatory town hall. Preston stood in front of a screen, his face lit up like a kid in a candy store. “Karen has decided to pursue other opportunities,” he said, as if I had a choice.
Then he announced that Chase would be taking over the day-to-day operations of the security infrastructure, reporting directly to him. Six hours later, they touched the fiber lines. I got a text from a guy in the NOC, a quiet kid named David who still called me every time something went wrong, even though I was officially gone. “Karen, he’s trying to bind the root authority to his own key.
This is a federal contract. If he does this, we’re all in violation of 18 U. S. C.
1030. ”
I read it and felt a spike of genuine fear. That’s the kind of statute that comes with a gavel and a lot of orange. It protects government systems, and we were running classified subnets under the DoD’s umbrella.
If Chase touched that terminal with his gritty “hustler” energy, we wouldn’t just get fired. We’d be looking at the inside of a cell for a long time. “He says he can rewrite the kernel to ignore the check,” David texted back, and my stomach dropped. “He’s live-streaming it to his followers.
”
I sat on my porch, the cool night air doing nothing to calm the heat rising in my chest. I didn’t sabotage anything. I was a professional, and more importantly, I was a patriot. I wasn’t going to prison for these clowns.
I simply stopped holding the ceiling up. The heartbeat check was a system I designed myself, back when I cared about doing things right. It was a simple protocol: every tier-one terminal sent a silent ping to a redundant node every three minutes. If the heartbeat didn’t arrive, the system assumed the facility had been compromised.
And what does a system do when it’s compromised? It locks down. It kills the network. It makes sure no one, not even someone with all the wrong credentials, can get past the outer gate.
I didn’t need to be there to protect the system. I just needed to make sure that when the lights flickered, no one was left holding the bag. The first 24 hours were quiet. Then the texts started coming in, faster and faster, like distress signals from a sinking submarine.
“He asked for root access to the core firewall,” David wrote. “He’s threatening to quit if they don’t give it to him. ”
I typed back: “Tell them no. ”
“He says if he doesn’t get it, he’s going to stream a full network map to his followers.
”
I read that text and felt a spike of genuine fear. That was a breach of protocol so severe I didn’t even want to say it out loud. I looked at my phone for a long moment, then I used the secure line I’d kept in the back of my closet, the one Preston didn’t know about. The call connected to a cold voice on the other end.
“Miller,” it said. “I’m initiating a level four audit,” I said. “I’m telling you now, you need to secure the perimeter. They’re touching the wrong things.
”
There was a pause, a long, heavy pause. Miller was a man of few words, but when he spoke, it was like hearing gravel shift. “You’re saying the system is compromised? ”
“Not yet.
But it will be. They’re rewriting the kernel on a live DoD server. The intrusion detection system will interpret that as a hostile foreign attack and initiate the emergency failsafe. ”
“How long?
”
“Four hours,” I said. “Maybe less. ”
Another pause. Then Miller said, “Secure line, stay there.
Do not, I repeat, do not contact the company. I’m on my way. ”
I stayed where I was, sitting in the quiet of my kitchen, the echo of a dead man’s word hanging in the air. I didn’t pack a bag.
I didn’t call anyone. I just sat and watched the clock on the wall tick. And then, at 7:42 p. m.
, I saw the notification. A pop-up in a corner of my screen, a signal from the redundant system I’d built. It showed a live stream: “@chasecyberking late night grind rewriting some legacy spaghetti code to free the data. ”
I clicked it.
There he was, front and center, the idiot in the hoodie, grinning into a webcam with a view of the server room behind him. The title of the stream was “crisis management earl saving the data from the haters. ”
I didn’t laugh. I just watched.
Because I knew what came next. The clock on the wall read 7:47 when the first alarm sounded through the livestream. I saw the white gas blast out of the rack, engulfing the two consultants who were standing next to Chase, their mouths open in confusion. Then I saw the lights flicker, and the screen went dead.
I sat back in my chair, picked up my teacup, and watched the timestamp tick over to 7:48. The system had locked down. The network was dark. The data was safe.
Miller called me three hours later. “It’s done,” he said. “We got there just in time. The handshake is broken, but we can restore it.
We just need someone who knows the original architecture. ”
“You need the original architect,” I said. “Yes. ”
I didn’t answer.
Not yet. I just set down the teacup, looked out the window at the moon hanging low over the empty field behind my house, and let the silence stretch. The system was locked tight. The data was safe.
But the real story wasn’t over. Not by a long shot.
