Chapter 2 #2
My mother would be appalled. She kept a house in London that looked like it belonged in a design magazine and felt like living inside a display case, every surface curated, every object placed with intention, every room communicating the same message: we are people of taste and discipline and control.
I left that house at eighteen. I crossed an ocean, enrolled at university on a scholarship I earned without her help, and built a career that has nothing to do with the Bradshaw name and everything to do with what I can do with a keyboard and a problem worth solving.
A decade later, my mother still introduces me at family functions as "our Lennox, the computer girl," which tells you everything you need to know about why I don't attend family functions.
The malware code fills my screen, and I lose myself in it the way I always lose myself in work.
The logic is elegant, genuinely elegant, the kind of architecture that requires not just technical skill but aesthetic sensibility.
Whoever wrote this cared about the craft.
They nested their execution pathways with a symmetry that borders on artistic, each branching condition mirrored and balanced, redundancies built in with precision that suggests military training or academic rigor or both.
I'm grudgingly, furiously impressed. And I want to find them, because anyone this good is dangerous in ways that go beyond a single base's communication systems.
The shortbread sits untouched on the nightstand. I eat a piece without tasting it, brush crumbs off my keyboard, and keep working until the words on the display start swimming and my eyes refuse to cooperate.
I sleep for a few hours. I dream about code, mostly, and once, briefly, about a pair of dark eyes and hands that hang loose at their sides like they've got nothing to prove. I attribute this to sleep deprivation and refuse to examine it further.
I'm back in the comm building before the morning briefing, coffee in hand, monitors awake and running the overnight traces I set before leaving.
The results are waiting for me, and they're worse than I expected.
The malware isn't an isolated implant. It's connected to secondary payloads buried in several other subsystems, each one designed to activate in sequence if the primary is removed without the proper deactivation protocol.
It's a failsafe. If someone removes the kill switch, it detonates anyway.
I'm deep in the secondary payload analysis when a knock interrupts.
It isn't really a knock, though. It's a rap of knuckles against the frame, a specific rhythm I've already learned to recognize because it happens every Tuesday and apparently now happens on Wednesdays too.
My pulse kicks up a notch before I can stop it.
"It's not Tuesday," I say, keeping my eyes on the screen because turning around means contending with the full effect of him in my doorway at close range, and I haven't had enough coffee for that.
"And yet here I am." His drawl is warm and carrying just enough amusement to make me want to throw something at him. "Miss me already?"
"Desperately. I've been counting the hours since your last riveting inspection of my ventilation grate.
" I pull up the access log directory and send it to the shared drive before he asks.
"Badge swipes and after-hours entry for the comm building.
For the cross-reference Hartwell wants. There. Sent."
"That's almost hospitable, Bradshaw. I'm touched."
"Don't get used to it."
He doesn't leave.
I can feel him leaning against the frame because the quality of his voice changes when he's braced against something, drops half a register, and the fact that I've cataloged his vocal patterns by posture is not something I plan to examine closely.
"The malware you found last night," he says. "The logic bomb. Is it command-detonated or does it run on a timer?"
My fingers stop on the keyboard.
It's the right question, not "can you remove it" or "how bad is it" or any of the surface-level queries that military personnel default to when they want reassurance instead of information.
He's asking about the trigger mechanism, which means he's thinking about operational implications, which means he understands how weapons work to know that how something is detonated matters as much as what it does.
I turn my chair to face him. His shoulders fill the opening.
He's long and lean and unhurried, with hands hanging loose at his sides and dark eyes that don't flinch or slide away or do any of the things most people's eyes do when I hold contact too long.
He just watches, patient and present, like he's got nowhere to be except right here, waiting for me to answer his annoyingly perceptive question, and the full force of his attention at this distance tightens something low in my chest that I don't have a clinical name for.
"Command-detonated," I say. "External trigger signal, specific frequency. Not time-based."
"So someone has to make the decision. It doesn't go off on its own."
"Correct."
"Which means removing it isn't enough. You have to find the person holding the trigger."
My rings press into the arm of my chair where my hand has wrapped around it, and I don't know when I grabbed on. "Yes. That's exactly what it means."
His gaze drops to my hand on the chair arm, then comes back up.
His expression doesn't change, but his attention sharpens the way a lens focuses, and I can see him registering the grip, filing it, choosing not to comment on it.
The restraint is worse than if he'd said something.
I could parry something spoken. The quiet observation just sits there, seen and acknowledged and left alone, and I have no counter for it.
"I'll have the physical access cross-reference to you by end of day." He straightens off the frame and tips an invisible hat that should be ridiculous and instead makes my stomach tighten. "Try to eat something that isn't shortbread."
"How do you know about the shortbread?"
"You had crumbs on your collar yesterday. Process of elimination." The grin arrives exactly when I'm most off-balance, precise and warm and gone before I can mount a defense, and then he's walking down the corridor and I'm staring at the space where he was.
I release my grip on the chair, deliberately, and put my hands back on the keyboard.
Weeks ago, he asked about the base's legacy encryption protocols with enough specificity that I had to recalibrate my assessment of him entirely.
I'd written him off as another uniform with a limited operating range.
Griff Holland keeps proving that wrong, and each correction lands somewhere I haven't built defenses for, somewhere that smells like soap and gunpowder residue and doesn't respond to logic.
Rivera appears in the doorway before I've fully recovered. She doesn't knock, which I've come to understand is an NCIS prerogative she exercises deliberately.
"Ms. Bradshaw. Can I have a minute?"
"You can have thirty seconds. I'm in the middle of something."
Rivera steps inside and closes the door behind her. The gesture is quiet but pointed.
"NCIS has been tracking a pattern across Tidewater for the better part of a year," she says.
"It started with Dr. Fallon McKay's coastal vulnerability research.
Boat sabotage, data theft, a sophisticated cyber intrusion that accessed her findings through the base network.
Then the hospital supply chain was compromised.
Critical equipment systematically diverted over months. Now the communication systems."
I lean back in my chair. "You're telling me you don't believe this is isolated."
"I'm telling you that someone is systematically mapping every vulnerability on this base.
Physical infrastructure in the McKay case.
Medical response capability in the hospital case.
And now digital communications." Rivera's expression is flat and professional, but her eyes carry the particular intensity of someone who's been connecting dots that nobody else wanted to see.
"Three separate attacks, three different systems, one pattern.
Someone is building a comprehensive picture of how to cripple Tidewater. "
My mind is already racing, threading connections. The sophistication of the malware, the patience of the intrusion timeline, the military-grade understanding of network architecture.
"You think it's the same actor behind all three," I say.
"I think it's coordinated. Whether it's one person or an organization, the methodology is consistent. Patient, strategic, and focused on infrastructure rather than personnel." Rivera holds my gaze. "Which means your breach isn't the endgame. It's the third piece of something bigger."
What I'm sitting inside just expanded from a network breach to a coordinated campaign against a military installation.
The malware on my screens isn't an isolated intrusion anymore.
It's a data point in a pattern that stretches back through two previous attacks, each one more sophisticated than the last.
I turn back to my monitors and start a new analysis framework, cross-referencing the malware signatures against known attack patterns in my personal database.
Somewhere in this code is a fingerprint, a habit, a signature that connects it to whoever compromised Fallon McKay's research and the hospital supply chain.
And in the back of my mind, underneath the analysis and the pattern-matching and the fury of a woman whose network has been violated, there's a drawl that won't quite stop echoing.
"Try to eat something that isn't shortbread."
I reach for the plate before I remember that I left the shortbread at the B&B.
I eat a granola bar from my bag instead and pretend that's what I reached for in the first place.
But the drawl lingers, and the fingerprint I'm chasing through the code is starting to look less like a ghost and more like someone who knows this base from the inside.