Page 23 of Echo: Run


Font Size:

My breath catches in my throat like I've been punched. My hands freeze over the keyboard.

Dead drop seven. The emergency channel Micah and I established back when we were careful and hopeful and believed encrypted messages could protect what we had. Back when I thought secure communication meant something. Back when I trusted that the silence meant he was safe, not that he'd abandoned me.

I haven't opened this system since the day I stopped leaving messages he never answered. Since the day I deleted theencryption keys and told myself I'd never check that channel again. I told myself I'd moved on. Told myself I didn't care anymore whether Ghost was alive or dead or simply gone.

The notification blinks, patient and waiting.

I stare at it for a long moment, heart pounding so hard I can feel my pulse in my throat. Micah left Echo Base hours ago to track Reeve—the Committee operative sent after Rachel and Lucas. Kane assigned him the target when he first joined the team. He geared up in the armory, checked his weapons with that methodical precision that used to make me feel safe, then walked out without looking back.

Whatever this is, he sent it while tracking Reeve in the field.

Ignoring it would be easy—delete the notification, pretend I never saw it, go back to reviewing intercepts and maintaining the careful distance I've built over the past week. The distance that's keeping me functional and sane.

Instead, my hand moves to the mouse and clicks the notification.

The message decrypts automatically, our old protocols still embedded in the system despite my best efforts to purge them. I'd tried deleting the encryption keys months ago and found them backed up in multiple locations, nested in code I'd written when I still believed we had a future. I gave up trying to erase him from the systems and just stopped looking.

The message is short. Direct. Exactly the way Micah communicates when the situation is critical and there's no time for anything except essential information.

Compromised. Reeve knows more than he should about Echo Base. Trust no one outside the team. Burn after reading. - H

My breath catches. Cold washes through me, down my arms, into my fingers where they rest on the keyboard. I read itagain, parsing every word for additional meaning, for context he couldn't include in an emergency transmission.

Compromised. Not "potential breach" or "possible leak," but compromised—present tense, active threat. The word choice is deliberate. Micah doesn't waste language. If he says compromised, he means he has evidence, proof, something concrete enough to risk breaking the silence between us.

Reeve knows more than he should. Surveillance couldn't provide this. Neither could public records, satellite imagery, or the patience of even the most skilled operative. He has operational details, internal structure, information that should be impossible to obtain without access to our secure network or direct intelligence from someone who's been inside, someone who knows.

Trust no one outside the team.

Outside the team, not inside—the distinction matters. Micah's drawing a line, establishing parameters for who might be compromised. External contacts, support network, anyone in our operational circle who isn't physically based at Echo Ridge.

My mind runs through the list automatically, analyst instincts taking over even as my hands start to shake.

Victoria Cross, our primary intelligence broker. She hates the Committee with a passion that borders on obsession, has her own reasons for wanting them destroyed. But she's also pragmatic enough to sell information to whoever pays. Would she burn us for the right price? For the right leverage?

The handful of federal contacts we've cultivated over the past year. Mostly burned operators like us, people with axes to grind against the system that betrayed them. Dylan vouched for two of them. Kane recruited another. Rachel had helped vet several of the external contacts before she'd stepped back to focus on Lucas—her son deserved stability after everything the Committee had put them through. Evennow, she occasionally provides analysis when something needs her particular expertise. Any one of the external contacts could have been flipped. Blackmail, threats against family, promises of reinstatement. The Committee has resources we can't match, connections that run deep into agencies that are supposed to be clean.

Even some of our equipment suppliers, the off-grid networks we use for secure communications. A breach anywhere in that chain could compromise operational security. Could give someone access to information they shouldn't have.

Burn after reading.

Standard protocol for intelligence that can't risk discovery. Except I'm not going to burn it. Not yet. Maybe not ever.

I save the message to an isolated server, encrypted with keys only Kane and the core team can access. Physical separation from our main network, no internet connection, secured behind biometric locks that require both fingerprint and retinal scan. Air-gapped. Completely isolated. If someone wants this information, they'll have to fight their way into Echo Base to get it.

Then I close the dead drop and sit back in my chair, studying the screens without really seeing them. My reflection stares back from the dark glass—pale and tired, my hair pulled into a ponytail that's coming loose after hours at the console.

Micah sent this hours ago. He's in the field now, hunting Reeve through whatever trail he managed to pick up. Operating alone because that's what Ghost does best. Disappearing into shadows, tracking targets who think they're safe, emerging only when he has the intel he needs.

I remember him working once, back in DC. He'd been tracking a Committee courier through Georgetown, and I'd provided signal support. He moved through crowds like smoke, present but invisible, there and gone before anyone registeredhis presence. Beautiful in a way that made my chest ache. Dangerous in a way that should have scared me, but didn't.

I shake off the memory and focus on the immediate problem. I should alert Kane. This is exactly the kind of threat that requires immediate team response. Lock down the base, review all external communications, audit everyone who's had access to operational information in the past months. Standard protocol when you suspect a leak.

But alerting Kane means briefing the team, and briefing the team means admitting I've been monitoring a dead drop system I claimed to have deleted—admitting Micah and I still have encrypted channels no one else knows about, admitting I lied when I said I'd purged all connections to the man who abandoned me when I needed him most.

Worse, it means triggering a full security review that could alert whoever's feeding information to Reeve. If there's a mole in our external network, they'll go to ground the moment we change protocols or start asking questions, cover their tracks, and make it impossible to trace the leak back to its source.

I can investigate quietly—run communication audits, trace data patterns, identify anomalies without triggering alarms. I've been doing this work for years, first at NSA and now here. Pattern recognition is what I do: find the irregularities, follow the threads, build the case one data point at a time.