Zero nine

Chapter 13 - Counter-Strike in the Dark

Z

I did not plug the black drive into the lab's main network. Instead, I moved Preston upstairs to my small apartment, handed him a dry change of clothes and a bowl of hot stew, and instructed him to stay away from the windows. Then, I went down to the basement workshop where I maintained a completely isolated, air-gapped terminal—a machine with zero wireless capabilities and no physical connection to the external internet.

I inserted the steel drive into the air-gapped machine and initiated a deep hex-level forensic audit.

As the terminal's green phosphor lines scrolled across the black screen, the sheer malevolence of the payload revealed itself. It was not simple commercial malware. It was a weaponized worm designed by high-level cyber-mercenaries, specifically configured to latch onto the unique algorithmic handshakes of the Holloway quantum protocol. If injected into the satellite feed, it would have systematically corrupted the cryptographic hashes, creating a subtle vulnerability that would allow Apex Horizon to decrypt global banking communications while framing the Holloway Foundation for systemic protocol failure.

Apex Horizon wasn't just a rogue venture firm; they were a corporate front financed by the former institutional creditors who had lost hundreds of millions when Sterling Dominion collapsed. Unable to sue through the courts, they were attempting to orchestrate the total technical assassination of Elena’s legacy.

I stared at the code. Thirteen years ago, I had helped Arthur Sterling cover up stolen patents. I knew the exact corporate logic, the hidden offshore shell registries, and the legal loopholes these syndicates utilized. I understood their architecture because I had once been one of their key architects.

For the first time in four years, I did not act as a repentant monk. I acted as a seasoned strategist with nothing left to lose.

I pulled out a secure, single-use burner phone I kept for laboratory emergency dispatches and dialed the private emergency relay number stamped on the hardware token Ethan had given me two years prior.

The line clicked twice.

"Holloway Security Node Alpha," a cool, synthesized voice stated. "State authorization code."

"This is Julian," I said clearly. "I need an immediate, direct line to Ethan Holloway. Priority zero. We have an active zero-day intrusion attempt targeting the Aletheia satellite infrastructure."

There was a three-second silence, followed by the crisp sound of an encrypted line connecting.

"Julian?" Ethan’s voice came through the speaker, alert, razor-sharp, and completely devoid of panic despite the late hour. "We detected an anomalous IP ping routing through a terminal in Newark forty minutes ago. Did someone approach you?"

"They approached Preston," I replied, keeping my voice steady. "They gave him a steel-cased Trojan designed to piggyback on the educational node's cryptographic keys. I have the payload running on an air-gapped sandbox in my basement right now."

"Preston?" A second voice joined the call. It was Leo. His tone was analytical, cutting straight to the core of the problem. "What are the compiler signatures on the payload?"

"It's an asynchronous polymorph using an antiquated Sterling Dominion backdoor from 2012," I answered, reading the hexadecimal blocks off the screen. "A backdoor I personally wrote for Arthur Sterling fourteen years ago to bypass SEC automated trade monitoring. Apex Horizon didn't write this from scratch; they resurrected my old corporate skeletons."

A heavy silence hung over the line. Even across hundreds of miles, the irony was deafening. The very weapon I had constructed to protect my fraudulent empire over a decade ago had returned to threaten my sons.

"Can you trace the command-and-control server without executing the network ping?" Leo asked.

"I can do better than that," I said, my fingers flying across the mechanical keyboard with a precision I hadn't felt in a decade. "The 2012 backdoor has a hardcoded administrative master override—a cryptographic kill-switch I embedded into the assembly layer before I left MIT. Arthur never knew about it. Apex Horizon doesn't know it exists. If I inject a reverse-compiled payload back through their listening port, I can extract their entire internal server directory, including their client rosters, financial backing records, and communication logs with foreign intelligence brokers."

"Julian," Ethan’s voice softened slightly, a note of warning entering his tone. "If you ping their listening port from an unshielded network, they will triangulate your physical location in Astoria within ninety seconds. These aren't corporate attorneys. These are high-threat cyber-mercenaries."

"I know," I replied, looking up at the ceiling of the basement, thinking of the thirty-two students who depended on this lab, the boy sleeping upstairs, and the two sons whose names I had disgraced for thirteen years. "That's why I'm going to do it from a public relay router three blocks away, while Preston stays safe here. You two just need to prepare the Department of Justice dossier on your end. Give me eight minutes."

May you like

"Julian, wait—" Leo began, but I terminated the call.

I copied the isolated reverse-exploit onto a clean flash drive, pulled on my heavy woolen coat, and stepped out into the freezing November rain, heading into the dark alleys of Queens to settle the last outstanding debt of my previous life.

Other posts