The Tantra operations channel flickered to life at 01:58 local time, a minimalist interface of green text on black background that reminded Reva of the terminal emulators she had trained on as a teenager. She was logged in as Vidyut-Rani, her presence marked by a small lotus icon next to her username. Six other users were already in the channel, their names a constellation of Sanskrit phonemes: Agni-4, Chakra-7, Soma-0, Matsya-3, Vayu-11, and Prithvi-2. The full pantheon of elemental purifiers, assembled to observe the initiation of their newest recruit.
Matsya-3 was the operation lead, and their messages appeared in a slightly different shade of green, a subtle hierarchy encoded in hexadecimal. "Target status: asleep. Water heater idle for six hours. Building network intrusion confirmed. Vidyut-Rani, you have command. Execute at your discretion." The words were dispassionate, the tone of a surgical team waiting for the lead surgeon to make the first incision.
Reva's fingers hovered over her keyboard. The exploit kit she had modified was loaded and ready, its payload rewritten to trigger a diagnostic self-check instead of a thermal runaway. The code would connect to the target's smart water heater through the manufacturer's cloud API, initiate what appeared to be a standard firmware update, and then abort with an error code that would read as a hardware incompatibility. The water heater would beep once, log a failed update, and return to idle. The target—a municipal official named Devendra Paswan who had indeed been accused of embezzling water purification funds, though the courts had actually deadlocked rather than acquitted—would wake in the morning with nothing more than a blinking error light on his appliance.
But the execution had to be flawless. The other users in the channel were monitoring the operation through a parallel dashboard that displayed real-time telemetry from the target's device: power draw, water temperature, pressure readings, network latency. Any deviation from the expected attack pattern would be noticed immediately. The original exploit was designed to cycle the heating element in a specific sequence that would cause a steam pressure buildup. Reva's modified version needed to replicate that sequence's network traffic signature while producing a different physical outcome.
She typed: "Initiating connection to target device. Cloud API handshake in progress." The words felt surreal, as if she were narrating a dream in which she had become the villain of her own story. The API handshake completed in milliseconds, and her exploit began to execute. On her screen, the diagnostic logs scrolled past in a controlled cascade. The water heater's firmware accepted the incoming command packet. The heating element began to cycle. And then, precisely at the moment when the original exploit would have disabled the safety cutoff, her modified code inserted a different instruction: a self-test routine that checked the thermostat calibration and then aborted all active processes.
The telemetry dashboard showed a brief spike in power draw, followed by a flatline. The water temperature rose by 0.3 degrees Celsius, well within normal fluctuation range. The pressure sensor registered no anomaly. The device beeped once—a soft electronic chirp that would be barely audible in a sleeping household—and displayed a maintenance alert on its front panel.
Reva typed: "Payload delivered. Thermal runaway signature detected. Awaiting pressure buildup." She held her breath, counting the seconds until the other users would realize the expected explosion was not going to happen.
Chakra-7 responded first: "Pressure readings remain nominal. Anomaly detected. Vidyut-Rani, confirm payload integrity." The question was technical, but the implication was sharp-edged. In this community, technical failure was indistinguishable from sabotage, and sabotage was indistinguishable from betrayal.
She had prepared for this. "Target device is running an undocumented firmware patch," she typed. "The safety cutoff protocol has been modified by the manufacturer since the last intelligence update. The exploit triggered a diagnostic override instead of a thermal runaway. I'm seeing error code 0x7F3 in the device log. This is a known issue with the DronasTech Gen-4 water heater series manufactured after the third fiscal quarter." She pasted a snippet of fabricated error log into the channel, its hex codes meticulously constructed to match DronasTech's actual diagnostic format—she had spent two hours that afternoon studying the company's public firmware documentation to ensure the forgery would pass scrutiny.
A long pause followed. In the silence, Reva could hear the hum of her hotel room's refrigerator, the distant honk of a rickshaw horn in the street below, the thud of her own heart against her ribs. Then Soma-0 spoke, their text appearing with the weight of authority: "The error code is genuine. I've cross-referenced it with DronasTech's internal knowledge base. This is a known issue in units manufactured after the September batch. The operation was compromised by a supply chain variable we failed to account for. This is not operator error. This is an intelligence gap."
Relief flooded through Reva so intensely that she felt lightheaded, but she kept her response measured: "Recommend we update the target intelligence database to include firmware revision numbers for all future operations. This failure was preventable." She was speaking their language now—the language of continuous improvement, of blameless post-mortems, of systems thinking applied to murder. The role was becoming easier to inhabit, and that ease frightened her more than the risk of exposure.
Matsya-3 closed the operation with a formal acknowledgment: "Vidyut-Rani, your execution was technically sound. The failure lies in our intelligence, not in your performance. You are granted provisional membership with access to Tier 2 resources. Full membership pending a successful operation within thirty days." The lotus emoji appeared, followed by similar acknowledgments from the other users. One by one, they logged off, until only Reva and Soma-0 remained in the channel.
"You handled that well," Soma-0 typed. "Most recruits panic when an operation goes sideways. You stayed analytical. Where did you train?"
Reva hesitated. The question was casual, but Soma-0 did not ask casual questions. Every interaction with this user felt like a chess move, and she was perpetually playing black. "Self-taught," she replied. "I've spent years in industrial control systems, mostly on the defensive side. Vulnerability assessment, penetration testing. The private sector pays well but teaches you nothing about justice. I came here because I wanted my skills to mean something."
There was another pause, longer this time. Then Soma-0 sent a private message, outside the operations channel: "Come to the philosophical forum tomorrow. I'm posting a new essay on the Jakhera Dam. I'd value your technical perspective on the SCADA architecture. Your background in industrial systems suggests you might have insights the others lack."
The invitation felt like a door opening into deeper darkness, and Reva knew she would walk through it. "I'll be there," she typed, and logged off.
She closed her laptop and sat motionless in the darkness of her room. The operation had succeeded—not in harming anyone, but in preserving her cover and advancing her infiltration. Yet the victory felt hollow, even nauseating. She had just participated in a simulated murder attempt, and the only reason no one had been hurt was that she had sabotaged her own attack. The members of Tantra had reviewed her performance as if it were a code submission, and they had found her worthy of provisional trust. She was inside now, deeper than any investigator had ever gone, but the cost was a small piece of her own moral clarity, and she did not know how many pieces she had left to lose.
She slept fitfully, dreaming of water heaters that grew limbs and crawled across kitchen floors, of her sister's face reflected in a digital control panel, of a lotus blooming in time-lapse and each petal that unfurled revealing a line of hexadecimal code.
In the morning, she received a call from Inspector Jesht. His voice was strained, carrying an urgency she hadn't heard even during the Kiran Mokri investigation. "There's been a major incident in your city," he said. "Mekhal. Last night, around two in the morning. A residential building in the Panchavati district lost power for about ninety seconds. During the outage, a man named Rohan Varma—no relation to the professor, as far as we can tell—was electrocuted in his apartment. He was a witness in an ongoing corruption case against the Mekhal municipal water board. The timing is suspicious."
Reva felt the blood drain from her face. "Electrocuted how? The power was out."
"That's what we're trying to understand. His apartment had a backup generator, one of those automatic transfer switches that kick in when the grid goes down. The switch malfunctioned and sent a surge through the wiring while he was touching a metal light fixture. The generator's control unit was connected to the internet for remote monitoring. And the building's smart meter logs show a brief command signal received about ten seconds before the transfer switch activated. The signal originated from an IP address in Saptagram."
Saptagram. The city where she had just conducted her ersatz operation against Devendra Paswan. The coincidence was too precise to be a coincidence at all. "The signal was routed through Saptagram," she said, "but that doesn't mean the operator was there. It could be a relay point, a compromised device being used as a proxy."
"I was hoping you'd say that," Jesht replied. "Because the Saptagram police have already identified the IP address. It belongs to a residential water heater registered to a man named Devendra Paswan. The device's network logs show it was compromised approximately three weeks ago and has been used as a botnet node ever since. Someone was using his water heater as a launchpad for a murder in another city."
Reva closed her eyes. The operation she had been assigned—the operation she had believed was a test—had been a diversion. While she was focused on the water heater, proving her loyalty by attempting a non-lethal warning, someone else had used the same device as a proxy to execute a far more lethal operation in Mekhal. She had been a patsy, or worse, an alibi. If the Mekhal murder was traced back to the Saptagram water heater, the digital trail would lead investigators to the Tantra forum, and there they would find evidence of Vidyut-Rani's presence in the operations channel, her careful messages, her precise execution. She would be the face of the crime, while the true perpetrator vanished into the anonymous depths of the network.
"They set me up," she whispered.
"Who set you up?" Jesht's voice sharpened. "Reva, what have you gotten yourself into?"
She couldn't answer honestly without incriminating herself, and she couldn't lie without severing her most valuable law enforcement connection. She chose a middle path: "I'm tracking a group called Kali-Yantra. They're using infrastructure as a weapon, and I think they just used me as a scapegoat for a murder I didn't commit. I need time to figure out who orchestrated this and why. Can you hold off on the Saptagram connection for twenty-four hours?"
"Twenty-four hours," Jesht said slowly. "After that, I have to share what we have with the national cybercrime unit. Reva, if you're in danger—"
"I'm always in danger," she said. "That's the whole point of their system. Everyone is in danger, all the time, and nobody knows it until the lights go out."
She ended the call and immediately logged back into Tantra. The philosophical forum was active, and Soma-0's new essay had just been posted. The title was "The Cascade Principle: Why Single Points of Failure Are Ethical Necessities." She scrolled past the dense philosophical preamble until she found the section on the Jakhera Dam, and there, embedded in a paragraph about turbine control redundancy, was a line that made her stop breathing: "Last night's demonstration in Mekhal proved that a compromised node in one city can deliver judgment in another, with the operator safely insulated by layers of distributed infrastructure. The Rohan Varma operation was not merely a purification. It was a proof of concept for the Cascade Principle. And it succeeded beyond all parameters."
Reva stared at the screen. Soma-0 was not just a philosopher of infrastructure violence. Soma-0 was claiming authorship of the Mekhal murder. And Reva's own operation in Saptagram had provided the compromised node that made it possible. She had been woven into a killing she did not see coming, and the person who had woven her was now inviting her to discuss dam architecture in a private forum, as if they were colleagues sharing a research interest.
She typed a reply to Soma-0's private message from the night before: "I read your essay. The Cascade Principle is elegant. I'd like to understand the Mekhal demonstration in more technical detail. Can we discuss it in a secure channel?"
The response came almost instantly: "I was hoping you'd ask. You're ready for the next level, Vidyut-Rani. Meet me in the encrypted voice channel at midnight. There's something I want to show you about the Jakhera Dam that will make the Mekhal operation look like a fire drill."
Reva saved the message and began preparing her voice modulator—a piece of software that would disguise her speech patterns while analyzing Soma-0's for any traceable acoustic fingerprint. She was walking into the center of the web now, and the spider was waiting. The only question was whether she would be a guest or a meal.
No comments yet. Be the first to comment!