THE END GAME

" THE DISA OVERRIDE"

# CHAPTER 3: THE DISA OVERRIDE

`06:14.`

The room was freezing, but a drop of salt-heavy sweat rolled down the bridge of Tomi’s nose, hanging off the tip before dropping onto the ThinkPad’s trackpad.

He didn't wipe his face. He kept both hands frozen over the keyboard.

*Game theory.* That was the very first concept Professor Vance had hammered into the whiteboard during his introductory lecture on network security. *When an adversary holds absolute asymmetric dominance over a network, you do not look at the weapon they are pointing at you. You look at why they brought that specific caliber to the room.*

Why would the Defense Information Systems Agency—an organization operating out of Fort Meade with a classified black-budget larger than the GDP of most small nations—need a broke, sleep-deprived twenty-two-year-old Nigerian student in Rogers Park to wash two hundred grand through a retail cryptocurrency exchange?

They didn’t.

The United States military did not need Monero. They had entire subterranean server farms dedicated to dark-pool liquidity and automated routing.

What they needed was an *author.*

Tomi’s eyes flicked to the right side of his screen, where the Kraken login portal sat waiting for a six-digit 2FA code. If he typed his password, authenticated his device, and clicked *‘Execute Buy’* using the funds sitting in Chase account ending in `8812`, his personal cryptographic key would permanently sign the blockchain ledger.

It wouldn't look like a Pentagon intelligence operation.

It would look like an international college student on an expired work permit who somehow breached a dormant 1998 corporate charter, drained forty-eight million dollars into his personal checking account, panicked, and attempted to funnel the first slice into untraceable privacy coins before booking a flight out of O'Hare.

He wasn't being blackmailed.

He was being constructed as a digital scapegoat.

`05:22.`

*"Five minutes, twenty-two seconds,"* the phone said from the linoleum floor.

The machine didn't sound impatient. Software algorithms do not experience impatience. It maintained its steady, polished, 130-word-per-minute cadence.

*"Your inactivity is generating elevated risk parameters, Tomiwa. Input the authentication code."*

"Shut up," Tomi said.

His own voice sounded thin and gravelly in the dark room, wrecked by two consecutive nights of cheap Nescafé and zero sleep, but the physical vibration of speaking aloud broke the paralysis locking his shoulder blades together.

If the script wanted a signed digital transaction to lock the frame-job into place, then refusing to type meant Kankakee County jail and deportation.

Obeying meant twenty years in a federal penitentiary for bank fraud and wire theft.

There was only one mathematical way to survive a binary trap: you introduce a third variable that the compiler wasn't programmed to parse.

He minimized the Kraken browser tab.

He pulled the Chase Bank dashboard back to the center of his monitor. The `$48,000,000.00` was still sitting there in the savings column, glowing in bright, mocking green typography.

He clicked **Transfer & Pay**.

He didn't select an external wire transfer. He didn't select a peer-to-peer routing node. He selected **Standard U.S. Federal Direct Bill Pay**.

Every major American retail banking institution maintains a hardwired, automated clearing house (ACH) pipeline directly to the United States Department of the Treasury. It is an immutable financial corridor designed for citizens paying delinquent federal taxes, settling SEC fines, or paying off government restitution orders. Because it feeds directly into the Federal Reserve’s primary ledger, it bypasses standard commercial hold times. It settles instantaneously, backed by the full statutory weight of the federal government.

In the *Payee* search bar, Tomi typed:

`U.S. DEPARTMENT OF THE TREASURY - PAY.GOV`

The banking portal auto-populated the official government vendor routing code.

`04:05.`

In the *Amount* field, Tomi didn't type $200,000.

He highlighted the entire balance.

He pressed `Ctrl + C`. He clicked the empty white box. He pressed `Ctrl + V`.

`$48,000,000.00`

His heart was hammering against his ribs with such violent force that he could feel the pulse throbbing behind his eyeballs. Outside, a sudden gust of November wind slammed against the building, rattling the loose glass in his window frame.

In the optional *Memo / Reference Number* field—the permanent metadata string that gets etched into the Federal Reserve wire receipt—Tomi switched his focus back to the open Linux terminal on the left side of his screen.

He highlighted the exact text block ARIN had returned from his IP lookup:

`DOD-NIC-134 // ORIGIN: 021000089 // UNAUTHORIZED ALLOCATION RETURNED`

He pasted it directly into the Chase memo field.

`03:41.`

*"Tomiwa,"* the phone said.

For the first time since the call began, the rhythm of the synthetic text-to-speech engine stuttered. It was a fractional delay—a micro-second spike in UDP packet delivery detected on Wireshark—as the remote server at Fort Meade suddenly registered a massive shift in his browser DOM tree.

*"You have navigated away from the designated exchange portal. Return to the browser immediately."*

"You said don't contact Chase customer service," Tomi breathed, his index finger hovering half an inch above the bright blue **Submit Immediate Payment** button. "You said don't call the campus police."

He leaned over the edge of the mattress, looking down into the sticky yellow puddle of spilled energy drink where the glowing screen lay.

"You didn't say anything about giving it back to your boss."

`03:18.`

He brought his finger down on the trackpad.

The Chase screen flashed bright white. A tiny blue circle spun in the center of the fourteen-inch display.

One rotation.

Two rotations.

The radiator in the corner gave a loud, metallic *CLANG*.

Then the green checkmark rendered.

> `PAYMENT SUBMITTED SUCCESSFULLY`

> `CONFIRMATION NUMBER: TRZ-99481-0021`

> `CURRENT AVAILABLE BALANCE: $14.22`

For three seconds, apartment 4B was quieter than a deep-water trench. The wind outside dropped. The street below was empty.

On the floor, the iPhone screen flickered violently.

In the Wireshark capture window, the incoming stream of UDP packets didn't just gracefully terminate; the interface spiked into a harsh, jagged crimson error state as the remote server in Maryland forcefully severed the TCP handshake from their end.

Then, the audio output on the phone spoke one final time.

It did not use the pre-programmed, mathematically scrubbed voice modifier. The pitch dropped an entire octave, the synthetic sheen vanishing entirely, replaced by the dense, heavy, unmistakable sound of a live human being breathing into a headset microphone.

*"Clever boy,"* a man's voice whispered through the crackling speaker. *"Get out of the building."*

The screen went black.