Arjun leaned forward, his eyes focused and unwavering as he began planning his next move, fully aware that the situation had reached a critical point where hesitation could cost him everything, and with Rakesh Sharma now actively investigating him from within the network, the balance had shifted into a dangerous territory where only one of them could remain in control without exposing the entire system.
He understood that simply defending himself would not be enough.
He needed to act.
And not just reactively, but strategically—by turning the suspicion back onto Rakesh in a way that would appear natural, undeniable, and completely disconnected from himself, creating a scenario where the system would begin to question Rakesh’s actions instead.
Arjun began by carefully studying Rakesh’s independent operations, the hidden transactions, the unauthorized communications, the side dealings that existed outside the official network structure, all of which pointed toward a man who was not just serving the system, but using it for his own benefit, creating vulnerabilities that Arjun could exploit.
Using this information, Arjun designed a trap.
A controlled operation that would appear to originate from Rakesh’s own network, involving a high-value transaction that would attract attention from the system’s monitoring protocols, but with subtle alterations that would make it look suspicious, inconsistent, and potentially harmful to the stability of the network.
At the same time, Arjun planted digital traces—small but precise pieces of evidence that would link the operation directly back to Rakesh, ensuring that when the system analyzed the activity, the conclusion would be unavoidable.
Everything had to be perfect.
There could be no mistakes.
No loose ends.
Once the setup was complete, Arjun initiated the operation, triggering the sequence that would set everything into motion, and within moments, the system responded exactly as expected.
Alerts began to appear.
Flags were raised.
Internal monitoring systems activated.
The network was reacting.
But this time, the focus was not on Arjun.
It was on Rakesh Sharma.
Within minutes, high-level inquiries were sent, questioning the legitimacy of the operation, demanding explanations, analyzing the data, and as the pressure increased, Rakesh was forced to respond, his activity within the system becoming more erratic, more defensive, as he attempted to regain control of the situation.
Arjun watched silently as everything unfolded, his expression calm, his movements controlled, as he maintained his position, responding only when necessary, ensuring that he remained above suspicion while the system’s attention shifted entirely toward Rakesh.
And then, it happened.
A final alert.
“Unauthorized activity confirmed.”
The system had made its decision.
Rakesh Sharma was now the primary suspect.
What followed was immediate and decisive—his access was restricted, his operations suspended, and a deeper investigation initiated, effectively removing him from his position of influence within the network, at least temporarily.
Arjun exhaled slowly, not in relief, but in recognition of what he had just done, as he realized that he had successfully manipulated the system from within, not just to protect himself, but to eliminate a threat, proving that he was not just surviving inside the network—he was controlling it.
But even as he secured this victory, a quiet thought remained in the back of his mind.
This was only the beginning.
Because if the system could turn on Rakesh so quickly…
It could just as easily turn on him.