The encrypted voice channel materialized at midnight, a static hiss resolving into the modulated tones of Soma-0. Reva had configured her own voice modulator to add a slight metallic timbre, just enough to mask her natural speech patterns without sounding artificial. She sat cross-legged on her hotel bed, laptop balanced on a pillow, a notebook open beside her for real-time transcription notes. The room was dark except for the screen's pale glow, and the only sounds were the distant hum of the city and the voice of a person who had, mere hours earlier, claimed credit for a murder.
"You're punctual," Soma-0 said. The modulator rendered their voice as a low tenor, gender-ambiguous, with the faint echo of someone speaking from a large empty room. "That's rare in new members. Most treat operational security as a suggestion rather than a discipline."
"Operational security is the difference between a purifier and a prisoner," Reva replied, borrowing a phrase she had read in one of Soma-0's own essays. The appropriation worked; she heard a soft grunt of approval on the other end of the line.
"I've been reading your posts in the technical forum," Soma-0 said. "Your analysis of the DronasTech firmware vulnerability was thorough. You understand industrial systems at a level most of our members never achieve. Where did you say you trained?"
"I didn't." Reva was prepared for this. "But since you're asking, I spent eight years with Kalpataru Industrial Security, doing penetration testing for power utilities across the Federated States. I left because I got tired of writing reports that nobody read. I'd find a vulnerability that could kill thousands, and the client would file it under 'acceptable risk' and renew their subscription. The grid is a weapon waiting to be used, and the only people who understand that are the ones who've spent their careers inside it."
There was a pause, filled only by the static whisper of the encrypted channel. Then Soma-0 spoke again, their tone shifting from interrogatory to almost collegial. "Kalpataru is a respectable firm. I worked with one of their alumni years ago, on a project I won't name over an unsecured channel. What did you think of their SCADA assessment framework?"
It was another test. Reva had never worked for Kalpataru, but she had studied their public research papers and conference presentations exhaustively during her years in the Federated States. "The Kalpataru framework is solid on perimeter defense but weak on insider threat modeling," she said. "They assume the enemy is outside the firewall. The smartest adversaries are already inside the control room."
"That's exactly what I told their chief architect at the Pan-Asian Infrastructure Summit in 2019," Soma-0 said, and for the first time, there was something almost warm in their voice. "He didn't listen. Most of them never listen. That's why we exist, Vidyut-Rani. Because the people who build these systems refuse to see what they've actually built."
The conversation shifted, almost imperceptibly, from interview to dialogue. Soma-0 began to speak about the Jakhera Dam with the obsessive precision of someone who had devoted years to understanding a single piece of infrastructure. The dam was not merely a hydroelectric facility; it was, in Soma-0's telling, the central nervous system of northern Bharitpur's power grid. Its twelve turbines generated enough electricity to serve eighteen million people. Its reservoir held enough water to flood three downstream provinces if the control gates were opened simultaneously. And its SCADA architecture, upgraded two years earlier by a SuryaGrid Solutions contract, contained a vulnerability that Soma-0 had discovered eighteen months ago and had been quietly cultivating ever since.
"The vulnerability is in the turbine synchronization module," Soma-0 explained, their voice taking on the cadence of a lecturer who had waited years for an attentive student. "When two turbines are brought online simultaneously, the control system uses a predictive algorithm to balance their rotational speeds. That algorithm was written by a junior engineer who no longer works for SuryaGrid. It contains a buffer overflow condition that can be triggered by a specifically crafted sensor input. If you send the right data at the right moment, you can cause the turbines to desynchronize catastrophically. The resulting mechanical failure would be indistinguishable from a manufacturing defect."
Reva wrote down every word, her handwriting growing smaller and faster as the technical details accumulated. "What kind of failure are we talking about? Electrical outage, or physical destruction?"
"Both. If the turbines desynchronize at full load, the shear forces would tear the rotor assemblies apart. Flying debris would damage the adjacent turbines. The cascade would take out the entire powerhouse. And the sudden loss of generation capacity would cause a frequency collapse across the northern grid. Brownouts in twelve cities. Blackouts in six more. Hospitals on backup generators. Water treatment plants offline. The domino effect would last for weeks."
The scale of it took Reva's breath away. "That's not a purification. That's a war crime."
"It's neither," Soma-0 said, their tone hardening. "It's a deterrent. The dam is not our target. It's our leverage. The Jakhera Dam is the single most heavily guarded piece of infrastructure in Bharitpur. The government has stationed a permanent military detachment there. They've installed anti-aircraft batteries. They've hardened the perimeter against physical intrusion. And none of that matters, because the vulnerability is not in the concrete or the steel. It's in the code. It's in the algorithm that nobody bothered to audit because the junior engineer who wrote it had already left the company and everyone assumed his work was functional."
Reva understood now. Kali-Yantra was not merely an assassination service. It was an insurgency, one that had embedded itself so deeply into the nation's infrastructure that it could hold entire cities hostage without firing a single bullet. The Tantra forum, the tiered subscription model, the cryptocurrency payments—all of it was infrastructure too, a parallel system of governance built on top of the physical world like a parasite on a host.
"You're not telling me this because you value my technical perspective," Reva said carefully. "You're telling me because you want something. What is it?"
Another pause. The static hissed. Then Soma-0 laughed—a dry, papery sound that the modulator couldn't quite disguise. "You really are sharp. Yes, I want something. I want you to review the exploit code for the Jakhera vulnerability. I wrote the core payload myself, but I need a second set of eyes—someone who understands industrial control systems well enough to spot edge cases I might have missed. The other members of the inner circle are talented, but their expertise lies in network intrusion, not in mechanical engineering. You understand both. That's rare. That's valuable."
"And if I refuse?"
"Then you remain a provisional member with Tier 2 access, and someone else reviews the code, and the operation proceeds with whatever flaws it currently contains. I'm not threatening you, Vidyut-Rani. I'm offering you a choice. You can be a passenger in this organization, or you can be a pilot. I've been looking for a co-pilot for a long time."
The word "co-pilot" landed with unexpected weight. Soma-0 was not merely recruiting a technician. They were recruiting a successor, or a partner, or both. The loneliness beneath the modulated voice was suddenly palpable—a person who had built a machine of immense destructive power and had no one to share it with who truly understood its workings.
"I'll review the code," Reva said. "Send it through the secure file transfer. Give me seventy-two hours."
"You'll have forty-eight," Soma-0 replied. "The operation window opens in fifty days, and there are other preparations that depend on your analysis. One more thing—this review requires a higher level of trust. I'm sending you an invitation to a physical meeting. Seven days from now, in the city of Gandhak, there will be a conference on sustainable infrastructure at the Royal Gandhak Hotel. I'll be attending as a registered participant. If you want to meet face to face, this is your opportunity."
The invitation hung in the air like a challenge. A physical meeting meant revealing her face, her voice, her identity—or at least an identity she could construct convincingly. It meant walking into a room with a person who had orchestrated multiple murders and might orchestrate hers if she made a single mistake. But it also meant access to the inner circle, to the operational details that could bring the entire organization down.
"I'll consider it," she said.
"Consider carefully. Trust is a two-way street, Vidyut-Rani. I've shown you the Jakhera vulnerability. Now you need to show me something in return." The channel clicked, and Soma-0 was gone.
Reva removed her headset and sat motionless in the dark. The forty-eight-hour deadline was tight, but the exploit code itself was an intelligence goldmine. If she could analyze it thoroughly, she could identify not only the specific vulnerability but also the coding style, the toolchain preferences, the commenting patterns—all the digital fingerprints that could lead back to Soma-0's real identity. And if she could convince Meera Das and Inspector Jesht to coordinate, they might be able to intervene before the Jakhera operation went live.
But the physical meeting complicated everything. Soma-0 would certainly have counter-surveillance measures in place. The Royal Gandhak Hotel would be scanned for listening devices, for undercover officers, for any sign that Vidyut-Rani was not who she claimed to be. Reva would need a legend—a complete backstory, verifiable employment records, a physical appearance that matched her online persona. She couldn't do it alone.
She called Meera Das on the encrypted line. It was nearly two in the morning, but Meera answered on the first ring, her voice alert and caffeine-fueled. Reva summarized the conversation with Soma-0, omitting only the details of the Saptagram operation that might incriminate her. When she finished, Meera was silent for a long moment.
"The Jakhera Dam," Meera said finally. "I've been warning the National Security Directorate about that vulnerability for three years. SuryaGrid's codebase is a disaster. Half their firmware was written by contractors who never met each other. If Kali-Yantra has a working exploit, we're looking at the most significant infrastructure threat since the cyberattacks on the coastal grid in '22."
"Can you get me access to SuryaGrid's internal code repository? I need to compare the exploit code against the original source to confirm it's genuine."
"I can try. But SuryaGrid is a private company with government contracts. They don't share their codebase with anyone, not even under court order. They claim trade secrets. They claim national security. What they really mean is they don't want anyone to see how badly their software is written." Meera's voice was bitter with years of accumulated frustration. "I'll pull what I can from the regulatory filings. They're required to submit security audits to the Energy Commission every two years. The audits are usually sanitized, but sometimes the technical appendices contain useful fragments."
Reva spent the next thirty-six hours in a fugue state of analysis. The exploit code arrived through the secure file transfer at three in the morning—twelve thousand lines of elegantly commented code written in a mix of C and Python, with embedded Assembly for the low-level hardware instructions. The code was beautiful in the way a well-designed weapon is beautiful. It was modular, well-documented, and horrifyingly efficient. It exploited the buffer overflow in the turbine synchronization module exactly as Soma-0 had described, and it included fallback routines that would attempt alternative attack vectors if the primary exploit was patched.
She analyzed the coding style with forensic attention. The commenting conventions were consistent with someone trained in European academic computer science—specific formatting patterns, a preference for certain variable naming conventions, a distinctive way of structuring function headers. The code referenced three obscure libraries that were primarily used in German and Swiss engineering programs. And buried in the comments of one subroutine, there was a stray reference: "See Muller et al., 2017, Journal of Embedded Systems Security, for the theoretical basis of the cascading desynchronization approach." The citation was too specific to be fictional. Somewhere, a researcher named Muller had published a paper that Soma-0 had read and incorporated into their work.
Reva searched academic databases for the citation and found the paper. It had been co-authored by a team at the Technical University of Zurich, including a postdoctoral researcher named Anselm Muller who had subsequently left academia for a private-sector position. His LinkedIn profile, still publicly accessible, listed his current employer as "SuryaGrid Solutions, Senior Systems Architect, 2018-2023." He had worked on the very turbine control system that contained the vulnerability. And his profile picture showed a man in his late forties with tired eyes and a faint smile, standing in front of a server rack in what appeared to be a data center.
Reva saved the profile and cross-referenced it with SuryaGrid's corporate registry. Anselm Muller had left the company abruptly in mid-2023, shortly after the Jakhera Dam upgrade was completed. His departure had been classified as a "mutual separation," and he had signed a non-disclosure agreement that prevented him from discussing his work. Since then, his digital footprint had gone almost entirely dark—no new publications, no conference appearances, no social media activity. Almost as if he had deliberately erased himself from the public record.
Almost as if he had something to hide.
She sent the analysis to Meera Das with a terse note: "Soma-0 may be Anselm Muller, former SuryaGrid architect. Currently untraceable. He's attending a conference at the Royal Gandhak Hotel in seven days. I need a legend and a surveillance team if I'm going to meet him face to face."
Meera's response came within the hour: "I'll arrange both. But Reva, if this is Muller, you need to understand what you're dealing with. He didn't just work on the Jakhera system. He designed it. He knows every line of code, every failsafe, every backup system. If he's really Soma-0, he's been planning this operation for years. You're not infiltrating a terrorist cell. You're walking into a trap designed by the smartest engineer in the room."
"Then I'll be the second-smartest," Reva typed back. "And I'll know where the trap is before I step into it."
She closed the chat and opened her laptop's camera, studying her own reflection in the lens. In seven days, she would need to become someone else entirely—someone confident enough to meet a killer's eyes without flinching, someone credible enough to convince a genius that she shared his vision. She was not sure that person existed yet. But she had seven days to invent her, and seven days to prepare for the moment when the screen between her and Soma-0 finally disappeared.
No comments yet. Be the first to comment!