Page 11

“Yes, sir. Moving slowly, but still inside.”

I make a decision. “Do not shut down the system.”

The analyst’s fingers freeze over his keyboard. “Sir?”

“If we shut down now, we lose our chance to identify them. Let them continue for now.”

Andrei shifts beside me. “Maxim, this isn’t just minor probing anymore.”

“I know. I said this last time, and I’ll say it again. Monitor them only.” I don’t look away from the screen. “They’ve been here for almost a whole day. They’re not going to run just because we’re watching.”

I pull up a chair and sit down in front of the secondary monitor. The analysts exchange glances, but they know better than to question me. I start tracing the hacker’s path through our systems, moving backward from their current position to their point of entry.

The work is meticulous. Every node they touched, every pathway they explored, every security measure they bypassed—I document it all, building a map of their journey through our network. The pattern that emerges is unlike anything I’ve seen before.

Most hackers follow predictable routes. They exploit known vulnerabilities, use standard tools, move in ways that reflect their training or their lack of it. State actors are methodical but rigid. Criminals are opportunistic but sloppy. This hacker is neither.

They adapted. At every junction where our security could have stopped them, they found an alternative route. They saw the architecture the way I see it: as a structure with logical pathways and hidden weaknesses, designed to keep people out but built by people who assumed no one would look hard enough to find the cracks.

This is not a team. Teams leave inconsistencies; different skill levels, different approaches, small errors that reveal multiple hands at work. This is a single operator, moving with a consistency of style that speaks to one mind, one methodology, one person sitting at a keyboard somewhere, making decisions in real time.

A single operator who understands systems better than anyone I’ve encountered.

“Kirill.” I don’t look up. “How did we miss this?”

Kirill steps closer to the screen. “The initial intrusion was flagged as anomalous traffic, as you know. Standard protocol is to monitor and assess before escalating. By the time we confirmed it was a genuine breach, they were already inside the restricted layers.”

That’s a problem. Our automated monitoring is good, but it’s not designed to catch someone who moves like this. The hacker knew how to stay below the threshold of automatic detection, how to make their presence look like background noise until they were deep enough that it didn’t matter.

I continue tracing. The deeper I go, the more I see the hacker’s methodology. They reused certain code structures—small, efficient scripts that performed specific functions. Not standard tools, not off-the-shelf software. Custom-built, tailored to our specific architecture, designed by someone who took the time to study our systems before making their move.

Then I find it.

There’s a signature buried in the code. A pattern of code that functions like a fingerprint, unique to the person who wrote it. It’s the kind of thing most people would never notice, hidden in the structure of the scripts themselves rather than in the data they access.

I’m not most people.

I isolate the fragment and run it through our internal databases. Nothing matches. I expand the search to external sources: dark web forums, hacker collectives, cybersecurity research papers. Still nothing. This identifier doesn’t appear anywhere in our records.

Which means one of two things: either this person has never been caught, never been flagged, never left a trace of their work anywhere that our intelligence can reach… or they’re so good that they’ve been operating at a level where their work doesn’t get noticed by anyone who would report it.

Either way, I’m impressed.

I flag the identifier and store it for direct tracking. If this person ever uses this code structure again, I’ll know.

“Maxim.”

Ivan’s voice comes from behind me. I turn to look at my brother. He’s been standing in the corner of the room since we entered, watching the proceedings with his usual calm. But there’s something in his expression now.

“What do you see?” he asks.

I stand and face him. “They were a professional. Someone with resources, training, and a level of skill that suggests they’ve been doing this for a long time. They moved through our systems like they knew where they were going. Not because they had inside information, but because they understood how systems like ours are built.”

“A rival organization?”

“Possibly, but the methodology doesn’t match any known group. This is a single operator.”

Ivan raises an eyebrow. “You’re sure?”