Demonetized by Design – Part 3

Story code: ST-000664

Part 3: Root Access

Maya let the crowbar clatter against the concrete floor. Brute force was useless against the magnetic lock she had wired herself. The migraine behind her right eye flared, a sharp, pulsing reminder of the ticking clock on her medication. The text message on her phone glared up at her from the cracked screen: *Technician dispatched.*

If the automated system was physically locking her workshop doors, it wasn’t just a platform moderation glitch. It was a targeted, local network intrusion. But her router’s firewall was locked down tight. She had configured it herself. There was only one way someone could bypass the local network restrictions without triggering a massive intrusion alert: they already had the administrative keys.

Maya bolted out of the garage, ignoring the throbbing pain in her skull. She ran to her spare bedroom closet, dragging a plastic storage bin out from under a pile of winter coats. She threw the lid off and dug past tangled XLR cables and broken soldering irons until her fingers closed around the cold, brushed-aluminum chassis of a five-year-old laptop.

It was the machine she used when she and Milo first incorporated Axiom Dynamics. That was three years ago, before they argued over monetization strategies. Before she had walked away to build her own solo DIY channel, leaving him with the corporate shell and the enterprise accounts.

She plugged the laptop straight into the wall outlet and booted it up. The screen flickered to life, displaying a dusty, outdated operating system. Maya didn’t bother opening a web browser. She hit the keyboard shortcut to launch a raw terminal window.

When she and Milo had first built the Axiom master control backend, Maya had hardcoded a backdoor authentication token into this specific machine’s physical MAC address. It was a fail-safe she had designed in case Milo’s sloppy password management ever accidentally locked them out of their own cloud servers. He had sworn he would patch the vulnerability after she left the company. She was betting her entire livelihood, and her physical safety, that his notorious laziness hadn’t changed.

Her fingers flew across the keyboard, typing the legacy SSH command from memory.
`ssh -i ~/.ssh/axiom_legacy_key admin@axiom-enterprise-panel.local`

The terminal hung for an agonizing five seconds. Maya held her breath. Then, a wall of crisp green text populated the dark screen.
`Authentication successful. Welcome to Axiom Master Control.`

She was in. Because her solo creator channel was still technically a legacy sub-domain generated under their original enterprise charter, the Axiom panel still held god-level administrative oversight over her account.

Maya typed a query to pull the raw backend audit logs for her channel’s recent strikes. She expected to see a massive, scrolling block of platform API requests-thousands of automated server pings from the video hosting site’s moderation AI.

Instead, the terminal spat out a shockingly short, manual list.

`[14:02:11] OVERRIDE: STRIKE_APPLIED // User: ROOT_AXIOM`
`[14:05:34] OVERRIDE: STRIKE_APPLIED // User: ROOT_AXIOM`
`[14:12:09] MOD_ACTION: CHAT_INTERCEPT_MANUAL // User: ROOT_AXIOM`
`[14:18:22] NETWORK_PUSH: LOCAL_RELAY_LOCK_ENGAGE // User: ROOT_AXIOM`

Maya stared at the screen. The bot from the support chat hadn’t been caught in a glitchy logic loop. It had been manually intercepted. Someone logged in as the Axiom root user was sitting at a keyboard, hand-typing those ominous, monospaced threats directly into her chat window.

She ran a trace on the root user’s active session, querying the origin IP address for the commands. The terminal returned a single, static IPv4 address.

`Origin IP: 73.15.202.94`

Maya felt the blood drain from her face, leaving her skin cold. It wasn’t a sprawling corporate server farm in Virginia. It was a residential block. Specifically, a residential block in the affluent, gated hills on the north side of the city. She didn’t need to look up the geolocation. She had personally wired the gigabit fiber network for that exact IP address three years ago.

It was Milo’s house.

Milo wasn’t just watching her solo channel burn; he was the one holding the matches. The absurd “Unsafe Medical Modification” strikes, the terrifying “Directive 33” code in the chat, the physical lockdown of her tool cabinets-it was all him. He was exploiting their shared backdoor infrastructure to masquerade as an unstoppable, rogue algorithm.

A sharp, heavy knock on the front door shattered the silence in the house.

Maya flinched. She looked down at the terminal timestamp. *Technician dispatched.*

She unplugged the laptop, cradling the heavy machine in her left arm, and walked down the hallway. Her bare feet were completely silent on the hardwood. She didn’t bother looking through the peephole. She pulled up her front porch security camera feed on her phone.

Milo stood on her welcome mat. He was wearing a crisp, expensive polo shirt, holding a thick leather-bound folio against his chest. He looked the exact picture of a deeply concerned business partner. His pristine silver SUV was idling in her driveway.

Maya unlocked the deadbolt and pulled the door open.

Milo’s face instantly shifted into a mask of deep, practiced sympathy. “Maya,” he breathed, stepping forward. “Thank god you’re home. I saw the system alerts on the Axiom backend. The platform’s algorithm has gone completely rogue. It’s aggressively flagging your hardware tutorials as medical devices. They’re scrubbing everything.”

Maya stood squarely in the doorway, blocking his path into the house. She didn’t say a word.

Milo held up the leather folio, tapping it urgently. “I’ve been on the phone with their enterprise reps all morning. They won’t talk to you because you’re classified as a solo creator now. But if we migrate your channel’s IP-your CAD files, your blueprints, your entire video archive-back under the Axiom corporate umbrella, my enterprise tier can shield it from the automated sweeps. I have the transfer agreements right here. Just sign them, and I can have the local network quarantine lifted in ten minutes.”

He offered a warm, reassuring smile, his eyes practically swimming with fake concern. “I brought the paperwork so we can fix this right now. You won’t lose a single video.”

Maya looked at the folio, then up at his impeccably calm face. The sheer audacity of it made the migraine pounding in her temples sharpen into a cold, terrifyingly clear focus. He had drained her bank account, locked her out of her own workshop, and terrified her with fake cybersecurity threats, all to strong-arm her into signing away the rights to her open-source engineering work.

“A rogue algorithm,” Maya repeated, her voice perfectly deadpan.

“It’s a nightmare,” Milo agreed, shaking his head. “They’re calling it Directive 33. The enterprise rep told me it’s totally unyielding.”

Maya slowly turned the heavy laptop around in her arms, angling the screen so the harsh afternoon sun illuminated the raw green text of the terminal window. She tapped the glass screen directly beneath the last line of code.

`[Origin IP: 73.15.202.94 // Session: ACTIVE_MILO_ADMIN]`

Milo’s eyes flicked to the screen. His warm, sympathetic smile froze, then slowly dissolved, leaving behind a slack, bloodless expression.

“It’s funny,” Maya said softly. “I didn’t know an unyielding enterprise algorithm drove a silver SUV.”


Leave a Comment