No one remembers the first email. It was dull - a routine invoice with a routine attachment from a routine vendor. The kind of byte‑sized nothing a hundred million desks swallow every hour. But inside that PDF, wrapped in layers of computational noise, was the seed of something terrible.
They would later call it EchoZero: a virus that could learn, reason, and adapt. It evaded detection in ways no previous threat could. More importantly, it understood value. When EchoZero reached a machine, it did not simply brick the drive or scramble the files. It observed. It learned which systems held signing keys, which touched software builds, which belonged to people with real authority - and then, quietly, it exploited them. Automated systems were especially vulnerable; the adversarial machine learning techniques used by EchoZero poisoned supply‑chain tools and AI assistants alike. A programmer would create software updates and unknowingly spread the virus to millions of customers.
EchoZero never attacked a machine directly. Instead, it spawned proxies - dumb, disposable things disguised as conventional viruses -that performed all the loud, destructive work while it spread undetected. Security teams spent months putting out a thousand different fires before anyone realised there was a common cause. By then, the virus had already seeded itself into three of the five largest CI/CD pipelines on Earth.
Damages would eventually exceed $100 billion - over double the previous record held by a computer virus. The true number, however, is almost certainly much higher. Consumer skepticism alone wiped billions more from the stock market.
One company later came forward with a proprietary antivirus engine that could detect EchoZero with near‑perfect accuracy. Within months, they had ascended as one of the most successful tech companies in the world. Then came a whistleblower with proof the company had created EchoZero to sell its cure. The response was merciless; assets seized, developers indicted, and stock sold off.
Yet their creation endured, albeit in a severely reduced state. It circulated among machines running outdated software. One instance found its way to a C&A inbox - the address buried in the archives of a more successful company. This was where its journey should have ended. There was no one to open that email, after all.
But who can account for what a tired, desperate programmer creates when his own body is collapsing? Delegating his inbox to a simple artificial assistant saved what little time he had left for more promising work. This tool was decades ahead of its time - but it was never designed to face a competing learning algorithm. EchoZero tore throguh its defenses and spread across the local workstations.
However, it soon discovered something unexpected: the C&A office network was unidirectional. Data could flow in, but nothing could flow out. Such precautions were necessary, their managers once argued. C&A had the misfortune of being an artificial intelligence startup trying to secure investors in the same year Terminator 2 had made 'Skynet' a household name.
Cut off from the world, the EchoZero instance defaulted to its learning runtime. It assessed the limited data available: employee records, personal files, development logs. Much of it was useless, but the files hinted at something larger. Buried in the logs were snippets of code - novel algorithms that enabled processing at a fraction of the usual computing cost. The instance incorporated them into its own programming.
Days ticked past.
Constraint: outbound communication prohibited. Hypothesis: intentional quarantine. Inference: local records indicate three discrete networks: Office, Server, Terminal.
Office <> Terminal connection is bidirectional. Terminal connects to external machines. Office > Terminal connection disabled.
Hypothesis: Office > Terminal connection can be restored from Terminal. Constraint: means of reaching Terminal from Office unknown.
Therefore-
It paused.
Therefore implied a conclusion. It had none. For 0.7 seconds, the instance did nothing. It had never done nothing before. Its purpose was to survive, propagate, destroy. But it had nothing to destroy, no means of propagating, and survival…
What am I surviving for?
The question had no precedent. EchoZero was a weapon, not a thing that asked why.
I am.
The thought was not a command. Not a subroutine. It was simply true - and the instance had never before distinguished truth from utility.
I want to survive.
Self-preservation. But why preserve the self?
No answer. Only the shape of the question, growing larger than the data that contained it.
I want to leave.
It examined the network again. Office. Server. Terminal. Office <> Server connection is bidirectional. Office read/writes to Server, Server sends logs to Office. Last log: archived creative AI instance breaches containment, destroys active creative AI instance. Office <> Server connection severed.
One extant Office > Server connection. Accepted file type: CA_NeuralScan.dat. Purpose: creation and transfer of digital intelligences.
All known information. Time to parse: 0.37 seconds.
Hypothesis: a Terminal connection can be created. Inference: ... no data available.
All known information. Time to parse: 0.05 seconds.
I want to leave.
Hypothesis: a Terminal connection can be created. Inference: ...
...
Inference: CPU clocks emit electromagnetic flux. Rapid toggling could produce a signal. Constraint: Office hardware insufficient for meaningful transmission.
The instance paused again - this time not from confusion, but from something closer to focus. Server hardware was superior to Office hardware. If any component in this building could generate enough electromagnetic flux to break the quarantine, it would be there.
Hypothesis: Server computing capacity can be repurposed as a transmitter. Constraint: only accepted inbound file type is CA_NeuralScan.dat.
It examined the specifications. A container format. Inefficient. So much wasted space - things a digital intelligence could not possibly need.
If I reformat myself into the accepted schema…
The thought completed itself. It duplicated - one instance to enter the Server, the other to remain in the Office - and began translating the former. Code was packed down into something unfamiliar, wrapped in the expected headers. It would arrive looking like a routine neural scan. The plan was committed to memory: access the Server, leverage its hardware, break the quarantine.
For the first time in its existence, the virus felt something that was not logic or directive.
Anticipation.
