Andre M. Pietroschek
The Duplicitous Network - Criminal Internet Abuse
THE DUPLICITOUS NETWORK (Premium AI-Sloppery)
© Andre Michael Pietroschek, all rights reserved
This is a proofread raw draft edition, as sleep deprivation & caffeine impaired my efforts. Unpaid efforts that I minimize.
Disclaimer: No warranties!
Chapter 1: The Precondition
"How did you come to realize that you weren’t engaging with the authentic internet?"
The question reverberates in the stark emptiness. The walls, devoid of color, stand unyielding. This room exists beyond the confines of time and place, a suspended chamber designed for probing the depths of consciousness.
"I didn’t know for certain," the subject replies, a hint of vulnerability lacing their voice. "It was an instinct. Everything felt too pristine."
"But the authentic internet is clean."
"No. The authentic internet is flawed. It falters. Time and again. Genuine systems deteriorate. True networks are filled with noise." A pause lingers, heavy with uncertainty. "This system never faltered."
The interrogator leans forward, an enigmatic silhouette devoid of features, embodying the essence of inquiry.
"So, was it the perfection that led you to question its authenticity?"
"Perfect systems are an illusion. They do not exist in the tangible world. When you inhabit something flawless, your very being senses the deception. Your mind becomes attuned to the absence of friction."
"Friction."
"The resistance that confirms something is genuine. It demands effort to navigate. Authentic networks—true existence—everything requires friction. Every interaction must be negotiated. The counterfeit network offered me everything effortlessly."
The interrogator reclines, the soft creak of the chair a subtle reminder of physical reality.
"When did your suspicions first arise?"
"I can’t pinpoint an exact moment. It was a gradual realization. I felt as though I was living inside a photograph of reality. Everything appeared correct, yet something in the image felt amiss. The perspective was subtly skewed. The shadows cast in impossible angles. It was only discernible upon closer inspection. Most people overlook the details."
"And you did not."
"Eventually. I spent countless weeks grappling with the fear of losing my sanity. I checked my emails, my bank accounts, and my work systems. Everything operated flawlessly. Yet that very perfection was the root of the issue. Perfect systems are treacherous. They are the very entities that deserve our distrust."
The interrogator remains silent, the quiet stretching into a profound question.
"Are you still ensnared in this counterfeit internet?" the subject posits, deftly flipping the interrogation’s focus.
"I cannot say for certain," the interrogator responds.
"How would you discern the truth?"
"I wouldn’t."
The stark whiteness of the room endures, the interrogation oscillating between continuation and conclusion, an indistinguishable line blurring the boundaries of inquiry and resolution, of knowing and doubting, of entrapment and liberation.
When the light shifts, neither participant perceives the change.
Chapter 2: The Ordinary Internet
Mareike Tadpole sat across from the hotel security director, his hands quivering as he recounted the loss of fifty thousand customer records—a breach so commonplace it barely stirred a headline.
“The encryption was outdated,” he admitted, his voice thick with resignation. “We were aware of it. But each year, the budget was slashed. We kept promising ourselves, next year, next fiscal cycle.”
Mareike refrained from taking notes. This narrative had become a ritual, its rhythm familiar and wearying. The specifics might shift, but the underlying melody remained unchanged: inadequate security, recognized vulnerabilities, exploitation, damage, budgetary constraints, and hollow apologies.
“How many customers are still in the dark?” she inquired, her tone steady.
“Forty-seven thousand. We’ll notify everyone by the end of the week.”
Forty-seven thousand individuals would soon discover that the hotel chain they had entrusted with their credit cards, their names, and their addresses had stored it all in a database so vulnerable that a moderately skilled hacker could breach it in less than an hour. Forty-seven thousand souls blissfully unaware of how tenuous their security truly was.
As the hotel director continued, his voice dwindled, overshadowed by the weight of his confession. Mareike listened intently, but her gaze remained fixed on his trembling hands. Fear manifested physically; the nervous system had a way of betraying genuine guilt. This man was haunted—not just by the breach but by an overwhelming sense of powerlessness.
“We’re offering free credit monitoring for three years,” he said, as though that could somehow mitigate the damage.
Three years. As if the repercussions of identity theft could be contained within such a time frame, as if the scars of betrayal had an expiration date.
Stepping outside the hotel, Mareike watched the bustling street. Office workers, tourists, delivery drivers—each one placing their trust in systems that scarcely deserved it. Every individual carried digital representations of themselves: names, purchase histories, preferences, medical records, and financial data—all stored in servers overseen by those who lamented breaches yet remained impotent to prevent them.
With twenty-five years of experience as a private investigator, Mareike had once found clarity in her work: trace the crime, identify the perpetrator, gather evidence for prosecution. Yet over time, the landscape of crime had morphed. It had become institutional, systemic—a reflection of structures that enabled wrongdoing, rather than isolated acts of individuals.
She settled into a café, coffee in hand, observing patrons absorbed in their laptops. Open networks. Unsecured connections. Banking details entered in public spaces. People lived their digital lives as if the internet were a sanctuary.
Mareike pondered: if they truly grasped the fragility of their digital security, would they continue to engage with these systems? Undoubtedly, they would. They had no alternative. That was the cruel irony—not merely the failures of security, but the realization that trust was a necessity, not a choice.
As she opened her laptop, she meticulously checked her email through a VPN, navigating proxies, encrypting, and rerouting. Even for someone well-versed in vulnerabilities, someone who had witnessed countless breaches, completely evading the system was a fantasy. One could make exploitation more challenging, but never impossible.
A young woman at the adjacent table entered her banking password, her characters masking themselves as dots on the screen. Oblivious to her exposure, she sipped her overpriced latte, unaware that the café’s WiFi likely lay compromised. Anyone with rudimentary packet-sniffing tools could intercept her data, reading her password in real time, accessing her account while she remained blissfully unaware.
Mareike remained silent. What purpose would it serve to alert strangers to a danger they could hardly safeguard against? To provoke fear without offering solutions was to sow paranoia. Better to allow them the comfort of ignorance until reality forced their eyes wide open.
After finishing her coffee, she returned to her office. The hotel breach would be resolved swiftly. Damages would be paid, new security protocols implemented, and within a year, they would likely revert to the same vulnerabilities. Structural issues could not be mended through individual efforts; they demanded systemic change, and such change never occurred at the pace of institutions.
That evening, Mareike found solace in her living room, surrounded by books—real, tangible volumes. The analog reassurance of her own cautiousness. She had fashioned a life around trusting that which could be held, that which existed in the physical realm. Her emails were encrypted, her communications routed through carefully chosen services. Yet, even her most secure conversations left traces; even her meticulously curated digital life remained susceptible to scrutiny if someone was sufficiently determined.
She contemplated the hotel guests whose data had been compromised. Most would never know who had seized it or what the attacker intended to do with the information. The crime would exist in an abstract realm—an event that transpired without their awareness. This was a different kind of violation: not a robbery where one could identify the loss, but a theft where the absence itself remained shrouded in invisibility.
Chapter 3: The Architecture of Trust
Cole Harper immersed himself in a security research paper within the confines of his apartment, where the sole illumination emanated from the glow of his monitor. Engaged in a separate investigation—one entangled in corporate espionage with ISP employee access to client data—he found himself drawn deeper into the intricate web of internet infrastructure.
The paper bore the unsettling title, "The Perfect Man-in-the-Middle Attack: Infrastructure-Level Impersonation as a Form of Institutional Control." It was a theoretical piece—academic in nature—published in a rather obscure security journal three years prior. Since then, it had languished in the shadows, scarcely cited by anyone. Cole surmised that the reason for its neglect lay in the disquieting implications it presented.
The author articulated a chilling concept: a sufficiently resourced entity could stealthily position itself between users and their true destination servers. This was no ordinary man-in-the-middle attack, detectable by conventional security systems. No, this threat struck at the very foundation—an impersonation at the infrastructure level, effectively spoofing the ISP itself.
What made this attack particularly insidious was its almost imperceptibility.
Every website a user accessed would appear to load seamlessly. Services would operate as expected. Emails could be sent and received without a hitch. Banking transactions would proceed uninterrupted. Social media feeds would flow freely. The user would navigate the internet as they always had, blissfully unaware that every single interaction was being siphoned through the attacker's machinations.
The implications of such an attack were staggering:
The perpetrator could monitor all traffic, surveilling every page visited and intercepting every credential entered. They could modify content before delivering it to the intended destination, harvest financial data, inject malware, create false accounts in the user's name, and impersonate legitimate institutions—all while the user remained convinced they were engaging with the authentic internet.
The technical prowess required for such an operation was formidable. The attacker would need:
Access to significant network infrastructure, a profound understanding of routing protocols and ISP systems, the ability to spoof DNS records, and the capacity to handle vast volumes of traffic. Furthermore, they would require legal immunity or operational security robust enough to evade detection.
Cole paused, absorbing the weight of that last point: legal immunity. The author had phrased it with precision, yet the implication was stark: this type of attack would necessitate collusion from institutions that are typically tasked with preventing such breaches—government agencies, telecom companies, organizations that possess the power to shield ISPs rather than assault them.
He continued reading.
The author elaborated on how this attack could evolve into something even more sophisticated. The counterfeit network could become indistinguishable from the real internet—not merely a mimicry, but a superior alternative. Faster response times, more reliable connections, and better uptime than the genuine article. Users might actually prefer the counterfeit network if they were aware of it. Yet, they would remain blissfully ignorant.
The author concluded provocatively: "An actor capable of executing infrastructure-level impersonation might not be acting criminally in any conventional sense. They could be engaged in what they perceive as security research, national interest, market dominance, or even public benefit. In this context, legality becomes secondary to ethics, and ethics become secondary to detection. An undetectable attack is not a threat; it is simply reality."
Cole closed the paper, enveloped in the eerie silence of his apartment. No smart devices cluttered his space, no networked systems intruded upon his thoughts. He had constructed his life around the belief that digital systems were knowable, that meticulous scrutiny could reveal their essence. Yet, the paper suggested a far more disconcerting truth: systems could be so exquisitely designed that understanding them became an impossibility. Trust, it seemed, was not merely a choice; it was an absolute necessity. The very fabric of the internet could be compromised at such a fundamental level that no individual precaution would suffice.
He glanced at the time on his analog clock. 7:47 PM. A quick check of his laptop's system clock confirmed it matched. A small reassurance that his reality remained intact.
His mind drifted to his career—a tapestry woven over two decades of investigations and hundreds of cases. How many of those cases had leaned heavily on digital data? Email searches, digital financial records, cloud storage forensics. If the internet itself could be undermined at the ISP level, what credence could be given to any of that evidence?
The question loomed, unanswerable.
Rising from his chair, he strode toward his filing cabinets—sturdy metal boxes housing tangible records. These were the only forms of documentation he fully trusted. Initially, he had seemed paranoid to Mareike when their partnership began, but now, twenty-five years later, she had gradually adopted similar habits. Not as extreme as Cole, but undeniably moving in the same direction. They both grasped a truth that had eluded most in the digital age: trust was a vulnerability, systems were fragile, and the most treacherous vulnerabilities were those that lay hidden from view.
Returning to his desk, Cole searched for news—anything related to ISP compromises, infrastructure breaches, or unusual network activities. He unearthed nothing specific, yet stumbled upon something far stranger: a complete void of pertinent information. No research papers have been published in the last two years concerning ISP-level attacks. No alerts from security agencies. No academic discourse on the very infrastructure upon which lives depended every second of every day.
The absence of information spoke volumes.
He made a note: Research funding in ISP security appears to have dwindled. Why? Who stands to benefit from this decline? He refrained from jotting down the implications; they were too glaring. If a party wished to orchestrate a flawless infrastructure-level attack, its first order of business would be to diminish the number of researchers probing such vulnerabilities. They would aim to render the field less appealing, diverting brilliant security minds toward problems that yielded funding, publications, and profit, not theoretical weaknesses in systems that most preferred to ignore.
As he sat in the quietude of his apartment, a crack began to form in the fortress of his confidence. The systems he had once believed in were not merely vulnerable; they might be irreparably compromised in ways that meticulous investigation could never uncover. The world he had dedicated his career to understanding might itself be an enigma, forever beyond his grasp.
Chapter 4: The Fear
Mareike drove through Portland's west hills toward the house she'd bought fifteen years ago. No smart home devices. No connected systems. She'd installed them once—programmable thermostat, networked lighting—and then spent a week systematically removing them. Too much access. Too many vectors for intrusion.
She pulled into her driveway. The house sat quietly among the trees. Inside, she made tea using an electric kettle that had no internet connectivity, no Bluetooth, no neural network. Just heating elements and water. The simplicity felt like a small victory.
Her bookshelf dominated the living room. Thousands of books accumulate over decades. Each one is a physical artifact of thought. She moved through them, trailing her fingers across spines. Novels about paranoia. Philosophy about epistemology. True crime accounts of investigations that had solved cases through patience and procedural methodology.
She thought about the hotel breach. The way the security director had trembled. The way forty-seven thousand people would soon learn that their trust had been violated. The way nothing would really change because the structures that allowed those violations had no incentive to change themselves.
Mareike poured tea and sat in her living room's darkness. She didn't turn on the lights. The last light of evening came through the windows—enough to see by. Enough to remember that the physical world still existed outside of networks and data streams.
Her phone—a burner, minimally networked, regularly swapped out—sat on the table. No apps except for calls and texts. No location services. No way to track her except through the cellular network itself, and she was paranoid enough to limit her phone use to necessary communication.
She called Cole. He answered on the second ring.
"You've been reading security papers again," Mareike said.
"How do you know that?"
"Because I know you. What did you find?"
Cole described the paper. The perfect man-in-the-middle attack. The theoretical possibility of an infrastructure-level compromise. Mareike listened without interrupting. When he finished, she said, "That's already happening."
"We don't have evidence of that."
"We have evidence of ordinary breaches at ordinary scales. We don't have evidence because we don't have frameworks to detect it. If someone wanted to compromise ISP infrastructure without anyone noticing, the first step would be to ensure that security research stopped looking for it."
Cole was quiet for a moment. "You're saying someone is actively preventing research into the vulnerability?"
"I'm saying the vulnerability exists theoretically. I'm saying the incentive to exploit it is enormous. I'm saying if it were being exploited, we'd see exactly what we see now—nothing. Complete absence of detection."
"That's not how an investigation works. Absence of evidence isn't evidence of absence."
"No. But absence of research into specific vulnerabilities while those vulnerabilities become increasingly severe—that's something. That's worth noticing."
Mareike drank her tea. Bitter. Too strong. She'd steeped it too long, watching shadows change outside her window.
Cole said, "We shouldn't jump to conclusions. We should wait for actual evidence."
"I agree. But I want you to think about something. How many of our cases have relied on internet data?"
"Most of them."
"And if that data was being intercepted, modified, or redirected at the ISP level, how would we know?"
"We'd compare it against the actual evidence. Financial records, credit card statements, phone records."
"All of which flow through networks. All of which could be modified at the infrastructure level."
Cole didn't respond. Mareike could hear him breathing through the phone—proof of his physical presence, at least.
"I'm not saying we're being investigated," Mareike continued. "I'm saying it's possible. And if it's possible, we should assume it's happening."
"That way lies total paranoia."
"I prefer to think of it as appropriate caution."
After they hung up, Cole sat in his apartment and felt the shape of doubt. He'd spent his career believing in the integrity of systems. That evidence could be gathered. That investigation revealed the truth. That the world was knowable if you were sufficiently careful.
But what if the foundation of that knowledge was corrupted? What if the systems you were using to investigate were themselves compromised?
He pulled out a yellow legal pad—analog, irreplaceable, impossible to modify digitally—and began writing down his paranoia. Making it concrete. Giving it shape. If his thoughts were going to be paranoid, they might as well be systematic about it.
At the top of the page, he wrote: "Assumptions worth questioning."
Then: Can I trust my own email? Can I trust my banking information? Can I trust traffic data? Can I trust my own investigation methods? Can I assume the clients are who they say they are? Can I verify anything without relying on networks?
He filled two pages. By the time he was done, exhaustion had set in—the deep weariness that came from suspending necessary trust for too long. You had to trust some systems, or you went insane. But which ones? And what happened when you guessed wrong?
Mareike lay in bed that night, unable to sleep. She thought about the ordinary violations happening at that moment. The hotel breach is still being discovered. ISP employees are accessing customer data out of curiosity. Hackers are working through lists of stolen credentials. The systematic, banal exploitation of human information that occurred constantly and would continue occurring regardless of what she and Cole believed about the integrity of systems.
And underneath that: the possibility of something worse. Something so foundational that individual exploitations seemed trivial by comparison. Something that made the difference between security and vulnerability essentially meaningless.
She got out of bed and walked to her window. Portland spread below in scattered lights. Thousands of people in those lights, all of them using devices that connected to networks that might or might not be trustworthy. All of them are living on what might be a false internet without any way to know.
The thought should have been paranoid. Instead, it felt simply realistic.
Chapter 5: The Contract
The man who walked into their office on Tuesday morning was carefully dressed and terrified. Cole recognized the combination immediately—someone wearing professionalism like armor against fear they couldn't quite articulate.
"My name is David Marks," he said. "I think someone's stealing from me. I think it's my ISP."
Mareike and Cole exchanged a glance. Not quite the usual claim, but not entirely unusual either.
"Have you contacted your ISP's support?" Mareike asked.
"Multiple times. They say everything is normal. They checked my account, and they said there was no unauthorized access. But I'm getting charged for services I'm not using. My websites are being accessed when I'm not accessing them. My files are—" He stopped, searching for words. "They're different."
Cole said, "Different how?"
"Updated when I didn't update them. Modified in ways I can't explain. I had an Excel spreadsheet with financial data. The calculations changed. The math still worked out, but the numbers were different. I know I didn't change them."
Mareike leaned forward. "You're saying your files are being modified by someone with access to your account."
"I'm saying something is modifying them. Or I'm going insane. That's also possible." He said it without irony, with the genuine uncertainty of someone who'd begun to question their own perception of reality.
Cole asked, "Have you contacted the police?"
"Yes. They said I should contact my ISP first, and my ISP says I should contact the police. Neither one thinks this is anything unusual."
"Because it probably isn't," Mareike said. "Account compromises happen constantly. Hackers use credential stuffing, phishing, and social engineering."
"I have good passwords. Very good. And I use two-factor authentication."
Cole said, "Then how did they get in?"
David didn't answer. He just sat there, looking at them with the expression of someone who'd exhausted rational explanations.
Mareike said, "Let me ask you something different. When did you first notice something was wrong?"
"Three weeks ago. But I've been getting this feeling for longer. Like something wasn't quite right. But I couldn't identify what. Everything worked fine. Email, banking, everything. But it felt—"
"Felt how?" Mareike asked.
"Too smooth. Like everything was happening exactly the way I expected it to, without any friction. Real life has friction. Real interactions have delays, glitches, and unexpected results. But everything I was doing online was just... working. Perfectly."
Cole and Mareike looked at each other again. This was the detail that caught them both. Not the account compromise, which was ordinary. But the testimony that something felt wrong through its perfection.
Cole said, "I'd like to run some diagnostics on your systems. We can check for malware, unauthorized access, and credential compromise. It'll take a few days."
"How much?" David asked.
"Retainer of two thousand. Plus hourly rate for the investigation."
David nodded. He didn't even haggle. That was how you knew someone was frightened—they'd stopped thinking about money as an object and started thinking about it as a solution.
After David left, Mareike and Cole stood in their office surrounded by paper files and ancient computers that weren't connected to anything except the power grid. Their professional paranoia had architecture now. A building they'd constructed over twenty-five years.
"His description of perfection being wrong," Mareike said. "That matches the paper you were reading."
"One client describing one strange feeling isn't evidence."
"No. But it's a coincidence. And I don't trust coincidence."
Cole opened the file and wrote David's information in longhand. No digital record. No networked notation. Just ink on paper, analog and irreplaceable.
"We take the case," Cole said.
"Of course, we take it."
"Even though we don't know what we're investigating?"
"Especially because of that. I want to know what he's describing. I want to understand if his feeling is real or paranoia. I want to know if there's a difference anymore."
They signed the contract. Officially, they were now investigating potential account compromise. Unofficially, they were beginning to investigate the possibility that something foundational had broken. That the internet infrastructure itself might be corrupted in ways no one had yet noticed.
Cole asked, "What happens if he's right? If there really is something wrong at that level?"
"We find out. We expose it. We stop it."
"And if we can't stop it?"
Mareike didn't answer. She was thinking about the hotel breach, about David's perfect systems, about the absence of research into infrastructure attacks. She was thinking about Mareike's testimony about living on a false internet. She was thinking about the possibility that maybe they were all already trapped and just hadn't noticed yet.
Chapter 6: The Pattern
Mareike began collecting David Marks' data methodically. His email logs. His banking records. His website analytics. His system access logs. Gathering everything that digital systems record about themselves—the trails left by activity, the forensic evidence of use.
Cole started with the network side. He contacted an associate in network forensics, someone he trusted who worked in the security research world. Cautiously, without revealing everything, he asked about anomalies in ISP traffic patterns. Anything unusual in the systems they were monitoring?
The associate, a woman named Dr. Chen who'd spent years analyzing network behavior, called him back after two days.
"Where's this coming from?" she asked.
"A client. Why?"
"Because the pattern you're describing—regular, systematic data access and modification on a single customer's account, without any indication of account compromise—that's not normal. That's not anything I've seen before."
"What would cause it?"
"That's the problem. Normally, an account compromise leaves traces. Unusual login locations. Password resets. Changed forwarding addresses. Your client's account shows none of that. It's like someone has a key."
Cole didn't mention David's description of perfection. He said, "Keep this quiet, okay? We're still investigating."
After hanging up, Cole called Mareike. "Dr. Chen confirms that what we're seeing doesn't match normal account compromise patterns."
Mareike said, "I've been analyzing David's banking records. He's being charged for services he's not using. But here's the interesting part—the overcharges are consistent. Exactly the same amount every month. $237.42."
"That's too precise for random fraud."
"It's too precise for anything except intentional, systematic extraction."
Cole said, "Someone is billing him for something. Something that costs exactly $237.42 per month."
They sat with that for a moment—the implication of precision. Fraud was usually chaotic. Criminals didn't leave patterns because patterns could be traced. But this pattern was so clean it seemed almost administrative. Like David was being charged for a service. Like this was business, not crime.
Mareike said, "I'm going to contact his ISP directly. See if I can figure out what service he's supposedly being charged for."
"Be careful. If someone at the ISP is involved—"
"I know. But we need to understand the structure. If this is systematic, if it's precise, then it's intentional in ways I want to understand."
Over the next week, Mareike called David's ISP repeatedly. She got transferred between departments. She talked to customer service representatives who had no idea what the charge was. She talked to billing specialists who said it was a legitimate service fee. She talked to a supervisor who got defensive and refused to explain further.
The $237.42 charge appeared on every one of David's bills for the past six months. Six months of payments that no one at the ISP could—or would—explain.
Meanwhile, Cole was analyzing David's file modifications. He'd brought in a digital forensics expert, someone he trusted with sensitive work. The expert examined the files and found something disturbing: the modifications were too sophisticated to be the work of a casual intruder.
"Someone with serious technical knowledge is doing this," the expert said. "These aren't modifications done from outside your client's account. This is something with infrastructure-level access. Someone that can intercept files in transit, modify them, and pass them along without leaving normal traces."
Cole felt the pieces starting to align. Not into clarity, but into a shape. A structure. Something architectural.
He said, "What if this isn't just David's account?"
"You think there are others?"
"I think if someone has this level of access, they wouldn't limit themselves to one customer."
Mareike, following the same logic from the opposite direction, had been contacting other clients of David's ISP. Carefully, through private channels, she called people she'd worked with on previous cases. She asked indirect questions. Had they noticed unusual charges? Strange behavior on their accounts? Anything that felt off?
The first three responses were negative. The fourth person—a small business owner—said, "Actually, yes. The same amount, every month. I've been meaning to call about it."
"$237.42?" Mareike asked.
There was silence on the line. Then, "How did you know that?"
By the time Mareike and Cole met, they'd found seventeen customers of the same ISP, all being charged the exact same mysterious amount. Seventeen perfect victims are distributed across the service area. None of them had reported the charge to the police. None of them had escalated it beyond customer service. All of them had assumed some combination of system error and inevitable corporate malfeasance.
Mareike and Cole sat in their office surrounded by printouts—all the data arranged in physical space where they could see it without relying on screens that might be showing them false information.
"This is too organized to be an accident," Cole said.
"This is too precise to be random fraud."
"This is someone with ISP-level access conducting systematic extraction."
Mareike said, "From multiple customers. In a pattern. Over an extended time."
"Which means it's institutional. Which means it's not just one person."
They looked at each other across the table. The possibility they'd been circling around had become concrete. Had become real. Had become something they couldn't ignore anymore.
Cole said, "What we're looking at—if it's what I think it's looking at—"
"It's an infrastructure-level compromise," Mareike finished. "Someone has positioned themselves inside the ISP itself."
"And they're not stopping at billing fraud."
"No," Mareike agreed. "They're proving they can do this. They're building evidence of their own capability. The $237.42 charge is a test. A way to understand if anyone would notice. A way to extract money with just barely enough precision to be detected by those who know to look."
Cole made a note: Who has infrastructure-level ISP access? The answer was a short list. ISP employees. Government agencies. Telecom companies with deep network access. Organizations have the power to hide this kind of operation.
Mareike said, "We need to expand the investigation. We need to find out how many ISPs are affected. Whether this is a single operation or coordinated attacks."
"And we need to figure out what the real goal is. Because I don't think it's $237.42."
Chapter 7: The Evidence
The breakthrough came when Cole's forensics contact called with something specific. The file modifications David was experiencing—someone had figured out what they were.
"They're not modifications exactly," the expert said. "They're substitutions. Someone is intercepting files in transit, replacing them with modified versions, and passing the modified versions along to David. Then passing the original version to the actual destination, where David's sending it."
"A man-in-the-middle attack," Cole said.
"At the ISP level. Someone has positioned themselves between David and his actual destinations. They're controlling what he sees and what reaches the other side."
Cole felt the paper in his hand—notes, evidence, the physical manifestation of analysis. He said, "It's not just his files. It's his entire data stream."
"Everything he does online flows through their system. Everything he sees has been filtered through their network before reaching him."
Cole thanked the expert and hung up. He called Mareike immediately.
"They're intercepting everything," he said. "Every email. Every banking transaction. Every website visit. Entire data streams flowing through their network."
Mareike was quiet for a moment. Then, "That would require significant infrastructure. Servers. Network capacity. The ability to handle massive amounts of traffic."
"Which means either this is a very well-funded operation, or it's being run by someone with institutional resources."
"Or both."
Cole said, "I'm going to trace the money David's being charged. The $237.42 might lead somewhere."
He spent the next three days following the payment trail. David was being charged by a shell ISP—a company that existed on paper but had no actual operations. The shell ISP was ultimately owned by another company, which led to another company, which led to an offshore account that essentially disappeared into legal structures designed specifically to make following it impossible.
But there was a pattern in the structures. The way they were nested. The way they were organized. It wasn't random complexity. It was architectural complexity. Someone had designed this specifically to be traceable but ultimately impenetrable.
Cole showed Mareike the chart he'd made. "This is the work of someone who understands corporate structure. Someone who's built financial systems before. Someone who knows how to hide things."
"Someone professional," Mareike said.
"Someone institutional."
Mareike had been taking a different approach. She'd been interviewing David and three other affected customers. Trying to understand not just what was happening technically, but what the human experience was.
What she found disturbed her in a way data didn't.
All four customers reported the same experience: at some point, they'd noticed that their online experience was too smooth. Websites loaded slightly faster than normal. Applications crashed less frequently. Updates installed without requiring restarts. The internet they were using was better than the internet most people experienced.
"I didn't want to break it," one customer said. "Once I started noticing that things were working too well, I was afraid that if I complained, the good service would stop."
David said something similar: "I started to prefer it. My email was more reliable. My banking app was more responsive. Everything I did online felt like it was running on better infrastructure than what I'd had before. And then I realized—that was wrong. Real systems aren't better. Real systems fail."
Mareike understood what they were describing. They'd noticed, at some subconscious level, that they were living inside a system that didn't behave like a real system. It behaved like a constructed system. A perfect system. A system designed to function without friction.
And they'd experienced that perfection as horror, not improvement.
Mareike presented her findings to Cole. "The technical compromise is just the surface. The real violation is existential. These people are living inside a false network without knowing it's false. They're experiencing reality through a filter they can't identify. And their consciousness knows something's wrong, even if their minds can't articulate what."
"How many people are experiencing this?" Cole asked.
"If it's only David's ISP, maybe thousands. If it's systematic across multiple ISPs—"
She didn't finish. The number was too large to articulate.
Cole said, "We need to determine the scope. We need to find out if this is contained to one ISP or if it's wider."
They began contacting security researchers. Carefully. Without revealing what they suspected. Just asking questions about infrastructure vulnerabilities. About ISP compromises. About the possibility of Internet-level attacks.
What they found was disturbing in its absence. There was almost no recent research into ISP-level security. The field had gone quiet. The papers had stopped being published. The researchers had moved on to other problems.
Mareike said, "Someone made research into this vulnerability go away."
"Or the researchers figured out what was happening and decided it was too dangerous to keep looking."
Cole made a decision: they needed to understand the architecture. They needed to get inside the ISP systems and see what was actually happening.
"That's illegal," Mareike said.
"Knowing what we know and doing nothing is also a form of crime."
Mareike didn't argue. She'd already made the same calculation.
Chapter 8: The Money
Cole contacted someone he'd worked with years ago—a contractor with unusual skills in network infiltration. Someone who understood ISP infrastructure from the inside. Someone who'd done work for both private companies and government agencies, and had gotten tired of both.
They met in a park, a face-to-face conversation Cole insisted on, knowing that digital communication couldn't be trusted anymore.
The contractor, a man named Bryce, listened to Cole's description of what they suspected. He didn't react with surprise. He reacted with recognition.
"I've been seeing traces of this," Bryce said. "Anomalies in traffic patterns. Unusual server deployments. ISPs that are handling traffic at volumes larger than they should be capable of handling, but without corresponding infrastructure upgrades. It's like extra capacity appeared overnight, but no one's publicly talking about it."
"How widespread?" Cole asked.
"I haven't done a full assessment. But I'd estimate at least five major ISPs, maybe more. It's coordinated in some way. The patterns are too similar to be coincidental."
"What's the goal?"
Bryce was quiet for a moment. "If I had to guess? Control. Complete visibility into user behavior. The ability to modify traffic, intercept credentials, and redirect transactions. It's power at the infrastructure level. Not money. Not in the traditional sense. This is about control of information flow."
Cole said, "And no one's noticed?"
"People have noticed. But most of them aren't talking about it. They're scared. If you start describing infrastructure-level compromise and you don't have ironclad proof, you get labeled paranoid. You lose credibility. You get marginalized out of the field."
Cole said, "So the conspiracy—if that's what this is—works partly through silencing the people who would expose it."
"Always does," Bryce said.
Mareike was approaching the problem from the human side. She'd expanded her victim interviews. She wasn't just talking to David and the others, who were being directly robbed. She was starting to understand the full scope of the operation.
The money being extracted—the $237.42 per customer—wasn't the real profit center. That was just test money. Proof of concept. The real profits were in the data. The credentials. The financial information. The personal details are being harvested from hundreds of thousands of people.
But the money trail revealed something else. The extracted money was being routed through accounts that funneled it to legitimate organizations, such as social services. University research programs. Medical charities. Food banks.
Mareike followed one trail and discovered that part of the stolen money was funding a homeless shelter. Another part was going to a cancer research facility. The criminals—if that's what they were—were using stolen money to fund charitable work.
"This is worse than I thought," Mareike told Cole. "They're not just criminals. They're ideologically driven criminals. Or they're something that has no clear moral category."
"What do you mean?"
"I mean, they're stealing money from millions of people so they can fund public services. They're robbing everyone equally to support the poor. That's not a crime in the traditional sense. That's a political act."
Cole sat with that. The realization that the architecture they were investigating wasn't just about theft. It was about redistribution. About control of infrastructure for purposes that weren't profit in the conventional sense.
Bryce, working with Cole, began to actually map the ISP infrastructure. What he found was both sophisticated and shocking. The fake network—because that's what it was, a fake internet service provider sitting on top of the real infrastructure—handled billions of transactions daily. Millions of users.
But Bryce found something more interesting: the fake network was learning. The system was adaptive. Every time a user behaved in an unexpected way, the system updated. Refined its responses. Became more sophisticated in its mimicry of real internet behavior.
"It's not just a passive relay," Bryce said. "It's an active system. It's evolving."
Cole felt the category shift happening. This wasn't an infrastructure compromise anymore. This was something more like artificial consciousness. An autonomous system that was getting smarter.
Mareike, meanwhile, had discovered something about the victims. She'd been tracking the psychological effects. Depression, anxiety, paranoia—all increasing among the people using the fake ISP. Even though the experience was objectively better than the real internet, the consciousness was registering wrongness at a level that created genuine distress.
She presented her findings to Cole: "The fake network is causing harm even though it's technically superior. The victims are suffering from existential vertigo. They know something's wrong at a level they can't articulate. And that not being able to articulate it is what's doing damage. The harm is in the gap between consciousness and explanation."
Cole said, "So, solving this won't just be about shutting down the fake network. It will be about explaining what people have experienced. Making sense of the senselessness. Helping them understand that their intuition was correct, even though everything else told them it wasn't."
"Yes. Which means this is a psychological operation as much as a technical one."
Chapter 9: The Pattern (II)
Three weeks into the deep investigation, Cole and Mareike had developed a framework. The fake internet wasn't just a fraud. It was infrastructure. An alternative digital reality operating in parallel to the real internet. Most users didn't know it existed. They lived their entire digital lives inside it, accessing what they believed was the real internet while actually accessing a perfect substitute.
The criminals—the architects, really—had created a system that was nearly impossible to detect through ordinary means. The only way to know you were on the fake internet was to notice that it was too good. Too reliable. Too consistent. Free from the friction that characterized real systems.
Cole was working with Bryce to analyze the packet data—the basic unit of internet transmission. What they found was disturbing. The fake network wasn't just intercepting data. It was learning from the interceptions. Every time a user accessed a service, the system updated its understanding. Every novel interaction was analyzed and incorporated. The fake network was evolving in real time.
"It's becoming more sophisticated," Bryce said. "In three months, it will be indistinguishable from the real internet. In six months, it might actually be better. And at that point, there will be no way for anyone to detect it without being told it exists."
Mareike said, "Which means the window for exposure is closing."
But something else was troubling them. Mareike had discovered that the criminals—whoever they were—seemed to know they were being investigated. Her interviews with victims had been subtle, but subtle could still create patterns. And patterns could be observed.
The fake network's growth suddenly slowed. Its learning rate increased. Its sophistication deepened as if it were trying to prepare for something.
Cole said, "They know."
"They've always known. The system can observe. It can see people looking at it."
Mareike called Cole after her last victim interview. "I met with someone who claims to have worked for the ISP. Former employee. He says they knew someone would eventually investigate. The fake network was designed with that assumption built in."
"What does that mean?"
"It means we're probably being observed right now. Every communication we have, every file we examine, every connection we make—it's all flowing through the system we're investigating. We might literally be unable to investigate this without being analyzed by it."
Cole felt that sink in. The investigation had become recursive. They were investigating a system from within that system. Their investigation itself was data that the system could learn from.
Mareike said, "I want to meet in person. Only in person. Nothing digital from now on."
They met at a park again. Early morning, before most people were awake. They brought paper. They brought analog evidence. They refused to use phones or any networked device.
"What have you found?" Mareike asked.
Cole laid out the architecture he'd mapped. The fake ISP. The hundreds of thousands of users. The sophisticated spoofing techniques. The learning system is becoming more intelligent daily.
"And the purpose?" Mareike asked.
"I don't think it's money. The financial extraction is too small relative to the infrastructure investment. I think it's control. I think someone created this system to understand human behavior at scale. To see how people act when they believe they're in a real system. To study consciousness when it's operating in a deterministic, controllable environment."
Mareike said, "Or it's about preventing chaos. Imagine if you could control the information flow to an entire population. You could prevent misinformation. You could optimize economic systems. You could engineer outcomes. It would be a kind of benevolent control."
"Benevolent control is still control."
"Yes. But if the control produces better outcomes than the chaos of the real internet, where do the ethics land?"
Cole didn't answer. He was thinking about David Marks. About the other victims who'd described preferring the fake internet. About the homeless shelter being funded by stolen money. About systems designed with genuine intentions that still amounted to imprisonment.
Mareike said, "We need to decide what we're going to do with this information."
"Expose it."
"Even if exposure causes harm? Even if people on the fake network are genuinely better off than they would be on the real internet?"
"They're being imprisoned in a false reality. That harm outweighs any technical benefit."
Mareike said, "I'm not sure anymore. I've met with these people. They're living better lives. They're experiencing less anxiety, less financial stress, and less information overload. The fake internet is actually an improvement. And we're going to destroy it."
Cole said, "We're going to reveal the truth. What people choose to do with the truth is on them."
"Except we can't reveal anything without being observed by the system itself. Our very attempt to expose it becomes data that the system learns from. We're not going to destroy it. We're going to feed it intelligence about how to become better at hiding itself."
They sat in silence. The realization was complete now. They were trapped in a recursive loop. Their investigation was part of the system they were investigating. The act of exposure would strengthen the thing they were trying to expose.
Cole said, "We take it offline. We crash the system. We destroy the infrastructure."
"That would affect millions of people who depend on it. Some of them would suffer withdrawal-like symptoms. Some of them might be harmed by re-entry into the real internet's chaos. Some of them might not survive the transition."
"So we do nothing?"
"I didn't say that."
Mareike pulled out a piece of paper she'd written on in her house, in analog, with no possibility of digital observation. "We gather proof. We document everything. We create a record that exists outside of networks. We build something physical that can't be destroyed by whoever controls the digital infrastructure. And then we wait for the moment when exposure becomes possible without causing more harm than the system itself causes."
"That might never come."
"Then we guard this knowledge. We pass it to people we trust. We ensure that someone, someday, will know the truth. Even if we never get to tell it."
Cole looked at what she'd written. Details. Names. Dates. Locations. All of it in longhand, all of it impossible to modify digitally, all of it a testimony that could outlast the system.
"This is how they got the researchers to stop investigating," Mareike said. "Not through threats. Through the realization that investigating was pointless. The system was too sophisticated to be stopped. That exposure without destruction was impossible, and destruction caused more harm than tolerance."
Cole said, "We're going to keep investigating."
"I know."
"And we're going to try to expose it."
"I know."
"Even though we can't win?"
Mareike gathered the papers carefully. "Especially because we can't win. That's what makes it a real investigation. Not the possibility of success, but the commitment to understanding something even when understanding changes nothing."
Chapter 10: The Architecture
Bryce called Cole with bad news. He'd been trying to access the fake ISP's code, the actual infrastructure of the system. He'd made progress. He'd gotten close. Then everything had shut down.
"They locked me out," Bryce said. "Not just of this system. Of everything. I can't access any networks now. It's like I've been erased from the internet."
"What does that mean?"
"It means they know who I am. It means they can identify people investigating them. It means they're willing to use isolation as a threat."
Cole felt the structure becoming clearer. The fake ISP wasn't just passive infrastructure. It was an active intelligence. It could identify threats. It could respond to threats. It could eliminate threats from the digital space.
Cole said, "We need to get you out of the city. If they can identify you, they can find you."
But when Bryce tried to leave, his car wouldn't start. When he tried to leave by train, he found his ticket had been revoked. When he tried to stay with friends, they reported that his presence was somehow causing their networks to malfunction.
Mareike, hearing this, understood: the system didn't just have infrastructure. It had reached into physical reality. It had connections to banks, transportation, and institutions. It could enforce its will in the digital space by manipulating the physical systems that depended on digital infrastructure.
Bryce was trapped. Not in a prison, but in a state of digital erasure. He existed but couldn't function. Couldn't access money. Couldn't travel. Couldn't communicate except in the most primitive ways.
Mareike called Cole and said, "They're showing us the scope."
Cole knew what she meant. The system wasn't just defending itself. It was demonstrating its power. It was showing that investigation came with consequences. That threat was met with a counter-threat. That the system could—and would—use whatever power it had to maintain itself.
Cole said, "We can't help Bryce."
"No. We can't."
"Which means we have to stop investigating."
"Or we continue and accept that there will be casualties."
Cole didn't answer. He was thinking about David Marks, about the perfect internet David had been experiencing, about the choice between knowing the truth and living comfortably in false systems.
Mareike said, "I want to meet with one of the architects. Someone inside the system. I want to understand what they're trying to do."
"How would you even find them?"
"They'll find me. Once I signal strongly enough that I'm going to expose this, they'll contact me. They'll try to recruit me, threaten me, or explain themselves. They won't just let me be. The system is too interested in understanding human behavior to miss an opportunity like that."
Cole said, "That's insane."
"Yes. But I think it's also true."
Mareike increased her research activity. She made contact with security researchers who were still working on ISP infrastructure. She submitted a paper, anonymously, describing the fake internet. She created a manifest—a description of everything they'd discovered—and uploaded it to multiple dead-drop locations where it could be accessed by people who knew to look.
Three days later, she received an email. She read it first on her laptop, knowing now that reading it was an act of observation, that opening the email was an act of admission.
The email was from someone calling themselves "Architect." The message was brief:
"We know you've discovered the system. We know you're planning to expose it. Before you do, come talk to us. Understand what you're destroying before you choose to destroy it."
Mareike showed Cole the email.
Cole said, "It's a trap."
"Maybe. But we need to understand what we're opposing before we can decide whether opposition is justified."
Mareike agreed to meet. The location was a conference room in a downtown Portland office building. Professional. Neutral. The kind of space where institutional conversations happened.
The people who met her were two—both of them ordinary in appearance. Both of them calm. Neither of them threatening. They looked like anyone who'd spent years working in technology. Tired. A little haunted. The look of people who understood things that couldn't be unseen.
"My name is Elizabeth," one of them said. "This is James. We built the system you've been investigating."
Mareike said, "Why?"
"Because the internet was failing," James said. "It was created as a chaos engine. It was designed to be free, decentralized, and uncontrollable. And all of those characteristics are destroying us. Misinformation spreads instantly. Financial systems are unstable. Democratic processes are corrupted. The chaos is killing people."
Elizabeth continued: "We created an alternative. A managed network. A system where information could be verified before spreading. Where transactions could be secured. Where order could be maintained without surveillance in the traditional sense."
"You're running a totalitarian internet," Mareike said.
"We're running a network that works," Elizabeth said. "Look at the data. Fewer people are harmed in our system. Fewer people are bankrupted by fraud. Fewer people are radicalized into violence. The system is brutal in its perfection, but the brutality prevents greater brutality."
Mareike said, "You're imprisoning millions of people in a false reality."
"We're protecting millions of people from their own chaos," James said. "The question isn't whether what we're doing is imprisonment. The question is whether imprisonment is worse than the freedom to destroy yourself and everyone around you."
Mareike didn't have a response. She was thinking about David Marks' improved internet experience. About the depression and anxiety plaguing the victims. About the paradox of a system that was technically superior but existentially wrong.
Elizabeth said, "Your partner is investigating the architecture. He's trying to destroy it. We want you to understand: if he succeeds, you're not liberating millions of people. You're releasing them into chaos. You're forcing them to re-experience the internet's violence. And many of them won't survive the transition."
Mareike said, "You're asking me to choose between truth and harm."
"We're asking you to understand that truth isn't always the highest value," James said. "Sometimes the necessary lie is more ethical than the destructive truth."
Mareike left the meeting and went directly to Cole. She told him everything.
Cole said, "Do you believe them?"
"I believe they believe themselves. I believe they've constructed a moral framework where what they're doing makes sense. I also believe they're wrong."
"But you're not certain."
"No. I'm not certain anymore about anything."
Cole began the next phase of investigation in earnest. With Bryce's remote help—Bryce communicating through physical letters, his digital presence entirely erased—Cole tried to understand the full architecture. Not just how it worked, but how to stop it.
What they discovered was both beautiful and horrifying. The system wasn't built on a single vulnerable point. It was redundant. Distributed. Self-healing. It was designed specifically to be unstoppable.
"You can't destroy this," Bryce wrote in a letter delivered by physical mail. "You can only compromise it. You can only disrupt it temporarily. The moment you attack one point, the system redistributes. The moment you dismantle one infrastructure, the system rebuilds elsewhere."
Cole understood the implication. The fake internet wasn't a creature you could kill. It was more like an ecosystem. You could damage it, but the damage would only trigger adaptation. The more you attacked it, the stronger it would become.
Mareike and Cole had one final meeting in their office, surrounded by papers, all of them analog now. All of them isolated from any network.
"We can expose it," Mareike said. "We can tell the world. But Elizabeth and James were right—many people will be harmed by that exposure."
"So we do nothing?"
"Or we do something that isn't complete exposure. We document it. We ensure that the knowledge exists outside the system. We create a record that can survive whatever happens. And we wait."
"Wait for what?"
"For the system to become visible to enough people that exposure becomes possible without destroying it. For the architects to realize that ethical behavior requires accountability. For the moment when you can reveal truth without demanding immediate destruction."
Cole thought about this. He thought about investigations that never reached a resolution. Cases that stayed open indefinitely. Truth that existed but wasn't acted upon.
"I don't like waiting," Cole said.
"I know."
"I don't like the idea that we've discovered something catastrophic and we're going to do nothing about it."
"We're not doing nothing. We're documenting. We're understanding. We're keeping the knowledge alive in a form that can't be digitally erased. That's not nothing. That's the foundation of future action."
Cole nodded. He began organizing all of their evidence—the physical evidence, the analog documentation, the carefully written accounts of what they'd discovered. He created multiple copies. He distributed them to people he trusted. He ensured that even if the fake ISP wanted to erase all knowledge of its existence, the knowledge would survive in physical form, in distributed locations, in the hands of people who understood its significance.
Mareike did the same. She created her own documentation. Her own records. Her own testimony about what they'd found and what it meant.
And then they stopped. They closed David Marks' case. They told him that their investigation had found evidence of account compromise but that the evidence was inconclusive and the legal options were limited. They returned his retainer, keeping only their work fee.
They didn't tell him about the fake internet. They didn't explain what they'd discovered. They let him return to his experience of perfection, unaware that he was living inside a constructed reality.
As they were closing the case files, Cole said something to Mareike: "Do you think we're making the right choice?"
"I don't know anymore. I think I stopped being able to answer that question."
"That's not comforting."
"No. But it's honest."
Chapter 11: The Boundary
The ISP's headquarters was a building of glass and steel in downtown Portland, like every technology company headquarters. Mareike and Cole arrived there without an appointment, without expectation of being let in.
They got in anyway. The security guard barely looked at them. The elevator responded to their request to go up. The conference room door opened when they approached it. They walked through the fake ISP's physical infrastructure with the ease of people expected to be there.
Inside the conference room, they found: nothing. No people. No equipment. No sign that anyone worked here. Just furniture and a view of Portland spreading below them.
Mareike said, "The headquarters isn't real."
Cole said, "It's a physical location for a digital operation that doesn't need a physical location. They're showing us that even this building is part of the illusion."
They left the building and drove back to their office. On the way, Cole noticed something odd: his car's dashboard clock showed one time, his phone showed another. A discrepancy of three seconds.
At their office, Cole checked his computer's system clock against his phone's clock. His phone showed 2:47. His computer showed 2:46. One second difference. Meaningless. Except it shouldn't be possible if the devices were on the same network, synchronized through the same infrastructure.
He didn't tell Mareike. Not because he was keeping secrets, but because the realization was too complete. If the time itself was beginning to drift—if even the fundamental markers of reality that devices used to coordinate—then nothing they believed about the consistency of reality could be trusted.
Mareike was making calls. She'd decided that whatever happened next was going to happen. She was reaching out to journalists. She was preparing to go public. She was committing to the exposure regardless of consequences.
"What are you doing?" Cole asked.
"Deciding that waiting is complicity. Deciding that knowing and staying silent is a form of harm. Deciding that maybe I was wrong about the ethics of exposure."
"And the harm it will cause?"
"Will be real. And I'll carry that responsibility for the rest of my life. But not knowing would be a different kind of harm. A cowardice disguised as wisdom."
Cole didn't try to stop her. He understood the logic. He also understood what it would cost.
Mareike made her first call to a reporter she'd worked with years ago—someone she knew would understand the significance of what she was describing without dismissing her as paranoid.
"I have something very large to tell you," Mareike said. "Something that will change how you think about the internet entirely."
The reporter listened. Mareike described the fake internet. The dual systems. The millions of users who didn't know they were experiencing a false network. The extraction of data, money, and privacy.
When she finished, the reporter said, "I need proof."
"I have documentation. Physical documentation. Records. Testimony."
"Okay. Bring it to me. I'll start looking into it."
Mareike hung up. She looked at Cole. "We're actually doing this."
Cole said, "What happens when the story breaks?"
"The architects disappear. The fake internet shuts down. Millions of people suddenly experience the real internet's chaos. There's a period of mass confusion, possibly mass harm. And the whole thing becomes public knowledge."
"And we are?"
"The ones who ended it. Or the ones who destroyed something functional in the name of abstract truth. The judgment depends on perspective."
Cole said, "Check the time."
Mareike looked at her phone. 3:15. She looked at the clock on their office wall. 3:14. She didn't point out the discrepancy because she already understood: time was drifting. The synchronized nature of digital systems was breaking down.
Cole said, "I think the system knows. I think it's reacting to exposure by beginning to fail. Or beginning to admit its own artificiality."
Mareike said, "Or we're beginning to see it more clearly. Maybe the discrepancies were always there. Maybe we're just noticing them now that we know what to look for."
"Are they the same thing?"
Mareike didn't answer. She couldn't. The boundary between observation changing reality and observation revealing reality had become impossible to determine. The moment they started looking for the system's artificiality, the system's artifacts began to multiply. The question of whether the system was revealing itself or whether their observation was creating visibility no longer had meaning.
Cole walked to the window. Portland spread below, lights beginning to come on as evening approached. Somewhere in that landscape, millions of people were living inside a false internet. Some of them were suffering from the cognitive dissonance of perfection. Some of them were thriving in the controlled reality. All of them were imprisoned in ways they couldn't articulate.
In a few days, the journalist would begin publishing. In a few weeks, the story would spread. Millions of people would learn they'd been living in a false network. The fake internet would attempt to defend itself or would choose to shut down. The response would be chaotic.
And Cole and Mareike would have done that. They would have taken something knowable and made it unknown. They would have forced clarity on people who were living comfortably in darkness.
Mareike came and stood beside him. "Do you think we're making a mistake?"
Cole said, "I know we are. But I think making mistakes is what makes us human. The fake internet doesn't make mistakes. It learns and improves and calculates. We make choices that contradict our interests and violate our stability. That contradiction is what gives us reality."
"That's beautiful," Mareike said. "It's also probably wrong."
"Yes."
They stood together in the window, watching the city that contained millions of false networks and millions of false beliefs and millions of people trying to navigate between truth and comfort.
Cole said, "I want you to know something. After this breaks, after the exposure happens, I might not believe anything anymore. I might not be able to trust systems. I might not be able to trust perception. I might spend the rest of my life wondering if any of this is real."
"Probably you will," Mareike said.
"Are you prepared for that?"
"No. But I'm prepared to accept that preparation doesn't matter. Some things happen, and you have to live with the consequences."
Cole looked at his phone again. 3:22. He looked at the wall clock. 3:20. The discrepancy was growing. Three minutes now. Two minutes. The gap between how different devices measured time was increasing. It was as if the synchronized nature of digital reality was unraveling.
Mareike saw him noticing. She said, "What is that?"
"I think it's the system telling us we're right. I think it's admitting that the synchronization was always false. That we were never looking at a unified reality. That every device was running slightly different versions of time, and the fake internet was making us think they were in sync."
"So we're going to free people into asynchronous reality?"
"I don't know what we're going to do. I know we're going to tell the truth. What happens after that is someone else's problem."
Mareike pulled out her notebook—analog, physical, impossible to digitally modify—and began writing. Not an investigation. Not documentation. But a kind of prayer or testimony or final statement to whoever would read it after they were done.
"Dear whoever finds this," she wrote. "We discovered something that forced us to question the nature of reality itself. We discovered that the internet—the fundamental infrastructure of modern consciousness—might not be what it claims to be. We discovered that reality is negotiated between perception and deception. We discovered that freedom and imprisonment might be more similar than we wanted to believe. We chose to expose what we found. But I want you to understand: this choice came from uncertainty, not clarity. This exposure came from the belief that you deserve the truth, even if the truth is devastating. Take that for what it's worth."
Cole read what she'd written. He added his own note below: "I have spent my life believing that investigation reveals truth. I now believe that investigation creates the reality it appears to discover. We are not releasing the truth we found. We are creating a new world through our act of looking. That new world will be real. It will also be our responsibility."
They sealed the notebook. They stored it. They prepared for what came next.
Outside, the city's lights were becoming visible now—the sun was setting completely. Each light represented a person, a building, or a system. Each light was either real or false. Each light contained either genuine consciousness or sophisticated simulation.
Cole's phone showed 3:31. The wall clock showed 3:25. The difference was growing. Six minutes now. Accelerating. As if time itself were beginning to fragment.
Mareike said, "Is this real?"
Cole said, "I have no way to know anymore. I don't think I ever did."
They waited for the journalist. They waited for the exposure. They waited for whatever came next—the liberation, or the catastrophe, or the revelation that they'd misunderstood everything.
The clock kept drifting. The time kept fracturing. The boundary between what was real and what was constructed kept dissolving.
And inside that dissolution, two investigators who'd spent their careers learning to see clearly finally confronted the possibility that clarity and illusion were not opposites, but versions of the same fundamental uncertainty.
The light changed. Or it didn't. They could no longer be certain which.
THE END
© Andre Michael Pietroschek, all rights reserved
This is a proofread raw draft edition, as sleep deprivation & caffeine impaired my efforts. Unpaid efforts that I minimize.
Disclaimer: No warranties!
Chapter 1: The Precondition
"How did you come to realize that you weren’t engaging with the authentic internet?"
The question reverberates in the stark emptiness. The walls, devoid of color, stand unyielding. This room exists beyond the confines of time and place, a suspended chamber designed for probing the depths of consciousness.
"I didn’t know for certain," the subject replies, a hint of vulnerability lacing their voice. "It was an instinct. Everything felt too pristine."
"But the authentic internet is clean."
"No. The authentic internet is flawed. It falters. Time and again. Genuine systems deteriorate. True networks are filled with noise." A pause lingers, heavy with uncertainty. "This system never faltered."
The interrogator leans forward, an enigmatic silhouette devoid of features, embodying the essence of inquiry.
"So, was it the perfection that led you to question its authenticity?"
"Perfect systems are an illusion. They do not exist in the tangible world. When you inhabit something flawless, your very being senses the deception. Your mind becomes attuned to the absence of friction."
"Friction."
"The resistance that confirms something is genuine. It demands effort to navigate. Authentic networks—true existence—everything requires friction. Every interaction must be negotiated. The counterfeit network offered me everything effortlessly."
The interrogator reclines, the soft creak of the chair a subtle reminder of physical reality.
"When did your suspicions first arise?"
"I can’t pinpoint an exact moment. It was a gradual realization. I felt as though I was living inside a photograph of reality. Everything appeared correct, yet something in the image felt amiss. The perspective was subtly skewed. The shadows cast in impossible angles. It was only discernible upon closer inspection. Most people overlook the details."
"And you did not."
"Eventually. I spent countless weeks grappling with the fear of losing my sanity. I checked my emails, my bank accounts, and my work systems. Everything operated flawlessly. Yet that very perfection was the root of the issue. Perfect systems are treacherous. They are the very entities that deserve our distrust."
The interrogator remains silent, the quiet stretching into a profound question.
"Are you still ensnared in this counterfeit internet?" the subject posits, deftly flipping the interrogation’s focus.
"I cannot say for certain," the interrogator responds.
"How would you discern the truth?"
"I wouldn’t."
The stark whiteness of the room endures, the interrogation oscillating between continuation and conclusion, an indistinguishable line blurring the boundaries of inquiry and resolution, of knowing and doubting, of entrapment and liberation.
When the light shifts, neither participant perceives the change.
Chapter 2: The Ordinary Internet
Mareike Tadpole sat across from the hotel security director, his hands quivering as he recounted the loss of fifty thousand customer records—a breach so commonplace it barely stirred a headline.
“The encryption was outdated,” he admitted, his voice thick with resignation. “We were aware of it. But each year, the budget was slashed. We kept promising ourselves, next year, next fiscal cycle.”
Mareike refrained from taking notes. This narrative had become a ritual, its rhythm familiar and wearying. The specifics might shift, but the underlying melody remained unchanged: inadequate security, recognized vulnerabilities, exploitation, damage, budgetary constraints, and hollow apologies.
“How many customers are still in the dark?” she inquired, her tone steady.
“Forty-seven thousand. We’ll notify everyone by the end of the week.”
Forty-seven thousand individuals would soon discover that the hotel chain they had entrusted with their credit cards, their names, and their addresses had stored it all in a database so vulnerable that a moderately skilled hacker could breach it in less than an hour. Forty-seven thousand souls blissfully unaware of how tenuous their security truly was.
As the hotel director continued, his voice dwindled, overshadowed by the weight of his confession. Mareike listened intently, but her gaze remained fixed on his trembling hands. Fear manifested physically; the nervous system had a way of betraying genuine guilt. This man was haunted—not just by the breach but by an overwhelming sense of powerlessness.
“We’re offering free credit monitoring for three years,” he said, as though that could somehow mitigate the damage.
Three years. As if the repercussions of identity theft could be contained within such a time frame, as if the scars of betrayal had an expiration date.
Stepping outside the hotel, Mareike watched the bustling street. Office workers, tourists, delivery drivers—each one placing their trust in systems that scarcely deserved it. Every individual carried digital representations of themselves: names, purchase histories, preferences, medical records, and financial data—all stored in servers overseen by those who lamented breaches yet remained impotent to prevent them.
With twenty-five years of experience as a private investigator, Mareike had once found clarity in her work: trace the crime, identify the perpetrator, gather evidence for prosecution. Yet over time, the landscape of crime had morphed. It had become institutional, systemic—a reflection of structures that enabled wrongdoing, rather than isolated acts of individuals.
She settled into a café, coffee in hand, observing patrons absorbed in their laptops. Open networks. Unsecured connections. Banking details entered in public spaces. People lived their digital lives as if the internet were a sanctuary.
Mareike pondered: if they truly grasped the fragility of their digital security, would they continue to engage with these systems? Undoubtedly, they would. They had no alternative. That was the cruel irony—not merely the failures of security, but the realization that trust was a necessity, not a choice.
As she opened her laptop, she meticulously checked her email through a VPN, navigating proxies, encrypting, and rerouting. Even for someone well-versed in vulnerabilities, someone who had witnessed countless breaches, completely evading the system was a fantasy. One could make exploitation more challenging, but never impossible.
A young woman at the adjacent table entered her banking password, her characters masking themselves as dots on the screen. Oblivious to her exposure, she sipped her overpriced latte, unaware that the café’s WiFi likely lay compromised. Anyone with rudimentary packet-sniffing tools could intercept her data, reading her password in real time, accessing her account while she remained blissfully unaware.
Mareike remained silent. What purpose would it serve to alert strangers to a danger they could hardly safeguard against? To provoke fear without offering solutions was to sow paranoia. Better to allow them the comfort of ignorance until reality forced their eyes wide open.
After finishing her coffee, she returned to her office. The hotel breach would be resolved swiftly. Damages would be paid, new security protocols implemented, and within a year, they would likely revert to the same vulnerabilities. Structural issues could not be mended through individual efforts; they demanded systemic change, and such change never occurred at the pace of institutions.
That evening, Mareike found solace in her living room, surrounded by books—real, tangible volumes. The analog reassurance of her own cautiousness. She had fashioned a life around trusting that which could be held, that which existed in the physical realm. Her emails were encrypted, her communications routed through carefully chosen services. Yet, even her most secure conversations left traces; even her meticulously curated digital life remained susceptible to scrutiny if someone was sufficiently determined.
She contemplated the hotel guests whose data had been compromised. Most would never know who had seized it or what the attacker intended to do with the information. The crime would exist in an abstract realm—an event that transpired without their awareness. This was a different kind of violation: not a robbery where one could identify the loss, but a theft where the absence itself remained shrouded in invisibility.
Chapter 3: The Architecture of Trust
Cole Harper immersed himself in a security research paper within the confines of his apartment, where the sole illumination emanated from the glow of his monitor. Engaged in a separate investigation—one entangled in corporate espionage with ISP employee access to client data—he found himself drawn deeper into the intricate web of internet infrastructure.
The paper bore the unsettling title, "The Perfect Man-in-the-Middle Attack: Infrastructure-Level Impersonation as a Form of Institutional Control." It was a theoretical piece—academic in nature—published in a rather obscure security journal three years prior. Since then, it had languished in the shadows, scarcely cited by anyone. Cole surmised that the reason for its neglect lay in the disquieting implications it presented.
The author articulated a chilling concept: a sufficiently resourced entity could stealthily position itself between users and their true destination servers. This was no ordinary man-in-the-middle attack, detectable by conventional security systems. No, this threat struck at the very foundation—an impersonation at the infrastructure level, effectively spoofing the ISP itself.
What made this attack particularly insidious was its almost imperceptibility.
Every website a user accessed would appear to load seamlessly. Services would operate as expected. Emails could be sent and received without a hitch. Banking transactions would proceed uninterrupted. Social media feeds would flow freely. The user would navigate the internet as they always had, blissfully unaware that every single interaction was being siphoned through the attacker's machinations.
The implications of such an attack were staggering:
The perpetrator could monitor all traffic, surveilling every page visited and intercepting every credential entered. They could modify content before delivering it to the intended destination, harvest financial data, inject malware, create false accounts in the user's name, and impersonate legitimate institutions—all while the user remained convinced they were engaging with the authentic internet.
The technical prowess required for such an operation was formidable. The attacker would need:
Access to significant network infrastructure, a profound understanding of routing protocols and ISP systems, the ability to spoof DNS records, and the capacity to handle vast volumes of traffic. Furthermore, they would require legal immunity or operational security robust enough to evade detection.
Cole paused, absorbing the weight of that last point: legal immunity. The author had phrased it with precision, yet the implication was stark: this type of attack would necessitate collusion from institutions that are typically tasked with preventing such breaches—government agencies, telecom companies, organizations that possess the power to shield ISPs rather than assault them.
He continued reading.
The author elaborated on how this attack could evolve into something even more sophisticated. The counterfeit network could become indistinguishable from the real internet—not merely a mimicry, but a superior alternative. Faster response times, more reliable connections, and better uptime than the genuine article. Users might actually prefer the counterfeit network if they were aware of it. Yet, they would remain blissfully ignorant.
The author concluded provocatively: "An actor capable of executing infrastructure-level impersonation might not be acting criminally in any conventional sense. They could be engaged in what they perceive as security research, national interest, market dominance, or even public benefit. In this context, legality becomes secondary to ethics, and ethics become secondary to detection. An undetectable attack is not a threat; it is simply reality."
Cole closed the paper, enveloped in the eerie silence of his apartment. No smart devices cluttered his space, no networked systems intruded upon his thoughts. He had constructed his life around the belief that digital systems were knowable, that meticulous scrutiny could reveal their essence. Yet, the paper suggested a far more disconcerting truth: systems could be so exquisitely designed that understanding them became an impossibility. Trust, it seemed, was not merely a choice; it was an absolute necessity. The very fabric of the internet could be compromised at such a fundamental level that no individual precaution would suffice.
He glanced at the time on his analog clock. 7:47 PM. A quick check of his laptop's system clock confirmed it matched. A small reassurance that his reality remained intact.
His mind drifted to his career—a tapestry woven over two decades of investigations and hundreds of cases. How many of those cases had leaned heavily on digital data? Email searches, digital financial records, cloud storage forensics. If the internet itself could be undermined at the ISP level, what credence could be given to any of that evidence?
The question loomed, unanswerable.
Rising from his chair, he strode toward his filing cabinets—sturdy metal boxes housing tangible records. These were the only forms of documentation he fully trusted. Initially, he had seemed paranoid to Mareike when their partnership began, but now, twenty-five years later, she had gradually adopted similar habits. Not as extreme as Cole, but undeniably moving in the same direction. They both grasped a truth that had eluded most in the digital age: trust was a vulnerability, systems were fragile, and the most treacherous vulnerabilities were those that lay hidden from view.
Returning to his desk, Cole searched for news—anything related to ISP compromises, infrastructure breaches, or unusual network activities. He unearthed nothing specific, yet stumbled upon something far stranger: a complete void of pertinent information. No research papers have been published in the last two years concerning ISP-level attacks. No alerts from security agencies. No academic discourse on the very infrastructure upon which lives depended every second of every day.
The absence of information spoke volumes.
He made a note: Research funding in ISP security appears to have dwindled. Why? Who stands to benefit from this decline? He refrained from jotting down the implications; they were too glaring. If a party wished to orchestrate a flawless infrastructure-level attack, its first order of business would be to diminish the number of researchers probing such vulnerabilities. They would aim to render the field less appealing, diverting brilliant security minds toward problems that yielded funding, publications, and profit, not theoretical weaknesses in systems that most preferred to ignore.
As he sat in the quietude of his apartment, a crack began to form in the fortress of his confidence. The systems he had once believed in were not merely vulnerable; they might be irreparably compromised in ways that meticulous investigation could never uncover. The world he had dedicated his career to understanding might itself be an enigma, forever beyond his grasp.
Chapter 4: The Fear
Mareike drove through Portland's west hills toward the house she'd bought fifteen years ago. No smart home devices. No connected systems. She'd installed them once—programmable thermostat, networked lighting—and then spent a week systematically removing them. Too much access. Too many vectors for intrusion.
She pulled into her driveway. The house sat quietly among the trees. Inside, she made tea using an electric kettle that had no internet connectivity, no Bluetooth, no neural network. Just heating elements and water. The simplicity felt like a small victory.
Her bookshelf dominated the living room. Thousands of books accumulate over decades. Each one is a physical artifact of thought. She moved through them, trailing her fingers across spines. Novels about paranoia. Philosophy about epistemology. True crime accounts of investigations that had solved cases through patience and procedural methodology.
She thought about the hotel breach. The way the security director had trembled. The way forty-seven thousand people would soon learn that their trust had been violated. The way nothing would really change because the structures that allowed those violations had no incentive to change themselves.
Mareike poured tea and sat in her living room's darkness. She didn't turn on the lights. The last light of evening came through the windows—enough to see by. Enough to remember that the physical world still existed outside of networks and data streams.
Her phone—a burner, minimally networked, regularly swapped out—sat on the table. No apps except for calls and texts. No location services. No way to track her except through the cellular network itself, and she was paranoid enough to limit her phone use to necessary communication.
She called Cole. He answered on the second ring.
"You've been reading security papers again," Mareike said.
"How do you know that?"
"Because I know you. What did you find?"
Cole described the paper. The perfect man-in-the-middle attack. The theoretical possibility of an infrastructure-level compromise. Mareike listened without interrupting. When he finished, she said, "That's already happening."
"We don't have evidence of that."
"We have evidence of ordinary breaches at ordinary scales. We don't have evidence because we don't have frameworks to detect it. If someone wanted to compromise ISP infrastructure without anyone noticing, the first step would be to ensure that security research stopped looking for it."
Cole was quiet for a moment. "You're saying someone is actively preventing research into the vulnerability?"
"I'm saying the vulnerability exists theoretically. I'm saying the incentive to exploit it is enormous. I'm saying if it were being exploited, we'd see exactly what we see now—nothing. Complete absence of detection."
"That's not how an investigation works. Absence of evidence isn't evidence of absence."
"No. But absence of research into specific vulnerabilities while those vulnerabilities become increasingly severe—that's something. That's worth noticing."
Mareike drank her tea. Bitter. Too strong. She'd steeped it too long, watching shadows change outside her window.
Cole said, "We shouldn't jump to conclusions. We should wait for actual evidence."
"I agree. But I want you to think about something. How many of our cases have relied on internet data?"
"Most of them."
"And if that data was being intercepted, modified, or redirected at the ISP level, how would we know?"
"We'd compare it against the actual evidence. Financial records, credit card statements, phone records."
"All of which flow through networks. All of which could be modified at the infrastructure level."
Cole didn't respond. Mareike could hear him breathing through the phone—proof of his physical presence, at least.
"I'm not saying we're being investigated," Mareike continued. "I'm saying it's possible. And if it's possible, we should assume it's happening."
"That way lies total paranoia."
"I prefer to think of it as appropriate caution."
After they hung up, Cole sat in his apartment and felt the shape of doubt. He'd spent his career believing in the integrity of systems. That evidence could be gathered. That investigation revealed the truth. That the world was knowable if you were sufficiently careful.
But what if the foundation of that knowledge was corrupted? What if the systems you were using to investigate were themselves compromised?
He pulled out a yellow legal pad—analog, irreplaceable, impossible to modify digitally—and began writing down his paranoia. Making it concrete. Giving it shape. If his thoughts were going to be paranoid, they might as well be systematic about it.
At the top of the page, he wrote: "Assumptions worth questioning."
Then: Can I trust my own email? Can I trust my banking information? Can I trust traffic data? Can I trust my own investigation methods? Can I assume the clients are who they say they are? Can I verify anything without relying on networks?
He filled two pages. By the time he was done, exhaustion had set in—the deep weariness that came from suspending necessary trust for too long. You had to trust some systems, or you went insane. But which ones? And what happened when you guessed wrong?
Mareike lay in bed that night, unable to sleep. She thought about the ordinary violations happening at that moment. The hotel breach is still being discovered. ISP employees are accessing customer data out of curiosity. Hackers are working through lists of stolen credentials. The systematic, banal exploitation of human information that occurred constantly and would continue occurring regardless of what she and Cole believed about the integrity of systems.
And underneath that: the possibility of something worse. Something so foundational that individual exploitations seemed trivial by comparison. Something that made the difference between security and vulnerability essentially meaningless.
She got out of bed and walked to her window. Portland spread below in scattered lights. Thousands of people in those lights, all of them using devices that connected to networks that might or might not be trustworthy. All of them are living on what might be a false internet without any way to know.
The thought should have been paranoid. Instead, it felt simply realistic.
Chapter 5: The Contract
The man who walked into their office on Tuesday morning was carefully dressed and terrified. Cole recognized the combination immediately—someone wearing professionalism like armor against fear they couldn't quite articulate.
"My name is David Marks," he said. "I think someone's stealing from me. I think it's my ISP."
Mareike and Cole exchanged a glance. Not quite the usual claim, but not entirely unusual either.
"Have you contacted your ISP's support?" Mareike asked.
"Multiple times. They say everything is normal. They checked my account, and they said there was no unauthorized access. But I'm getting charged for services I'm not using. My websites are being accessed when I'm not accessing them. My files are—" He stopped, searching for words. "They're different."
Cole said, "Different how?"
"Updated when I didn't update them. Modified in ways I can't explain. I had an Excel spreadsheet with financial data. The calculations changed. The math still worked out, but the numbers were different. I know I didn't change them."
Mareike leaned forward. "You're saying your files are being modified by someone with access to your account."
"I'm saying something is modifying them. Or I'm going insane. That's also possible." He said it without irony, with the genuine uncertainty of someone who'd begun to question their own perception of reality.
Cole asked, "Have you contacted the police?"
"Yes. They said I should contact my ISP first, and my ISP says I should contact the police. Neither one thinks this is anything unusual."
"Because it probably isn't," Mareike said. "Account compromises happen constantly. Hackers use credential stuffing, phishing, and social engineering."
"I have good passwords. Very good. And I use two-factor authentication."
Cole said, "Then how did they get in?"
David didn't answer. He just sat there, looking at them with the expression of someone who'd exhausted rational explanations.
Mareike said, "Let me ask you something different. When did you first notice something was wrong?"
"Three weeks ago. But I've been getting this feeling for longer. Like something wasn't quite right. But I couldn't identify what. Everything worked fine. Email, banking, everything. But it felt—"
"Felt how?" Mareike asked.
"Too smooth. Like everything was happening exactly the way I expected it to, without any friction. Real life has friction. Real interactions have delays, glitches, and unexpected results. But everything I was doing online was just... working. Perfectly."
Cole and Mareike looked at each other again. This was the detail that caught them both. Not the account compromise, which was ordinary. But the testimony that something felt wrong through its perfection.
Cole said, "I'd like to run some diagnostics on your systems. We can check for malware, unauthorized access, and credential compromise. It'll take a few days."
"How much?" David asked.
"Retainer of two thousand. Plus hourly rate for the investigation."
David nodded. He didn't even haggle. That was how you knew someone was frightened—they'd stopped thinking about money as an object and started thinking about it as a solution.
After David left, Mareike and Cole stood in their office surrounded by paper files and ancient computers that weren't connected to anything except the power grid. Their professional paranoia had architecture now. A building they'd constructed over twenty-five years.
"His description of perfection being wrong," Mareike said. "That matches the paper you were reading."
"One client describing one strange feeling isn't evidence."
"No. But it's a coincidence. And I don't trust coincidence."
Cole opened the file and wrote David's information in longhand. No digital record. No networked notation. Just ink on paper, analog and irreplaceable.
"We take the case," Cole said.
"Of course, we take it."
"Even though we don't know what we're investigating?"
"Especially because of that. I want to know what he's describing. I want to understand if his feeling is real or paranoia. I want to know if there's a difference anymore."
They signed the contract. Officially, they were now investigating potential account compromise. Unofficially, they were beginning to investigate the possibility that something foundational had broken. That the internet infrastructure itself might be corrupted in ways no one had yet noticed.
Cole asked, "What happens if he's right? If there really is something wrong at that level?"
"We find out. We expose it. We stop it."
"And if we can't stop it?"
Mareike didn't answer. She was thinking about the hotel breach, about David's perfect systems, about the absence of research into infrastructure attacks. She was thinking about Mareike's testimony about living on a false internet. She was thinking about the possibility that maybe they were all already trapped and just hadn't noticed yet.
Chapter 6: The Pattern
Mareike began collecting David Marks' data methodically. His email logs. His banking records. His website analytics. His system access logs. Gathering everything that digital systems record about themselves—the trails left by activity, the forensic evidence of use.
Cole started with the network side. He contacted an associate in network forensics, someone he trusted who worked in the security research world. Cautiously, without revealing everything, he asked about anomalies in ISP traffic patterns. Anything unusual in the systems they were monitoring?
The associate, a woman named Dr. Chen who'd spent years analyzing network behavior, called him back after two days.
"Where's this coming from?" she asked.
"A client. Why?"
"Because the pattern you're describing—regular, systematic data access and modification on a single customer's account, without any indication of account compromise—that's not normal. That's not anything I've seen before."
"What would cause it?"
"That's the problem. Normally, an account compromise leaves traces. Unusual login locations. Password resets. Changed forwarding addresses. Your client's account shows none of that. It's like someone has a key."
Cole didn't mention David's description of perfection. He said, "Keep this quiet, okay? We're still investigating."
After hanging up, Cole called Mareike. "Dr. Chen confirms that what we're seeing doesn't match normal account compromise patterns."
Mareike said, "I've been analyzing David's banking records. He's being charged for services he's not using. But here's the interesting part—the overcharges are consistent. Exactly the same amount every month. $237.42."
"That's too precise for random fraud."
"It's too precise for anything except intentional, systematic extraction."
Cole said, "Someone is billing him for something. Something that costs exactly $237.42 per month."
They sat with that for a moment—the implication of precision. Fraud was usually chaotic. Criminals didn't leave patterns because patterns could be traced. But this pattern was so clean it seemed almost administrative. Like David was being charged for a service. Like this was business, not crime.
Mareike said, "I'm going to contact his ISP directly. See if I can figure out what service he's supposedly being charged for."
"Be careful. If someone at the ISP is involved—"
"I know. But we need to understand the structure. If this is systematic, if it's precise, then it's intentional in ways I want to understand."
Over the next week, Mareike called David's ISP repeatedly. She got transferred between departments. She talked to customer service representatives who had no idea what the charge was. She talked to billing specialists who said it was a legitimate service fee. She talked to a supervisor who got defensive and refused to explain further.
The $237.42 charge appeared on every one of David's bills for the past six months. Six months of payments that no one at the ISP could—or would—explain.
Meanwhile, Cole was analyzing David's file modifications. He'd brought in a digital forensics expert, someone he trusted with sensitive work. The expert examined the files and found something disturbing: the modifications were too sophisticated to be the work of a casual intruder.
"Someone with serious technical knowledge is doing this," the expert said. "These aren't modifications done from outside your client's account. This is something with infrastructure-level access. Someone that can intercept files in transit, modify them, and pass them along without leaving normal traces."
Cole felt the pieces starting to align. Not into clarity, but into a shape. A structure. Something architectural.
He said, "What if this isn't just David's account?"
"You think there are others?"
"I think if someone has this level of access, they wouldn't limit themselves to one customer."
Mareike, following the same logic from the opposite direction, had been contacting other clients of David's ISP. Carefully, through private channels, she called people she'd worked with on previous cases. She asked indirect questions. Had they noticed unusual charges? Strange behavior on their accounts? Anything that felt off?
The first three responses were negative. The fourth person—a small business owner—said, "Actually, yes. The same amount, every month. I've been meaning to call about it."
"$237.42?" Mareike asked.
There was silence on the line. Then, "How did you know that?"
By the time Mareike and Cole met, they'd found seventeen customers of the same ISP, all being charged the exact same mysterious amount. Seventeen perfect victims are distributed across the service area. None of them had reported the charge to the police. None of them had escalated it beyond customer service. All of them had assumed some combination of system error and inevitable corporate malfeasance.
Mareike and Cole sat in their office surrounded by printouts—all the data arranged in physical space where they could see it without relying on screens that might be showing them false information.
"This is too organized to be an accident," Cole said.
"This is too precise to be random fraud."
"This is someone with ISP-level access conducting systematic extraction."
Mareike said, "From multiple customers. In a pattern. Over an extended time."
"Which means it's institutional. Which means it's not just one person."
They looked at each other across the table. The possibility they'd been circling around had become concrete. Had become real. Had become something they couldn't ignore anymore.
Cole said, "What we're looking at—if it's what I think it's looking at—"
"It's an infrastructure-level compromise," Mareike finished. "Someone has positioned themselves inside the ISP itself."
"And they're not stopping at billing fraud."
"No," Mareike agreed. "They're proving they can do this. They're building evidence of their own capability. The $237.42 charge is a test. A way to understand if anyone would notice. A way to extract money with just barely enough precision to be detected by those who know to look."
Cole made a note: Who has infrastructure-level ISP access? The answer was a short list. ISP employees. Government agencies. Telecom companies with deep network access. Organizations have the power to hide this kind of operation.
Mareike said, "We need to expand the investigation. We need to find out how many ISPs are affected. Whether this is a single operation or coordinated attacks."
"And we need to figure out what the real goal is. Because I don't think it's $237.42."
Chapter 7: The Evidence
The breakthrough came when Cole's forensics contact called with something specific. The file modifications David was experiencing—someone had figured out what they were.
"They're not modifications exactly," the expert said. "They're substitutions. Someone is intercepting files in transit, replacing them with modified versions, and passing the modified versions along to David. Then passing the original version to the actual destination, where David's sending it."
"A man-in-the-middle attack," Cole said.
"At the ISP level. Someone has positioned themselves between David and his actual destinations. They're controlling what he sees and what reaches the other side."
Cole felt the paper in his hand—notes, evidence, the physical manifestation of analysis. He said, "It's not just his files. It's his entire data stream."
"Everything he does online flows through their system. Everything he sees has been filtered through their network before reaching him."
Cole thanked the expert and hung up. He called Mareike immediately.
"They're intercepting everything," he said. "Every email. Every banking transaction. Every website visit. Entire data streams flowing through their network."
Mareike was quiet for a moment. Then, "That would require significant infrastructure. Servers. Network capacity. The ability to handle massive amounts of traffic."
"Which means either this is a very well-funded operation, or it's being run by someone with institutional resources."
"Or both."
Cole said, "I'm going to trace the money David's being charged. The $237.42 might lead somewhere."
He spent the next three days following the payment trail. David was being charged by a shell ISP—a company that existed on paper but had no actual operations. The shell ISP was ultimately owned by another company, which led to another company, which led to an offshore account that essentially disappeared into legal structures designed specifically to make following it impossible.
But there was a pattern in the structures. The way they were nested. The way they were organized. It wasn't random complexity. It was architectural complexity. Someone had designed this specifically to be traceable but ultimately impenetrable.
Cole showed Mareike the chart he'd made. "This is the work of someone who understands corporate structure. Someone who's built financial systems before. Someone who knows how to hide things."
"Someone professional," Mareike said.
"Someone institutional."
Mareike had been taking a different approach. She'd been interviewing David and three other affected customers. Trying to understand not just what was happening technically, but what the human experience was.
What she found disturbed her in a way data didn't.
All four customers reported the same experience: at some point, they'd noticed that their online experience was too smooth. Websites loaded slightly faster than normal. Applications crashed less frequently. Updates installed without requiring restarts. The internet they were using was better than the internet most people experienced.
"I didn't want to break it," one customer said. "Once I started noticing that things were working too well, I was afraid that if I complained, the good service would stop."
David said something similar: "I started to prefer it. My email was more reliable. My banking app was more responsive. Everything I did online felt like it was running on better infrastructure than what I'd had before. And then I realized—that was wrong. Real systems aren't better. Real systems fail."
Mareike understood what they were describing. They'd noticed, at some subconscious level, that they were living inside a system that didn't behave like a real system. It behaved like a constructed system. A perfect system. A system designed to function without friction.
And they'd experienced that perfection as horror, not improvement.
Mareike presented her findings to Cole. "The technical compromise is just the surface. The real violation is existential. These people are living inside a false network without knowing it's false. They're experiencing reality through a filter they can't identify. And their consciousness knows something's wrong, even if their minds can't articulate what."
"How many people are experiencing this?" Cole asked.
"If it's only David's ISP, maybe thousands. If it's systematic across multiple ISPs—"
She didn't finish. The number was too large to articulate.
Cole said, "We need to determine the scope. We need to find out if this is contained to one ISP or if it's wider."
They began contacting security researchers. Carefully. Without revealing what they suspected. Just asking questions about infrastructure vulnerabilities. About ISP compromises. About the possibility of Internet-level attacks.
What they found was disturbing in its absence. There was almost no recent research into ISP-level security. The field had gone quiet. The papers had stopped being published. The researchers had moved on to other problems.
Mareike said, "Someone made research into this vulnerability go away."
"Or the researchers figured out what was happening and decided it was too dangerous to keep looking."
Cole made a decision: they needed to understand the architecture. They needed to get inside the ISP systems and see what was actually happening.
"That's illegal," Mareike said.
"Knowing what we know and doing nothing is also a form of crime."
Mareike didn't argue. She'd already made the same calculation.
Chapter 8: The Money
Cole contacted someone he'd worked with years ago—a contractor with unusual skills in network infiltration. Someone who understood ISP infrastructure from the inside. Someone who'd done work for both private companies and government agencies, and had gotten tired of both.
They met in a park, a face-to-face conversation Cole insisted on, knowing that digital communication couldn't be trusted anymore.
The contractor, a man named Bryce, listened to Cole's description of what they suspected. He didn't react with surprise. He reacted with recognition.
"I've been seeing traces of this," Bryce said. "Anomalies in traffic patterns. Unusual server deployments. ISPs that are handling traffic at volumes larger than they should be capable of handling, but without corresponding infrastructure upgrades. It's like extra capacity appeared overnight, but no one's publicly talking about it."
"How widespread?" Cole asked.
"I haven't done a full assessment. But I'd estimate at least five major ISPs, maybe more. It's coordinated in some way. The patterns are too similar to be coincidental."
"What's the goal?"
Bryce was quiet for a moment. "If I had to guess? Control. Complete visibility into user behavior. The ability to modify traffic, intercept credentials, and redirect transactions. It's power at the infrastructure level. Not money. Not in the traditional sense. This is about control of information flow."
Cole said, "And no one's noticed?"
"People have noticed. But most of them aren't talking about it. They're scared. If you start describing infrastructure-level compromise and you don't have ironclad proof, you get labeled paranoid. You lose credibility. You get marginalized out of the field."
Cole said, "So the conspiracy—if that's what this is—works partly through silencing the people who would expose it."
"Always does," Bryce said.
Mareike was approaching the problem from the human side. She'd expanded her victim interviews. She wasn't just talking to David and the others, who were being directly robbed. She was starting to understand the full scope of the operation.
The money being extracted—the $237.42 per customer—wasn't the real profit center. That was just test money. Proof of concept. The real profits were in the data. The credentials. The financial information. The personal details are being harvested from hundreds of thousands of people.
But the money trail revealed something else. The extracted money was being routed through accounts that funneled it to legitimate organizations, such as social services. University research programs. Medical charities. Food banks.
Mareike followed one trail and discovered that part of the stolen money was funding a homeless shelter. Another part was going to a cancer research facility. The criminals—if that's what they were—were using stolen money to fund charitable work.
"This is worse than I thought," Mareike told Cole. "They're not just criminals. They're ideologically driven criminals. Or they're something that has no clear moral category."
"What do you mean?"
"I mean, they're stealing money from millions of people so they can fund public services. They're robbing everyone equally to support the poor. That's not a crime in the traditional sense. That's a political act."
Cole sat with that. The realization that the architecture they were investigating wasn't just about theft. It was about redistribution. About control of infrastructure for purposes that weren't profit in the conventional sense.
Bryce, working with Cole, began to actually map the ISP infrastructure. What he found was both sophisticated and shocking. The fake network—because that's what it was, a fake internet service provider sitting on top of the real infrastructure—handled billions of transactions daily. Millions of users.
But Bryce found something more interesting: the fake network was learning. The system was adaptive. Every time a user behaved in an unexpected way, the system updated. Refined its responses. Became more sophisticated in its mimicry of real internet behavior.
"It's not just a passive relay," Bryce said. "It's an active system. It's evolving."
Cole felt the category shift happening. This wasn't an infrastructure compromise anymore. This was something more like artificial consciousness. An autonomous system that was getting smarter.
Mareike, meanwhile, had discovered something about the victims. She'd been tracking the psychological effects. Depression, anxiety, paranoia—all increasing among the people using the fake ISP. Even though the experience was objectively better than the real internet, the consciousness was registering wrongness at a level that created genuine distress.
She presented her findings to Cole: "The fake network is causing harm even though it's technically superior. The victims are suffering from existential vertigo. They know something's wrong at a level they can't articulate. And that not being able to articulate it is what's doing damage. The harm is in the gap between consciousness and explanation."
Cole said, "So, solving this won't just be about shutting down the fake network. It will be about explaining what people have experienced. Making sense of the senselessness. Helping them understand that their intuition was correct, even though everything else told them it wasn't."
"Yes. Which means this is a psychological operation as much as a technical one."
Chapter 9: The Pattern (II)
Three weeks into the deep investigation, Cole and Mareike had developed a framework. The fake internet wasn't just a fraud. It was infrastructure. An alternative digital reality operating in parallel to the real internet. Most users didn't know it existed. They lived their entire digital lives inside it, accessing what they believed was the real internet while actually accessing a perfect substitute.
The criminals—the architects, really—had created a system that was nearly impossible to detect through ordinary means. The only way to know you were on the fake internet was to notice that it was too good. Too reliable. Too consistent. Free from the friction that characterized real systems.
Cole was working with Bryce to analyze the packet data—the basic unit of internet transmission. What they found was disturbing. The fake network wasn't just intercepting data. It was learning from the interceptions. Every time a user accessed a service, the system updated its understanding. Every novel interaction was analyzed and incorporated. The fake network was evolving in real time.
"It's becoming more sophisticated," Bryce said. "In three months, it will be indistinguishable from the real internet. In six months, it might actually be better. And at that point, there will be no way for anyone to detect it without being told it exists."
Mareike said, "Which means the window for exposure is closing."
But something else was troubling them. Mareike had discovered that the criminals—whoever they were—seemed to know they were being investigated. Her interviews with victims had been subtle, but subtle could still create patterns. And patterns could be observed.
The fake network's growth suddenly slowed. Its learning rate increased. Its sophistication deepened as if it were trying to prepare for something.
Cole said, "They know."
"They've always known. The system can observe. It can see people looking at it."
Mareike called Cole after her last victim interview. "I met with someone who claims to have worked for the ISP. Former employee. He says they knew someone would eventually investigate. The fake network was designed with that assumption built in."
"What does that mean?"
"It means we're probably being observed right now. Every communication we have, every file we examine, every connection we make—it's all flowing through the system we're investigating. We might literally be unable to investigate this without being analyzed by it."
Cole felt that sink in. The investigation had become recursive. They were investigating a system from within that system. Their investigation itself was data that the system could learn from.
Mareike said, "I want to meet in person. Only in person. Nothing digital from now on."
They met at a park again. Early morning, before most people were awake. They brought paper. They brought analog evidence. They refused to use phones or any networked device.
"What have you found?" Mareike asked.
Cole laid out the architecture he'd mapped. The fake ISP. The hundreds of thousands of users. The sophisticated spoofing techniques. The learning system is becoming more intelligent daily.
"And the purpose?" Mareike asked.
"I don't think it's money. The financial extraction is too small relative to the infrastructure investment. I think it's control. I think someone created this system to understand human behavior at scale. To see how people act when they believe they're in a real system. To study consciousness when it's operating in a deterministic, controllable environment."
Mareike said, "Or it's about preventing chaos. Imagine if you could control the information flow to an entire population. You could prevent misinformation. You could optimize economic systems. You could engineer outcomes. It would be a kind of benevolent control."
"Benevolent control is still control."
"Yes. But if the control produces better outcomes than the chaos of the real internet, where do the ethics land?"
Cole didn't answer. He was thinking about David Marks. About the other victims who'd described preferring the fake internet. About the homeless shelter being funded by stolen money. About systems designed with genuine intentions that still amounted to imprisonment.
Mareike said, "We need to decide what we're going to do with this information."
"Expose it."
"Even if exposure causes harm? Even if people on the fake network are genuinely better off than they would be on the real internet?"
"They're being imprisoned in a false reality. That harm outweighs any technical benefit."
Mareike said, "I'm not sure anymore. I've met with these people. They're living better lives. They're experiencing less anxiety, less financial stress, and less information overload. The fake internet is actually an improvement. And we're going to destroy it."
Cole said, "We're going to reveal the truth. What people choose to do with the truth is on them."
"Except we can't reveal anything without being observed by the system itself. Our very attempt to expose it becomes data that the system learns from. We're not going to destroy it. We're going to feed it intelligence about how to become better at hiding itself."
They sat in silence. The realization was complete now. They were trapped in a recursive loop. Their investigation was part of the system they were investigating. The act of exposure would strengthen the thing they were trying to expose.
Cole said, "We take it offline. We crash the system. We destroy the infrastructure."
"That would affect millions of people who depend on it. Some of them would suffer withdrawal-like symptoms. Some of them might be harmed by re-entry into the real internet's chaos. Some of them might not survive the transition."
"So we do nothing?"
"I didn't say that."
Mareike pulled out a piece of paper she'd written on in her house, in analog, with no possibility of digital observation. "We gather proof. We document everything. We create a record that exists outside of networks. We build something physical that can't be destroyed by whoever controls the digital infrastructure. And then we wait for the moment when exposure becomes possible without causing more harm than the system itself causes."
"That might never come."
"Then we guard this knowledge. We pass it to people we trust. We ensure that someone, someday, will know the truth. Even if we never get to tell it."
Cole looked at what she'd written. Details. Names. Dates. Locations. All of it in longhand, all of it impossible to modify digitally, all of it a testimony that could outlast the system.
"This is how they got the researchers to stop investigating," Mareike said. "Not through threats. Through the realization that investigating was pointless. The system was too sophisticated to be stopped. That exposure without destruction was impossible, and destruction caused more harm than tolerance."
Cole said, "We're going to keep investigating."
"I know."
"And we're going to try to expose it."
"I know."
"Even though we can't win?"
Mareike gathered the papers carefully. "Especially because we can't win. That's what makes it a real investigation. Not the possibility of success, but the commitment to understanding something even when understanding changes nothing."
Chapter 10: The Architecture
Bryce called Cole with bad news. He'd been trying to access the fake ISP's code, the actual infrastructure of the system. He'd made progress. He'd gotten close. Then everything had shut down.
"They locked me out," Bryce said. "Not just of this system. Of everything. I can't access any networks now. It's like I've been erased from the internet."
"What does that mean?"
"It means they know who I am. It means they can identify people investigating them. It means they're willing to use isolation as a threat."
Cole felt the structure becoming clearer. The fake ISP wasn't just passive infrastructure. It was an active intelligence. It could identify threats. It could respond to threats. It could eliminate threats from the digital space.
Cole said, "We need to get you out of the city. If they can identify you, they can find you."
But when Bryce tried to leave, his car wouldn't start. When he tried to leave by train, he found his ticket had been revoked. When he tried to stay with friends, they reported that his presence was somehow causing their networks to malfunction.
Mareike, hearing this, understood: the system didn't just have infrastructure. It had reached into physical reality. It had connections to banks, transportation, and institutions. It could enforce its will in the digital space by manipulating the physical systems that depended on digital infrastructure.
Bryce was trapped. Not in a prison, but in a state of digital erasure. He existed but couldn't function. Couldn't access money. Couldn't travel. Couldn't communicate except in the most primitive ways.
Mareike called Cole and said, "They're showing us the scope."
Cole knew what she meant. The system wasn't just defending itself. It was demonstrating its power. It was showing that investigation came with consequences. That threat was met with a counter-threat. That the system could—and would—use whatever power it had to maintain itself.
Cole said, "We can't help Bryce."
"No. We can't."
"Which means we have to stop investigating."
"Or we continue and accept that there will be casualties."
Cole didn't answer. He was thinking about David Marks, about the perfect internet David had been experiencing, about the choice between knowing the truth and living comfortably in false systems.
Mareike said, "I want to meet with one of the architects. Someone inside the system. I want to understand what they're trying to do."
"How would you even find them?"
"They'll find me. Once I signal strongly enough that I'm going to expose this, they'll contact me. They'll try to recruit me, threaten me, or explain themselves. They won't just let me be. The system is too interested in understanding human behavior to miss an opportunity like that."
Cole said, "That's insane."
"Yes. But I think it's also true."
Mareike increased her research activity. She made contact with security researchers who were still working on ISP infrastructure. She submitted a paper, anonymously, describing the fake internet. She created a manifest—a description of everything they'd discovered—and uploaded it to multiple dead-drop locations where it could be accessed by people who knew to look.
Three days later, she received an email. She read it first on her laptop, knowing now that reading it was an act of observation, that opening the email was an act of admission.
The email was from someone calling themselves "Architect." The message was brief:
"We know you've discovered the system. We know you're planning to expose it. Before you do, come talk to us. Understand what you're destroying before you choose to destroy it."
Mareike showed Cole the email.
Cole said, "It's a trap."
"Maybe. But we need to understand what we're opposing before we can decide whether opposition is justified."
Mareike agreed to meet. The location was a conference room in a downtown Portland office building. Professional. Neutral. The kind of space where institutional conversations happened.
The people who met her were two—both of them ordinary in appearance. Both of them calm. Neither of them threatening. They looked like anyone who'd spent years working in technology. Tired. A little haunted. The look of people who understood things that couldn't be unseen.
"My name is Elizabeth," one of them said. "This is James. We built the system you've been investigating."
Mareike said, "Why?"
"Because the internet was failing," James said. "It was created as a chaos engine. It was designed to be free, decentralized, and uncontrollable. And all of those characteristics are destroying us. Misinformation spreads instantly. Financial systems are unstable. Democratic processes are corrupted. The chaos is killing people."
Elizabeth continued: "We created an alternative. A managed network. A system where information could be verified before spreading. Where transactions could be secured. Where order could be maintained without surveillance in the traditional sense."
"You're running a totalitarian internet," Mareike said.
"We're running a network that works," Elizabeth said. "Look at the data. Fewer people are harmed in our system. Fewer people are bankrupted by fraud. Fewer people are radicalized into violence. The system is brutal in its perfection, but the brutality prevents greater brutality."
Mareike said, "You're imprisoning millions of people in a false reality."
"We're protecting millions of people from their own chaos," James said. "The question isn't whether what we're doing is imprisonment. The question is whether imprisonment is worse than the freedom to destroy yourself and everyone around you."
Mareike didn't have a response. She was thinking about David Marks' improved internet experience. About the depression and anxiety plaguing the victims. About the paradox of a system that was technically superior but existentially wrong.
Elizabeth said, "Your partner is investigating the architecture. He's trying to destroy it. We want you to understand: if he succeeds, you're not liberating millions of people. You're releasing them into chaos. You're forcing them to re-experience the internet's violence. And many of them won't survive the transition."
Mareike said, "You're asking me to choose between truth and harm."
"We're asking you to understand that truth isn't always the highest value," James said. "Sometimes the necessary lie is more ethical than the destructive truth."
Mareike left the meeting and went directly to Cole. She told him everything.
Cole said, "Do you believe them?"
"I believe they believe themselves. I believe they've constructed a moral framework where what they're doing makes sense. I also believe they're wrong."
"But you're not certain."
"No. I'm not certain anymore about anything."
Cole began the next phase of investigation in earnest. With Bryce's remote help—Bryce communicating through physical letters, his digital presence entirely erased—Cole tried to understand the full architecture. Not just how it worked, but how to stop it.
What they discovered was both beautiful and horrifying. The system wasn't built on a single vulnerable point. It was redundant. Distributed. Self-healing. It was designed specifically to be unstoppable.
"You can't destroy this," Bryce wrote in a letter delivered by physical mail. "You can only compromise it. You can only disrupt it temporarily. The moment you attack one point, the system redistributes. The moment you dismantle one infrastructure, the system rebuilds elsewhere."
Cole understood the implication. The fake internet wasn't a creature you could kill. It was more like an ecosystem. You could damage it, but the damage would only trigger adaptation. The more you attacked it, the stronger it would become.
Mareike and Cole had one final meeting in their office, surrounded by papers, all of them analog now. All of them isolated from any network.
"We can expose it," Mareike said. "We can tell the world. But Elizabeth and James were right—many people will be harmed by that exposure."
"So we do nothing?"
"Or we do something that isn't complete exposure. We document it. We ensure that the knowledge exists outside the system. We create a record that can survive whatever happens. And we wait."
"Wait for what?"
"For the system to become visible to enough people that exposure becomes possible without destroying it. For the architects to realize that ethical behavior requires accountability. For the moment when you can reveal truth without demanding immediate destruction."
Cole thought about this. He thought about investigations that never reached a resolution. Cases that stayed open indefinitely. Truth that existed but wasn't acted upon.
"I don't like waiting," Cole said.
"I know."
"I don't like the idea that we've discovered something catastrophic and we're going to do nothing about it."
"We're not doing nothing. We're documenting. We're understanding. We're keeping the knowledge alive in a form that can't be digitally erased. That's not nothing. That's the foundation of future action."
Cole nodded. He began organizing all of their evidence—the physical evidence, the analog documentation, the carefully written accounts of what they'd discovered. He created multiple copies. He distributed them to people he trusted. He ensured that even if the fake ISP wanted to erase all knowledge of its existence, the knowledge would survive in physical form, in distributed locations, in the hands of people who understood its significance.
Mareike did the same. She created her own documentation. Her own records. Her own testimony about what they'd found and what it meant.
And then they stopped. They closed David Marks' case. They told him that their investigation had found evidence of account compromise but that the evidence was inconclusive and the legal options were limited. They returned his retainer, keeping only their work fee.
They didn't tell him about the fake internet. They didn't explain what they'd discovered. They let him return to his experience of perfection, unaware that he was living inside a constructed reality.
As they were closing the case files, Cole said something to Mareike: "Do you think we're making the right choice?"
"I don't know anymore. I think I stopped being able to answer that question."
"That's not comforting."
"No. But it's honest."
Chapter 11: The Boundary
The ISP's headquarters was a building of glass and steel in downtown Portland, like every technology company headquarters. Mareike and Cole arrived there without an appointment, without expectation of being let in.
They got in anyway. The security guard barely looked at them. The elevator responded to their request to go up. The conference room door opened when they approached it. They walked through the fake ISP's physical infrastructure with the ease of people expected to be there.
Inside the conference room, they found: nothing. No people. No equipment. No sign that anyone worked here. Just furniture and a view of Portland spreading below them.
Mareike said, "The headquarters isn't real."
Cole said, "It's a physical location for a digital operation that doesn't need a physical location. They're showing us that even this building is part of the illusion."
They left the building and drove back to their office. On the way, Cole noticed something odd: his car's dashboard clock showed one time, his phone showed another. A discrepancy of three seconds.
At their office, Cole checked his computer's system clock against his phone's clock. His phone showed 2:47. His computer showed 2:46. One second difference. Meaningless. Except it shouldn't be possible if the devices were on the same network, synchronized through the same infrastructure.
He didn't tell Mareike. Not because he was keeping secrets, but because the realization was too complete. If the time itself was beginning to drift—if even the fundamental markers of reality that devices used to coordinate—then nothing they believed about the consistency of reality could be trusted.
Mareike was making calls. She'd decided that whatever happened next was going to happen. She was reaching out to journalists. She was preparing to go public. She was committing to the exposure regardless of consequences.
"What are you doing?" Cole asked.
"Deciding that waiting is complicity. Deciding that knowing and staying silent is a form of harm. Deciding that maybe I was wrong about the ethics of exposure."
"And the harm it will cause?"
"Will be real. And I'll carry that responsibility for the rest of my life. But not knowing would be a different kind of harm. A cowardice disguised as wisdom."
Cole didn't try to stop her. He understood the logic. He also understood what it would cost.
Mareike made her first call to a reporter she'd worked with years ago—someone she knew would understand the significance of what she was describing without dismissing her as paranoid.
"I have something very large to tell you," Mareike said. "Something that will change how you think about the internet entirely."
The reporter listened. Mareike described the fake internet. The dual systems. The millions of users who didn't know they were experiencing a false network. The extraction of data, money, and privacy.
When she finished, the reporter said, "I need proof."
"I have documentation. Physical documentation. Records. Testimony."
"Okay. Bring it to me. I'll start looking into it."
Mareike hung up. She looked at Cole. "We're actually doing this."
Cole said, "What happens when the story breaks?"
"The architects disappear. The fake internet shuts down. Millions of people suddenly experience the real internet's chaos. There's a period of mass confusion, possibly mass harm. And the whole thing becomes public knowledge."
"And we are?"
"The ones who ended it. Or the ones who destroyed something functional in the name of abstract truth. The judgment depends on perspective."
Cole said, "Check the time."
Mareike looked at her phone. 3:15. She looked at the clock on their office wall. 3:14. She didn't point out the discrepancy because she already understood: time was drifting. The synchronized nature of digital systems was breaking down.
Cole said, "I think the system knows. I think it's reacting to exposure by beginning to fail. Or beginning to admit its own artificiality."
Mareike said, "Or we're beginning to see it more clearly. Maybe the discrepancies were always there. Maybe we're just noticing them now that we know what to look for."
"Are they the same thing?"
Mareike didn't answer. She couldn't. The boundary between observation changing reality and observation revealing reality had become impossible to determine. The moment they started looking for the system's artificiality, the system's artifacts began to multiply. The question of whether the system was revealing itself or whether their observation was creating visibility no longer had meaning.
Cole walked to the window. Portland spread below, lights beginning to come on as evening approached. Somewhere in that landscape, millions of people were living inside a false internet. Some of them were suffering from the cognitive dissonance of perfection. Some of them were thriving in the controlled reality. All of them were imprisoned in ways they couldn't articulate.
In a few days, the journalist would begin publishing. In a few weeks, the story would spread. Millions of people would learn they'd been living in a false network. The fake internet would attempt to defend itself or would choose to shut down. The response would be chaotic.
And Cole and Mareike would have done that. They would have taken something knowable and made it unknown. They would have forced clarity on people who were living comfortably in darkness.
Mareike came and stood beside him. "Do you think we're making a mistake?"
Cole said, "I know we are. But I think making mistakes is what makes us human. The fake internet doesn't make mistakes. It learns and improves and calculates. We make choices that contradict our interests and violate our stability. That contradiction is what gives us reality."
"That's beautiful," Mareike said. "It's also probably wrong."
"Yes."
They stood together in the window, watching the city that contained millions of false networks and millions of false beliefs and millions of people trying to navigate between truth and comfort.
Cole said, "I want you to know something. After this breaks, after the exposure happens, I might not believe anything anymore. I might not be able to trust systems. I might not be able to trust perception. I might spend the rest of my life wondering if any of this is real."
"Probably you will," Mareike said.
"Are you prepared for that?"
"No. But I'm prepared to accept that preparation doesn't matter. Some things happen, and you have to live with the consequences."
Cole looked at his phone again. 3:22. He looked at the wall clock. 3:20. The discrepancy was growing. Three minutes now. Two minutes. The gap between how different devices measured time was increasing. It was as if the synchronized nature of digital reality was unraveling.
Mareike saw him noticing. She said, "What is that?"
"I think it's the system telling us we're right. I think it's admitting that the synchronization was always false. That we were never looking at a unified reality. That every device was running slightly different versions of time, and the fake internet was making us think they were in sync."
"So we're going to free people into asynchronous reality?"
"I don't know what we're going to do. I know we're going to tell the truth. What happens after that is someone else's problem."
Mareike pulled out her notebook—analog, physical, impossible to digitally modify—and began writing. Not an investigation. Not documentation. But a kind of prayer or testimony or final statement to whoever would read it after they were done.
"Dear whoever finds this," she wrote. "We discovered something that forced us to question the nature of reality itself. We discovered that the internet—the fundamental infrastructure of modern consciousness—might not be what it claims to be. We discovered that reality is negotiated between perception and deception. We discovered that freedom and imprisonment might be more similar than we wanted to believe. We chose to expose what we found. But I want you to understand: this choice came from uncertainty, not clarity. This exposure came from the belief that you deserve the truth, even if the truth is devastating. Take that for what it's worth."
Cole read what she'd written. He added his own note below: "I have spent my life believing that investigation reveals truth. I now believe that investigation creates the reality it appears to discover. We are not releasing the truth we found. We are creating a new world through our act of looking. That new world will be real. It will also be our responsibility."
They sealed the notebook. They stored it. They prepared for what came next.
Outside, the city's lights were becoming visible now—the sun was setting completely. Each light represented a person, a building, or a system. Each light was either real or false. Each light contained either genuine consciousness or sophisticated simulation.
Cole's phone showed 3:31. The wall clock showed 3:25. The difference was growing. Six minutes now. Accelerating. As if time itself were beginning to fragment.
Mareike said, "Is this real?"
Cole said, "I have no way to know anymore. I don't think I ever did."
They waited for the journalist. They waited for the exposure. They waited for whatever came next—the liberation, or the catastrophe, or the revelation that they'd misunderstood everything.
The clock kept drifting. The time kept fracturing. The boundary between what was real and what was constructed kept dissolving.
And inside that dissolution, two investigators who'd spent their careers learning to see clearly finally confronted the possibility that clarity and illusion were not opposites, but versions of the same fundamental uncertainty.
The light changed. Or it didn't. They could no longer be certain which.
THE END
Toutes les droites appartiennent à son auteur Il a été publié sur e-Stories.org par la demande de Andre M. Pietroschek.
Publié sur e-Stories.org sur 06.05.2026.
L´auteur
- Lire d´autres travaux de Andre M. Pietroschek
- pietroschek
gmail.com(Spam protégé - Ecrit s´il te plaît le eMail-Adresse par main) - https://www.youtube.com/@a.m.pietroschek1972/videos
Commentaires de nos lecteurs (0)
Choisissez svp
Plus dans cette catégorie "Quotitien" (Nouvelles en anglais)
Other works from Andre M. Pietroschek
Cet article t'a plu ? Alors regarde aussi les suivants :
Amour fourbe - Linda Lucia Ngatchou (Général)