Chapter 27 Asher
ASHER
Chaos is just a pattern you have not decoded yet.
That is what I tell myself. That is the mantra that keeps my heart rate at a steady sixty-four beats per minute while the world burns around me. Most people see noise; I see variables. Most people see a fire; I see the thermodynamics required to extinguish it.
But right now, looking at the three monitors arranged in a semicircle on my desk, I am struggling to find the pattern.
“Talk to me, Asher,” Ethan barks from behind me. He is pacing the length of the server room—our War Room—like a caged tiger, his tie discarded and his top button undone. “What are we looking at?”
“It isn’t a probe anymore,” I say, my fingers flying across the mechanical keyboard. The click-clack sound is usually soothing, a rhythmic anchor, but today it sounds like gunfire. “The probe was just a knock on the door. They didn’t wait for us to answer. They kicked it in.”
On the center screen, lines of red code are actively overwriting my beautiful, clean architecture. It looks exactly like a wound opening up in real time.
“Sector four is compromised,” I state, keeping my voice flat to suppress the panic clawing up my throat.
“The encryption keys for the Confessions database are being brute-forced. Whoever this is, they are not using a laptop in their mother’s basement—they are using a botnet with massive processing power. ”
“The Confessions feature,” Owen says, leaning over my shoulder with his usual relaxed posture completely gone. He smells like stale coffee and the sharp tang of stress sweat. “Asher, that’s the vault. That’s the anonymous user data. If that gets out…”
“I know the variables, Owen,” I snap, typing a rapid command to reroute the traffic.
Access Denied. “If the Confessions data gets decrypted, the anonymity of two million users is destroyed. We promised them a safe space to share their darkest secrets. If those secrets are linked back to their real identities…”
“It’s a nuclear bomb,” Ethan finishes grimly. “We have politicians on this app. CEOs. Influencers. If their anonymous confessions about affairs, addictions, and corporate fraud get leaked…”
“Mosaic is dead,” I say. “Trust is our currency. If we lose it, we are bankrupt, and we lose everything.”
A new window pops up on my screen. It isn’t a system error. It’s a chat box.
[Unknown User]: Knock knock.
Acid floods my gut. A manual override. The hacker is not just an automated script; they are present, actively watching us try to stop them.
[Unknown User]: Nice firewall. Did you build it yourself? It reads like a script-kiddie job from 2018.
“They’re mocking us,” Owen says, his hands curling into fists. “Cut the line, Ash. Pull the plug.”
“I can’t,” I say, my eyes scanning the dense packet data. “If I sever the connection now, the fail-safe triggers a massive data dump. They have rigged the database with a dead man’s switch. If I disconnect them, the information automatically uploads to a public server. They have us in a chokehold.”
[Unknown User]: Let’s play a game. I have 40 terabytes of dirt. Nudes. Confessions. IP addresses. I’m going to release 1% of it in… let’s say… two hours. Unless you pay the toll.
“Blackmail,” Ethan growls.
[Unknown User]: I don’t want money. I want to watch you squirm. Let’s start with a public statement admitting your security is a joke. Post it on the homepage. Then we can talk about the price.
“They want to humiliate us,” I realize, the pattern finally emerging. This isn’t financial; it’s entirely personal. “This is a vendetta.”
“Fix it,” Ethan orders, his voice dropping to a terrifyingly calm register. “I don’t care how you do it. I don’t care if you have to burn the rest of the app to the ground. Protect the Confessions. You have two hours.”
“I need silence,” I say. “Everyone out. Except Owen. I need you to monitor the social channels in case they leak early.”
Ethan gives a sharp, military chin-lift. “I’ll handle Sterling. I need to come up with a convincing lie about why the system is lagging before his auditors notice.”
He turns to leave, but the glass door to the server room slides open before he can reach it.
It is Tessa.
The atmospheric pressure in the room hits a new, volatile frequency. Usually, her presence is a variable that drastically improves system performance, balancing Ethan’s aggression and Owen’s chaos while grounding me.
But today, my internal diagnostics flash a red warning the second she enters.
Catastrophic.
She is wearing a gray blazer that hangs off her frame, wrapping it around her body like armor. Her skin, usually a warm, vibrant tone, is the color of old parchment. There is a sheen of cold perspiration on her upper lip, and her eyes are glassy as she leans heavily against the metal doorframe.
“I heard shouting,” she says, her voice thin and reedy. “What’s happening? Why are the devs running around like the building is on fire?”
“Security breach,” Ethan says, stepping between her and the monitors in an instinctive maneuver to shield her from the disaster. “We’re handling it. You should go back to your desk.”
“Don’t handle me, Ethan,” she says, pushing past him. She walks toward us, but her steps are uneven, and she sways, forcing herself to correct her balance at the last second. “I’m the Brand Strategist. If we’re having a crisis, I need to know how to spin it. Is it a crash? A leak?”
“It’s a hostage situation,” Owen says quietly.
Tessa stops dead, her eyes darting from the red code scrolling on my screen to the active chat window from the hacker.
“Confessions,” she whispers, bringing a trembling hand to her mouth. “They have the Confessions?”
“They are threatening to leak them in just under two hours,” I say, not looking away from the screen, though every primal instinct in my body wants to go to her. “I am currently attempting to isolate the specific node they are using to bypass the encryption. It is… highly difficult.”
“Okay,” Tessa says, taking a deep, shuddering breath as the remaining color drains completely from her face.
She is nauseous. Visibly, violently nauseous.
“Okay. I can draft a holding statement. We need to prepare for the worst-case scenario. If the leak happens, we need to frame it as a targeted attack on privacy and position ourselves as victims alongside the users…”
She reaches for a heavy chair, dragging it over to my desk. The metal legs screech against the floor, and the harsh sound seems to physically hurt her, making her flinch and squeeze her eyes shut.
“Tessa,” I say, my fingers pausing over the keys for a millisecond. “You are unwell.”
“I’m fine,” she says, sitting down heavily. “Just a headache. Focus on the code, Asher. I’ll handle the PR.”
“You are not fine,” I insist. My brain splits into two parallel processes. Thread A: Stop the hacker. Save the company. Thread B: Protect Tessa.
She is operating at critical failure levels—her pallor is significant, her tremors are visible, and her breathing is far too shallow.
“Asher, look at the screen!” Owen shouts.
I snap my attention back to the monitor as the red code spikes violently.
[Unknown User]: Tick tock. I’m getting bored. Maybe I’ll leak a few early. Let’s see... User #8902. "I'm sleeping with my boss and his brother." Oof. Spicy.
A spike of pure ice hits my veins.
“That’s a bluff,” Ethan says, moving to stand closely behind my chair. “Random generation.”
“It is not random,” I whisper, staring hard at the command lines.
My eyes track the specific syntax the hacker is using to inject the SQL query. It is messy, utilizing a recursive loop that is not standard practice—it is exceptionally lazy.
And I know that exact loop. I spent three months completely rewriting it two years ago.
“I know him,” I say, the realization hitting me like a physical blow.
“What?” Ethan demands.
“The admin signature,” I say, pointing to the hash string on the screen. “The encryption key they are using to bypass the firewall. It is Greg.”
“Greg?” Owen asks, totally confused. “Greg from Accounting?”
“Greg the Junior Dev,” I snarl. “The one we fired during the early beta phase. The one who swore he permanently deleted his admin keys.”
“He sold his credentials,” Ethan realizes, his voice turning deadly.
“He must have,” I say, a heavy wave of guilt washing over me. “I successfully revoked his credentials, but he must have buried a hard-coded backdoor in the legacy library files before he left. I missed it.”
“So it’s a disgruntled ex-employee?” Tessa asks, her voice incredibly weak. “He just wants revenge?”
“Greg is not smart enough to run a botnet this size,” I say, typing furiously to verify my working theory. “He is a script kiddie. He doesn’t have the massive capital required to rent this much server space. Someone is actively backing him.”
I run a quick trace on the packet header. Usually, hackers route through Tor or a dozen secure VPNs, but Greg is sloppy. He routed it straight through a shell company.
Server Owner: N-Tech Ventures.
“N-Tech,” I read aloud. “That name sounds familiar.”
“It’s a holding company,” Tessa whispers, looking significantly worse than before. “For Nebula.”
The room falls completely still.
“Nebula,” Ethan repeats, the name a venomous curse. “Markus Vance.”
“Greg is the weapon,” I realize, quickly connecting the dots. “Markus is the bank. Nebula hired our disgruntled ex-employee to burn us down. It is corporate sabotage.”
Tessa lets out a soft, strangled sound. “Markus told me if I crossed him, he would make sure Mosaic didn’t last the year.”
“He’s trying to make good on that exact threat,” Owen says grimly. “If we go down, Nebula absorbs our market share overnight.”
“He is not going to win,” I say. My fingers fly across the keys with renewed aggression.
Now that I know it is Greg, I know the weak spots. Greg was lazy, and he reused old code. If I can find the matching hash in his injection script, I can reverse the data flow.
“How long?” Ethan demands.