2. The Eleven-Week Hunt
The Eleven-Week Hunt
JULIAN
I’ve been awake for twenty-one hours. Three empty espresso cups sit in a neat line at the far edge of the desk.
I operate with a certain minimum standard even in a rented server room above a laundry facility in Taipa.
I’m in thermal and tactical pants. My field kit is packed and waiting by the door.
Which is all to say, I’m ready.
Patience is a skill. The consequences of lacking it are worse than the cost of acquiring it.
This wait feels different.
Eleven weeks mapping her mind requires an entirely different architecture than eleven weeks mapping a system.
Systems are static between interactions.
She leaves residue—the vine, the specific routing choices, the operational decisions reflecting a personality rather than a protocol.
I’ve been reading it in layers, each breach a new paragraph in a document significantly longer than my initial estimation.
The vine is what I’ve been waiting for. It bloomed across the Cyprus server’s login panel at 03:14 Macau local.
Finally.
I’ve been tracking her for eleven weeks, three days, and approximately fourteen hours.
The vine animation shifts slightly with every deployment: different color saturation, different growth speed, different termination point. Organic. It’s her telling the system the session is closing—the digital equivalent of a distinctive knock on a locked door.
She knows she’s knocking. She doesn’t care who can hear it from the other side.
I found the first instance in a breach at a pharmaceutical subsidiary in Zurich, seventy-six days ago. Routine surveillance sweep. A cascade failure in the cloud backup protocols carrying the quiet, clinical destruction of someone deliberately leaving a calling card.
Right at the termination point. Forty seconds of animation on the compromised session before the connection drops.
Why a vine?
Two weeks on that single question. The answer, archived in a message board from 2007, provided the baseline structure.
The board was a technical forum—obscure, mostly abandoned, existing before modern platforms consolidated the internet’s fringe intelligence.
She posted under the screen name Ivy starting in 2007.
Her first post was a debugging question. Her second post answered someone else’s debugging question in a way the person asking clearly hadn’t expected from a new account with zero post history.
Over seven years and seventeen different IP addresses, she used that forum to learn and, occasionally, to help people who posted problems she found interesting.
The IP addresses, mapped, gave me placements across four states.
The posting history provided the specific texture of a mind building itself in the only continuous space it had.
She signed her posts with a small graphic. A hand-coded ASCII vine, the same character arrangement in every message, slightly different in execution—the same way this vine animation is different every session.
It’s her signature. The same one she’s been leaving on servers for the last three years.
She’s been Ivy her entire digital life.
The vine isn’t carelessness. It’s identity. The only constant she had.
Back to the Cyprus server. Back to the green rain cascading across my tertiary monitor.
She’s burning eleven million dollars per minute.
Eleven million.
Per minute.
Fascinating.
Ballsy.
The routing architecture is extraordinary—shell companies threaded through four tax jurisdictions, satellite bounces in low Earth orbit, packet fragmentation down to forty bytes.
She’s meticulous.
Confident.
She’s also leaving the door open long enough to route through two hundred million dollars. She’s emotionally involved with this particular target.
She’s made this confidence-driven mistake before.
The vine lands at 03:14:07. I have it sandboxed by 03:14:12.
I wrote the counter six days ago when I identified the payload signature in code artifacts she left on the Cayman server three weeks prior.
She thought that breach was clean.
Fourteen bytes in, the session log matched the vine’s organic growth algorithm. I extracted it, reverse-engineered it, built an isolation container to receive the malware, quarantined it in a stripped virtual environment, and severed the active executable from my actual system.
Four days ago, I also wrote a small message, in plain text, and attached it to the sandbox’s exterior—the surface she’d see if she sandboxed back. She will, if she’s as good as my profile suggests.
I assigned it a 70% probability.
She’s better than the profile I built out. She sandboxes back in 4.7 seconds.
The vine blooms directly into a box from which it can’t escape. The bridge she thought was her malware chomping through my OS is a live terminal connection.
It’s a little theatrical.
I know.
Eleven weeks of surveillance earns a degree of theatricality.
> Nice trick. Is that Poison Ivy or just a weed?
Four seconds of cursor blinks on my screen.
Three possible responses: she closes the connection, she cuts power, or she writes back.
She writes back.
> It’s an invasive species. You should wear gloves.
The words stay on the screen.
She’s funny.
Three seconds. That’s a problem.
The 4.1 seconds between my message and her reply is the exact pause of someone who thought of a funnier answer and decided against it.
She’s twenty minutes into an active breach with a foreign operator at her root access, and she’s editing for tone.
Humor under an active breach is a real-time intelligence test. She assessed my capability to receive the joke.
She’s right.
The actual woman is responding, rather than the profile.
I continue.
> I prefer bare hands. Who are you?
I type this without entirely planning to. It’s a true thing offered to an active target.
An operational deviation for me, but I do it anyway.
> I’m the Chaos Agent.
I stare at this for 0.6 seconds before I type back.
> Unlikely. That’s my title. You’re stealing my vibe.
It is my title.
Task Force 9 calls Julian Rhodes when something needs dismantling at the architectural level—the system, the network, the entire operational premise. Boyd is the wall. Dax is the blade. I’m the reason neither of them ever walks into a room that hasn’t already been opened.
I stare for 0.6 seconds because I found that exact phrase in her operational notes.
A document I extracted from a dead message board server fourteen weeks ago, encrypted under a password she rotated quarterly and hadn’t rotated since the previous April.
A working document—notes to herself, tool names, framing.
Chaos Agent. No definition. She didn’t think it needed one. She’s using it back at me.
She’s performing confidence, or she’s treating this terminal like a conversation with someone worth being her actual self with.
She used it first. I note this.
> I’m not trespassing. I’m fumigating. This money is dirty.
> That’s not why I’m here. Stop the burn.
> Make me.
I don’t smile at live terminals. Personal rule.
Make me is the pure defiance of someone receiving a direct command and answering it as a dare. She’s got me grinning ear-to-ear.
I launch the inverted DoS.
Bandwidth starvation—collapse the available network around her rather than flooding her with traffic, forcing the local router to drop packets and crash the session.
She’s routing two hundred million dollars simultaneously.
Her local bandwidth is already stressed. She has forty seconds, give or take.
The connection dies at second twenty-two.
Clean severance, no error code. She didn’t wait for the crash. She manually cut the power—and a hard power cut on a rig that size registers to a directional antenna on a local cell tower exactly like a gunshot.
I pull the last metadata packet from the session. Router identifier. Building network address. Cell tower triangulation from the electromagnetic spike at power cut.
A wing. A floor. Three possible rooms in a hotel on the Cotai Strip, Macau, identified by the building network’s DHCP record.
I pick up my phone.
There is one active device in those three rooms. I mapped her burner cycling pattern: new number every 48 hours, Singapore broker is the relay. The last cycle logged 31 hours ago. She has 17 hours left on this number.
I type four words and send.
`FOUND YOU.`
I put the phone down.
She has ninety seconds before she’s out of the room. Sixty before she’s in the elevator. Thirty before she decides which exit she trusts.
I already know which one she’ll take.
I’ve been tracking her for eleven weeks. My profiles are thorough.
Age: late twenties. Background: seven-plus foster placements across four states and one UK stint.
Self-taught cryptographer from age thirteen.
Published a paper on packet fragmentation under a pseudonym at nineteen that is, objectively, one of the most elegant treatments of the problem I’ve read.
I would cite it in my work if citing it didn’t involve explaining where I found it.
She’s been targeting the Consortium’s financial architecture for three years. She’s burned or rerouted an estimated $600 million in Consortium funds. Eleven server breaches. Never physically detained. Never identified in person by Consortium operatives. Never used the same operational base twice.
The most disciplined solo operator I’ve ever tracked.
She’s also been running on instinct and grief with no institutional backing, no protocol, and no exit plan for three years. Disciplined at this particular variety of damage and completely ungoverned on everything surrounding it.
I’d say she’s the most dangerous person I’ve tracked, but the word feels too small. She’s a weaponized equation with a grief algorithm running underneath it. Pure, unadulterated, grief-driven chaos.
At first, I thought she was just another ghost. That she’d evaporate like the others. But she doesn’t. She builds. She adapts. She learns. She outpaces me at every turn.
I find that incredibly exciting.
The profile fails to capture the shape of how she thinks. She doesn’t iterate—she solves. Each breach is built from zero. The Cyprus routing is a variant on a method I’ve spent two years failing to reconstruct from the Cayman artifacts.
Her solution is more elegant than mine would have been. I’ve been doing this for a long time. I don’t use that word lightly.
The fabric of her mind fascinates me.
It took me four weeks to find the motive.
Marta.
I didn’t need to find Marta to run the operation. I found her because the behavioral pattern—the specific targets, the burning rather than stealing, the consistency over three years—indicated a personal motive of an intensity pure ideology doesn’t generate.
Ideology fades. Grief compounds.
Asset G-447. Gemini Foundation. Liquidated 2022. A profile picture on a message board. A girl in Kyiv, avatar updated once a year, last changed in 2021. It matched a Gemini Foundation intake photograph at 94.3% facial recognition confidence.
Her name was Marta. She was twenty-three. She sent a message about going to the States for medical care and was never heard from again.
Marta wasn’t a target. She was inventory.
The Consortium didn’t decide to kill her—it processed her, the way it processes everyone the Gemini Foundation brings in.
A medical visa, a charity’s letter, a girl who needs a way out.
The Foundation moves her. The Consortium files her.
Somewhere in the routing she stops being a person and becomes a line marked liquidated.
Which brings me to why I’m in Macau. There’s a gap in the intelligence.
The Hardware Security Module.
The HSM.
It’s a physical device she extracted from the Consortium’s primary banking server eighteen months ago. Their master ledger, with encryption keys, routing architecture, and beneficial ownership records for every Board-level account in the last seven years.
If she has it, it’s the single most actionable piece of evidence against the Consortium in existence.
I confirmed she accessed the server. I confirmed the HSM was removed. I have no signal, no trace, no delivery record, no storage facility with her legend on file, no indication of a physical location.
In eleven weeks of surveillance, this is the only gap in the map.
She hid it somewhere that doesn’t triangulate. No digital trail. No physical paper.
Where would a woman who trusts nothing and no one put the one thing she can’t afford to lose?
I’ve turned this over for six days. The answer won’t sit still. There’s a third option beyond carrying it on her person, like using a dead drop with a known contact. Another possibility surfaces in the back of my mind.
She put it somewhere obvious. Somewhere logic would rule out.
I don’t have the answer. I have to get it from her.
But that’s okay. As good as I am with systems and algorithms, I’m even better at this face-to-face.
The target is moving. She is, at this moment, somewhere in the Cotai Strip’s transit infrastructure, executing a pre-planned exit she’s been modifying in real time since the moment my message hit her screen.
She’s fast, she’s resourceful, and she has three years of survival instinct backing every decision.
She will not expect me to already be in Macau. She’ll expect me behind a screen in Singapore, running algorithms, building triangulation models, working the problem remotely.
Working the problem remotely is slower. She is faster than her profile initially indicated.
Chaos Agent. Her phrase. Her title.
I look out the cab window at the Macau predawn. The harbor is going gray at the waterline, the container ships sitting low and dark in the water. Too many cab windows in too many cities. Tonight the operation fades behind the 4.1 seconds.
Taking 4.1 seconds to decide she’d rather be accurate than fast.
I do that.
I’ve never met anyone else who does that.
She’s wrong about who owns that title. But I take her point.
Somewhere in this city is a woman who’s been burning the Consortium’s money for three years. Who codes like she’s daring the system to catch her. Who named her malware after something that grows back stronger every time you cut it down.
She’s moving, and she has a head start, but I know which parking garage she’s heading for.
I’ve known for four days.
I’m better at this than she thinks.