Story code: ST-000623
Part 2: The Vendor Vault
The red light on the desk phone flashed, casting a faint crimson reflection against Sarah’s coffee mug. The shrill ring demanded an answer, while the silent, pulsing *Julian is typing…* indicator on her screen demanded her compliance. The dual threats squeezed her chest, making the stale air in her cubicle feel impossibly thin.
She reached out and jammed her index finger against the “Send to Voicemail” button on the phone base. The ringing cut off instantly, leaving a hollow silence in its wake.
A second later, Julian’s message populated the Slack window. *Sarah, the migration is moving smoothly, but we’ve hit a slight snag. I need you to drop the master admin keys for the campaign’s routing logic into the secure vendor vault. The optimization partner needs them to finalize the A/B testing matrix before launch.*
Sarah stared at the words, her mind racing. Optimization partner? There had never been a third-party vendor attached to this rollout. She had designed the A/B testing matrix herself, building every variant over the last three weekends.
She placed her fingers on the keyboard, forcing them to remain steady. *I wasn’t aware we were onboarding an external vendor for the autumn rollout, Julian. I have the A/B tests staged and ready to execute on my end today. My schedule is entirely clear.*
The typing indicator danced again. *Leadership decision, made late last night. We’re migrating the ecosystem to Apex Solutions to leverage their AI predictive models. It’s a massive win for the department. Just need those keys, Sarah. We’re on a tight clock.*
Apex Solutions. Sarah highlighted the name, copied it, and Alt-Tabbed to her browser, pasting it into a search engine. The results were generic-a dozen different consulting firms and shell companies shared the name, none of them matching the profile of an enterprise-level AI vendor.
She switched back to the developer dashboard, her backdoor view into the server logs. The data export had now crossed eighty gigabytes. The progress bar in the terminal window chewed through the files relentlessly. She scrolled down, tracking the file paths of the data currently being transferred.
Her blood ran cold. The terminal wasn’t just pulling from her `/campaign_autumn` directory anymore.
The script had jumped a directory level. The glowing white text on the black screen clearly showed files streaming out of `/var/www/secure/customer_staging`.
Julian wasn’t just migrating her marketing copy and landing pages. He was exporting the raw, unencrypted customer database. The staging folder contained the behavioral profiles, the lead scoring metrics, and-crucially-the billing tokens from the legacy platform. Transferring that level of Personally Identifiable Information outside the company firewall without compliance oversight wasn’t a workflow pivot. It was a massive, catastrophic data breach. And if Julian was using her campaign structure to mask the extraction, her digital fingerprints would be all over the staging ground.
The red light on her desk phone flared back to life, steady this time. The voicemail indicator.
Sarah picked up the handset and punched in her four-digit PIN, pressing the plastic receiver hard against her ear.
“This is a mandatory legal communication from Oaktree Loan Servicing,” a pre-recorded, metallic voice droned. “Your mortgage account is in severe arrears. The grace period for your loan modification has expired. If payment in full for past due amounts is not received by five PM tomorrow, Eastern Standard Time, we will initiate formal foreclosure proceedings and schedule a public auction of the property. Press one to speak to a representative…”
Sarah hung up the phone, dropping it back onto the cradle with a heavy plastic clatter. Five PM tomorrow.
The Q3 bonus payout was scheduled for payroll processing on Friday morning, explicitly contingent on her status as the lead architect of tomorrow’s campaign launch. If Julian handed the admin keys to “Apex Solutions,” her name would be scrubbed from the final deployment. The bonus would default to the department’s general pool-which Julian controlled. She wouldn’t just lose the credit for six months of grueling work; she would lose her home.
She looked back at the terminal. The export was speeding up. If she gave him the keys, he would have total control of the system architecture, and her campaign would be gone. If she refused, he would fire her for insubordination on the spot, evaporating her bonus anyway.
She needed proof that the IP address didn’t belong to a legitimate vendor. She opened a command line interface and typed a quick `traceroute` command, pinging the masked external IP to see where the data was actually landing.
The terminal pinged, tracing the digital hops. It bounced through an Amazon Web Services node, then hit a localized commercial ISP, before terminating at a server registered to a residential address in a neighboring state. Not a corporate data center. Not an enterprise AI firm. A private residence.
Julian was stealing the company’s data.
Another Slack message popped up, the notification sound jarring her nerves. *Sarah. The keys. I see you’re active on the network. Don’t make me escalate this to HR as a compliance block.*
He was threatening her. She rested her hands on the keyboard, staring at the flashing cursor. She knew the command to kill the export process. A simple `kill -9` followed by the process ID would instantly sever the connection, slamming the door on the data theft. But it would also trigger a system-wide alert, notifying IT, Julian, and the executive suite that Sarah had used a developer backdoor she wasn’t supposed to have. She would be exposing him, but she would be firing herself in the process.
She hovered her finger over the enter key, the silence of the cubicle pressing in on her. The terminal text blurred slightly as her eyes watered.
Suddenly, the terminal window on her screen froze. The scrolling lines of data halted. The blinking cursor vanished.
Sarah jammed the spacebar. Nothing. She clicked the mouse, but the cursor was locked dead in the center of the screen. Her entire machine had been remotely frozen.
“I thought I made myself clear about the keys, Sarah,” a voice said.
Sarah flinched, spinning her chair around.
Julian stood at the entrance to her cubicle. He wasn’t smiling. In his left hand, he held a sleek silver tablet, his thumb resting over a large virtual toggle switch on the screen. His eyes drifted slowly from her frozen monitors down to the unopened neon pink envelope from Oaktree Loan Servicing sitting openly on her desk.
“We need to have a conversation,” Julian said, his voice dropping to a low, quiet register. “Right now.”