Sshrd Script -

Then, a new line appeared:

Lin let out a breath she didn’t know she’d been holding. The bastion was still standing. The DR VM was alive. And because sshrd had used only native SSH—no extra agents, no APIs—it had left zero logs the attackers would think to check.

The corporate network had fallen hours ago. Ransomware, the kind that didn’t just lock files but laughed at you while doing it, had crawled through every primary server. The C-suite was screaming into a dead satellite phone. The backups? Also encrypted. The only machine still clean was this ancient CentOS bastion host—a forgotten sentry at the network’s edge, running nothing but SSH and Lin’s custom script. sshrd script

[dr-vm restore] Checksums verified. Volume snapshot mounted. Ransomware beacon spoofed. All clean.

The terminal spat out lines:

She hit Enter.

Lin’s fingers flew across the keyboard, each keystroke a tiny act of defiance. On her screen, a single line of text glowed in the terminal: Then, a new line appeared: Lin let out

The attackers had left one thread uncut: the bastion’s outbound SSH keys to a tiny, off-site disaster recovery VM in a different cloud region. The VM had no public IP, no DNS—just a hidden internal address reachable only via the bastion. If Lin could jump through the bastion and push a clean restore script onto that VM before the malware spread there too…

./sshrd.sh --target bastion.corp.local --jump dr-vm.internal --payload restore_toolkit.tar.gz And because sshrd had used only native SSH—no

But this time, she’d added a twist. The restore_toolkit contained not just backup utilities, but a decoy: a small, self-deleting worm that would mimic the ransomware’s beacon—reporting back to the attacker’s C2 that the bastion was also dead. A lie wrapped in an SSH tunnel, delivered by her own homemade script.

She opened a new terminal. Typed: