"Find them. Whoever sent this knows something about our infrastructure that nobody outside this room should know.That's either an asset or a threat, and I need to determine which one before they decide to use that door for something other than a greeting."
Kane nods. One nod, the kind that closes discussion and opens action.
"Victoria, trace the source. Tommy, harden the channel. Sarah, increase monitoring on all external relays. Daily reports until we know who's on the other side."
The briefing disperses. Sarah falls into step beside me in the corridor, her stride matching mine with the automatic rhythm of years spent working the same shifts in the same mountain facility.
"How bad?" she asks.
"The breach itself is contained. One channel, one message, no lateral movement into any operational system."
"That's not what I asked."
I push my glasses up. The lenses catch the corridor lighting and throw it back.
"Whoever did this thinks in code the way I do. The routing, the cipher, the way they selected that specific channel out of everything they could have targeted. They weren't looking for a weakness. They were looking for the most interesting part of the system and they found it."
Sarah's gaze holds mine for a beat longer than casual. She reads me the way she reads signal patterns, scanning for the anomaly underneath the baseline, and she’s known me long enough to locate it.
"Keep me posted," she says, and turns toward the signals suite.
I walk back to my station. Monitor three sits blank and patient in the row of active displays.
I killed the watchdog feed during briefing prep, and the dark screen occupies space between its glowing neighbors like a held breath.
I built this system. Every relay, every channel, every layer of encryption and counter-surveillance and communication infrastructure that keeps the people I care about alive and hidden inside this mountain.
I built it in a room of bare rock and salvaged equipment and the stubborn certainty that if I made the walls strong enough, nothing would get through.
Someone got through. Someone whose cipher made my jaw ache with its precision. Someone who looked at the system I spent years designing and saw it clearly enough to find the one opening I never knew existed and then used that opening to send a warning.
Compromised.
Whoever sent it didn't attack my system. They warned me.
That's worse, because it means they found the door and chose to knock instead of walking through it.
The person on the other side understood my work well enough to appreciate it, well enough to see through it, and well enough to reach me through a gap I'd have sworn on every line of code I've ever written did not exist.
I sit down. Pull the keyboard close. Start rebuilding the channel with new protocols, harder encryption, tighter monitoring.
My fingers move fast across the keys, and the rhythm of typing is the only thing that steadies the pulse still hammering at the base of my throat.
Below me, the servers hold their breath. And somewhere beyond the mountain, whoever sent that word is waiting to see what I do next.
2
DAR
Three days after sending the warning, my perimeter alerts trigger in sequence.
Left monitor first. The passive sensor I buried in my ISP's routing table, the one that flags any query targeting my subnet that doesn't match standard traffic patterns. Then the middle screen, where the honeypot email address I seeded across three dark web marketplaces receives a ping from an IP range routed through military-grade anonymization that isn't quite as anonymous as whoever deployed it thinks it is. Then the right monitor, where the geolocation spoofing on my primary connection stutters for forty milliseconds before stabilizing.
Forty milliseconds. Enough time for someone running the right kind of traffic analysis to triangulate a physical location within a twelve-block radius. I pull my hands off the keyboard. My fingers go still on the desk.
Someone is looking for me. Specifically, methodically, and with resources that exceed anything a private actor could deploy without institutional backing. The query patterns are too coordinated, the timing too precise, the footprint too clean. This is a professional operation, and it started within seventy-twohours of my sending a single word through a channel that should have been untraceable.
Should have been. That's the part that stings.
