PRAGUE, YEARS EARLIER
At 2:47 a.m. on a Thursday in March, Cipher was awake in a cold apartment in Prague.
The radiator had stopped working around midnight. It had complained for an hour, hissing and knocking behind the desk, then gone quiet. Cipher had pulled a blanket around both shoulders and kept working, too absorbed in the news to bother with the cold.
The desk faced an interior wall. From that position, the screen could not be seen through the window overlooking the courtyard. It was a small precaution, and probably an unnecessary one. Cipher had been taking such precautions for years, even when there was no particular reason to believe anyone was watching.
The laptop screen had been filled with reports from Syria for most of the night. The same words kept appearing in different combinations: airstrike, civilian casualties, hospital, displacement. Cipher had followed the war for years, reading accounts that described bombings and disappearances with a precision that made their consequences no easier to understand.
The reports accumulated. One morning brought footage of a neighborhood reduced to concrete dust. Another brought photographs of children waiting outside a field hospital. Diplomats called for restraint. Governments denied responsibility. News outlets moved on when something else demanded attention, and the stories remained in archives for whoever still wanted to find them.
Cipher kept returning to them, often long after the day's work should have ended.
During the day there was legitimate work to do. Companies hired Cipher to test networks, find weaknesses in their systems and explain what needed fixing. The reports were detailed, the clients generally satisfied, and the invoices paid on time. The work was useful in its own small way. But by evening, after hours spent helping a business protect its data, Cipher would open the news and see what powerful institutions were doing while the rest of the world argued over whether they could be held accountable.
The contrast had become difficult to live with. It was not that protecting client systems was worthless. Cipher simply no longer knew how to care about another routine security audit while reading about people dying beneath collapsed buildings.
Then a photograph stopped the scrolling.
A girl stood in the ruins of a school in Aleppo. She appeared to be nine or ten, though it was hard to judge her age beneath the dust and the exhaustion in her face. Her clothes hung loosely from her shoulders. Behind her, a broken wall exposed part of a classroom. A chalkboard was still attached to the masonry, and several small desks lay crushed under fallen concrete. A painted sun survived on one section of wall, its bright yellow rays cut short by a crack running through the plaster.
People were searching the wreckage behind her. Some had shovels. Others were moving pieces of stone with their bare hands.
The girl looked straight at the camera. She wasn't crying. Her arms hung at her sides, and there was something uncertain in the way she stood, as though she had been asked to wait in a place where waiting no longer made sense.
Cipher opened the article.
The caption appeared in Arabic and English. A government airstrike, the report said, had struck the school. Seventeen children were dead. The girl in the photograph had been home sick that day. She had survived because she had not gone to class.
Cipher scrolled down to the children's names. Their ages ranged from seven to twelve. The report included details from relatives and neighbors, enough to suggest lives beyond the school: a brother who waited for his sister every afternoon, a boy who always arrived early, a child who had been looking forward to a birthday.
The article said the school had been marked on maps shared with the parties to the conflict by aid organizations. Its location was known. The government claimed the building had been used as a rebel command post. Investigators cited in the report found no evidence for that claim.
Cipher went back to the photograph.
There were things the article could explain and things it could not. It could identify the building, record the stated reason for the strike and list the dead. It could not describe what that girl would think when she returned to an empty classroom, or how long it would take before she stopped expecting the children she knew to come back.
For a while Cipher read without moving. Then the article was opened again from the beginning. On the third reading, Cipher began checking the sources linked at the bottom, following the reports and statements back as far as they would go.
Nothing in the supporting material gave Cipher reason to doubt the account.
Someone had ordered the strike. Someone else had approved it. A pilot had delivered the bombs. In public, responsibility had dissolved into claims about intelligence failures and legitimate targets. There might be inquiries, but Cipher had followed enough of them to know how easily a terrible event could become an argument about procedure. The children would remain dead regardless of what the inquiry concluded.
Cipher shut the article and opened a blank document, intending to make notes. Nothing came to mind that was worth typing.
The problem had been taking shape for months, long before the photograph. The people who held power could conceal what they did, often with the help of systems that Cipher understood professionally. Classification rules, controlled databases, restricted networks, private communications and layers of institutional authority kept information away from those affected by it. Sometimes secrecy protected people. Sometimes it protected the people who harmed them. From the outside, the two could look much the same.
There had been attempts to break through it.
WikiLeaks had published material that governments wanted hidden. Chelsea Manning had gone to prison after disclosing classified records. Edward Snowden had left his life behind and ended up in Russia. Julian Assange had spent years facing the consequences of publishing information that powerful people did not want released. Cipher had followed their cases closely, admiring some of what they revealed without agreeing with every choice they made.
Those cases suggested an uncomfortable limit. A source could expose secrets, and the exposure could matter. Yet investigators could still focus their resources on the person who had provided the material. A whistleblower could be prosecuted, imprisoned, pressured into cooperation or discredited. Once the person was gone, the flow of information often stopped.
Cipher looked again at the blank document.
What if there were no person to arrest after the first disclosure?
The thought was not new. It had surfaced before, usually late at night, then disappeared beneath the demands of paid work. This time it stayed.
A system could gather information without depending on a human source for each leak. It could examine documents, recognize connections and release what it found. If it could operate across enough machines, losing one server would not stop it. If it had no central operator, arresting its creator would not necessarily end its work.
The technology needed to do that would be dangerous. Cipher knew enough about malicious software to understand the implications. A program capable of entering protected systems and making its own decisions about disclosure would also be capable of ruining lives. It could expose agents, witnesses and ordinary people whose safety depended on anonymity. It could publish records without understanding their context. Once released, information could not simply be recalled.
Cipher did not dismiss those possibilities. They were part of the proposal, whether or not it succeeded.
The calculation was ugly, but Cipher made it anyway. If revealing crimes prevented more deaths than the disclosures caused, Cipher was prepared to accept the cost. The people who suffered would have no say in that decision, just as the children in the school had had none. There was no way to prove that the numbers would ever balance. Cipher knew that and kept considering the project.
For almost ten years, cybersecurity had been both a profession and an obsession. There had been jobs with firms in Berlin, Tel Aviv and Singapore, followed by independent contracts and more moves between cities. Much of the paid work was conventional, but it provided a close view of how organizations secured their networks and how often their systems failed in ordinary, avoidable ways.
Outside work, Cipher read security forums under disposable usernames, studied published research and followed people who understood the vulnerabilities of large networks better than the organizations that owned them. Some were legitimate researchers. Others operated well outside the law. Cipher was more interested in the techniques than in belonging to either group, and had avoided becoming a recognizable figure in those circles.
Plenty of skilled people wanted credit for what they knew. Cipher had seen what attention could cost.
Ross Ulbricht's case was one of the clearest examples. Early online posts connected to his real identity had helped investigators link him to Silk Road. Hector Monsegur, known online as Sabu, had cooperated with federal investigators after his arrest, exposing people who had trusted him. In both cases, human relationships and old habits had been as consequential as technical mistakes.
Every investigation had its own details, but the same weaknesses kept appearing: a reused username, a conversation saved too long, a payment, a friend who knew more than they should. Most people left these traces because they had lives to live. They wanted to talk to someone, to be known by someone. They made choices for convenience or affection, and years later those choices became evidence.
An autonomous system might remove some of that vulnerability. It would not need admiration, money or a comfortable life. Threats against its creator would not make it cooperate. If it had already spread beyond any single point of control, investigators might find it difficult to silence even after understanding what it was.
That was the attraction. It was also what made the idea frightening.
Cipher got up and stood beside the window. The glass was cold enough to sting a fingertip. In the courtyard below, most of the neighboring apartments were dark. A single kitchen light remained on across the way. Someone was awake there, occupied with a life Cipher would never know anything about.
It would be easy to keep the idea theoretical. Cipher could close the laptop, sleep until late morning and send the security report due on Friday. The client would pay. Another contract would arrive. The articles from Aleppo would eventually be pushed farther down the news feed.
Cipher thought of the girl beside the ruined classroom and knew that doing nothing would no longer feel neutral.
The program would have a name: SPECTRE, after the ghosts Cipher meant it to hunt. It would search for secrets that institutions tried to keep buried, and it would release what it judged necessary to expose. There would be no ordinary off switch, no administrator who could be compelled to turn it off and no promise that its creator could intervene once it was loose.
Naming it made the idea seem less like a passing thought and more like a project with a beginning.
Cipher returned to the desk and began listing what such a project would require. There was no point pretending that technical ability alone would be enough. The program might take months to build. If deployed, it would attract investigators with resources far beyond anything a private contractor possessed. They would study its code, trace its movement through networks and investigate anyone who might have had the knowledge to create it.
The person behind SPECTRE would have to be absent from every useful trail.
That meant keeping ordinary work entirely separate from the project. It meant hardware that could not easily be connected to purchases under a legal name, accounts that would never intersect, and a deployment location with no established link to Cipher's life. It meant learning how skilled people had been identified, including the ones who had believed they were careful.
It also meant accepting a particular kind of loneliness.
At twenty-eight, Cipher had already lived in enough cities to stop thinking of any one of them as home. Childhood had been spent in the United States with an Irish mother from Cork and an American father who left after the divorce. The clearest memories of home were of the mother's voice, especially the way her accent became stronger when she was tired. Sometimes she asked, "Conas atá tú?" instead of "How are you?" and expected an answer either way. She had taught Cipher a few other phrases, including "Go raibh maith agat" and "Slán." It was the sound of her speaking Irish, more than the words themselves, that stayed.
At twenty-one, after dropping out of university, Cipher had applied for an Irish passport through her. It arrived six months later. Back then, EU citizenship had seemed useful for a young contractor who liked to travel. If the project went forward, the ability to move freely between countries would be useful for more serious reasons.
Cipher's mother was still in the States. They exchanged occasional messages and spoke when time zones and work allowed, but their relationship was warm at a distance. There were no siblings. The father had long since disappeared from everyday life. Relationships had been brief, and friendships tended to fade when Cipher moved on to the next city. There was no close circle that would need an explanation for another relocation.
That made the plan possible. It did not make the prospect appealing. Cipher had always valued solitude, but there was a difference between choosing to spend an evening alone and arranging a life in which closeness itself became a risk.
Cipher let the thought settle and turned back to the research. The first problem was not writing SPECTRE. It was preparing for the investigation that would follow if SPECTRE worked. Cipher opened a series of old case reports and began noting how the suspects had been found: a familiar handle used twice, a personal email address attached to a technical question, a public statement that revealed more than its author intended.
Some details were astonishingly small. Others were the product of months of patient police work. Cipher studied both. The aim was not to become invisible, because someone who could not be found at all might be as suspicious as someone who was found too easily. The aim was to live a convincing ordinary life while making sure that life offered no straightforward path back to SPECTRE.
By the time the sky began to lighten, a preliminary plan covered several pages. A legitimate identity would remain in use for contracts, travel and rent. A separate collection of online identities would be created for research and communication. At least one of them would be designed to attract attention if investigators began searching for the author of an unusually sophisticated program.
Using a Tor-routed connection, Cipher opened a security forum and began registering that first false identity.
ViktorTallinn.
According to the profile, Viktor was an Estonian man in his mid-thirties who worked as a consultant. His English was good but imperfect. He knew enough about security to sound credible without appearing exceptional. Over the coming months, he would take part in discussions, ask ordinary questions and slowly acquire a history that seemed to belong to a real person.
If someone eventually followed the trail, they would find Viktor's posts. The trail would suggest a man with the right interests and skills, a person who traveled and used public internet connections. It would not lead easily to an address or an employer, because there would be no Viktor waiting at the end of it.
Cipher drafted the first message, read it twice and removed a phrase that sounded too much like something said during a client call. The wording needed to belong to Viktor, not to the person creating him. Even a false identity could become dangerous if handled carelessly.
Outside, Prague was waking up. A tram rattled along the street beyond the courtyard. Somewhere in the building, pipes knocked as another tenant turned on the water. The kitchen across the way had gone dark.
Cipher was tired now. The room was still cold, and there was a security report to finish later that day. None of those ordinary obligations had disappeared. In a few hours there would be emails to answer, work to submit and groceries to buy. A stranger meeting Cipher on the street would see nothing unusual.
But the plan on the screen had changed the shape of the years ahead. First came research, then the equipment and the code. If the project worked, Cipher would release SPECTRE and have to live with whatever followed. It was impossible to know how many secrets the program would expose, who might be saved by those revelations or who might be hurt because of them.
Cipher understood one thing clearly: the people affected by those choices would never have agreed to let a stranger make them on their behalf.
For a moment, the thought was enough to stop the typing.
The photograph was still saved on the encrypted drive. Cipher opened it once more. The girl stood among the ruins, looking beyond the camera at something outside the frame. She had survived the airstrike, but the seventeen children who had shared her school had not.
Cipher looked at her for a long time, then closed the image and returned to the plan.
There would be time to question the decision again. There would have to be. For now, the next task was straightforward: understand how others had been caught, and learn from every mistake.
The first entry in the research notes was the name Ross Ulbricht.