Story code: ST-001902
Part 3: Batch Execution
“Thirty-eight million dollars,” David said, his voice trembling just enough to sound defeated. “If you hit enter on that tablet, the automated fraud triggers will freeze the transfer in milliseconds. It won’t clear the clearinghouse. You’ll burn the backups for nothing.”
Mateo didn’t move his thumb from the glass screen. “It’s a direct SQL injection. The system will process it as standard payroll.”
“And the bank’s API will reject it because it’s not originating from an authenticated executive device,” David lied, seizing the tiny thread of technical plausibility. “I need my laptop. I have to approve the disbursement through the primary admin dashboard, or the security flags will bounce it right back.”
Mateo studied David’s face, searching the pale, sweating features for the bluff. Down the street, the neighbor’s golden retriever finally stopped barking. The silence in the car was heavy and suffocating.
“Get it,” Mateo said, stepping back just an inch from the window frame. “Slowly.”
David reached over the center console, carefully sweeping the crumpled termination papers aside to grab his leather messenger bag from the passenger floorboard. He pulled out his silver laptop and balanced it on his thighs, pinned tightly between his stomach and the steering wheel.
His actual plan was simple and entirely self-serving. He would tether the laptop to his phone’s hotspot, access the master control suite, and hunt down the specific API token tied to Mateo’s rigged warehouse scanner. Once he revoked that token, Mateo’s tablet would lose its connection to the database and the subterranean video feed. The brother with the thermite would be blind. To defuse the immediate physical danger at his window, David would also quietly override Mateo’s termination code, reinstating his employment as a peace offering before he floored the gas pedal and sped away.
David flipped the screen open. The biometric camera flashed a sharp green light across his retinas, immediately followed by a prompt for his physical hardware key. He tapped the gold contact on the side of the laptop.
*Access Granted.*
He opened the terminal suite. His fingers flew across the keyboard, driven by pure, unadulterated panic. He bypassed the financial routing architectures and went straight into the `subcontractor_ops` node. Apex Staffing, the third-party agency that supplied all the warehouse temp labor, maintained a direct integration with David’s overarching system.
David needed Mateo’s employee ID to isolate the rogue scanner. He pulled up the Apex workforce management dashboard.
The screen populated. David moved his cursor toward the search bar.
He froze.
The cursor hovered uselessly over a massive, cascading wall of red text streaming down the center of the dashboard UI.
`ACTIVE TERMINATION QUEUE: 4,112`
David blinked, his brain aggressively rejecting the number. He assumed it was a historical data glitch, a cached error from a previous quarter. But the number ticked upward in real time.
`4,289`
`4,450`
David leaned closer to the screen, his breathing turning shallow. He clicked on the live batch processing log. The system wasn’t glitching. It was executing perfectly, exactly as commanded by the Apex Staffing master admin account.
Rows upon rows of employee IDs were being purged. Beside every single name was the exact same blank line and checkmark next to a generic “Policy Violation Code 11-A” that David had seen on the stapled papers resting on his passenger seat.
“What are you doing?” Mateo asked, his voice low, sensing the sudden, rigid shift in David’s posture. Mateo leaned back into the window frame, angling his head to look at the laptop screen.
David didn’t try to hide it. He couldn’t. His mind was furiously calculating the horrific math of what he was looking at.
His own highly illegal code had shaved fractions of cents off the overtime calculation over four years. It was a parasitic, invisible skim. But this? This was a slaughter.
Tomorrow was Friday. The end of the month. Payday.
David knew the Apex Staffing vendor contract inside and out. The corporate logistics budget paid Apex upfront for the projected labor hours, and Apex distributed the wages to the temps. But there was a penalty clause buried in the fine print. If a temp worker was terminated for a “policy violation” before the two-week pay period officially closed, they forfeited their pending hours to cover Apex’s “administrative onboarding losses.”
Apex wasn’t paying out the wages tomorrow. They were firing everybody.
“You didn’t get caught,” David whispered, the words slipping out as the sheer scale of the betrayal washed over him.
“What?” Mateo demanded, his grip tightening on the tablet.
David pointed a shaking finger at the cascading red numbers on his screen. `ACTIVE TERMINATION QUEUE: 5,102`
“You thought you got fired because you found my backdoor,” David said, his voice hollow. “You thought my system flagged your scanner and I sent a targeted termination order to cover up the skimming.”
Mateo frowned, his dark eyes snapping from David’s face to the laptop. “You did. I pulled the commit log last night, and three hours later, my shift supervisor handed me those papers.”
“It’s a coincidence,” David said, turning the laptop slightly so it faced the open window directly. “Look at the dashboard, Mateo. I didn’t fire you. Apex Staffing is firing *everyone*.”
Mateo stared at the screen. The red numbers blurred as they scrolled past, a relentless digital scythe cutting through thousands of livelihoods.
“Tomorrow is payday,” David explained, a sick realization settling deep in his bones. “If Apex terminates the workforce for cause today, they legally withhold the last two weeks of pay. The company already wired Apex the payroll funds. Apex is keeping the entire gross distribution. It’s tens of millions of dollars.”
Mateo’s expression fractured. The cold, calculated vengeance that had driven him to hijack an off-site server room and ambush an executive in his driveway suddenly faltered. He looked down at the tablet in his hand, at the blinking cursor of his SQL injection, and then back up to the laptop screen.
`ACTIVE TERMINATION QUEUE: 6,804`
The algorithm wasn’t malfunctioning. David’s skimming operation was petty theft compared to the heist the staffing agency was pulling off in broad daylight.
“They’re burning the whole warehouse down,” Mateo breathed.
David looked up at the man standing outside his car. The thermite threat was still real. The direct-deposit refund script was still waiting on a keystroke. But the rules of the extortion had just violently changed, and neither of them had any idea how to stop the machine they were watching.