New to Other-Terrestrial? Check here! Or if you need to, jump to the beginning of the episode here!
Of all places on Gohhi, the server hubs were perhaps the most valuable. It was said that they were better guarded than even the air recirculator systems that kept the station alive. The data in the servers contained financial and economic data that spanned every major station in the territory, which in the eyes of those who owned it, was worth far more than human life.
Which meant that it made no sense to see the gap in the defenses.
“I can’t understand it,” he muttered. “It smells like a trap . . .”
“I can go in and simply destroy what needs destroying,” Kell said calmly.
“No, we don’t know what server it’s on. There are millions of micro-servers in there . . .”
“Then I will destroy them all,” Kell retorted with a shrug. He started forward.
“No! That will be a disaster on an incredible scale for Gohhi! We have to do this surgically.”
Kell scowled. “You have many restrictions on your actions.”
“Yes. It’s part of being in a civilization.”
Kell sighed. “One reason my people did not live in one.”
As interesting as that comment was, Urle was more concerned with the server. He could see no reason why they might be setting a trap, as there was no evidence that Madspark’s body had even been discovered yet. When it was, it would certainly raise some flags.
While patrols of guards and drones went around the outside of the building, there was a definite gap, though.
When that gap came – only twenty seconds – he moved, gesturing Kell to move with him. In five seconds they were at the door, and in three more he’d connected. Another seven seconds had the door open, and with two seconds left to spare the door closed behind them.
“Easy,” he muttered. But these were only the first steps. The internal security was the real problem.
“I could have just forced the door,” Kell said.
Urle was busy looking down the hall. There was not much to this building except for a main hallway, with branching corridors leading to server rooms or cooling rooms, and various other equipment. There was no staff even inside the building at most times, and so no break or guard rooms.
The armed drones, those could be an issue.
But as he connected to the building’s internal systems, he found that they too were behaving oddly. There was an instability in their algorithms that had left large gaps in their search patterns, enough that they could easily get into the server rooms without being seen. What was more was that in four hours the glitch would cycle itself out and they’d be back to normal.
Someone else had been in here. Both physically and digitally.
Which made sense, if someone wanted to hack the servers it was far easier if you could get in – doing it remotely would typically leave far too many traces in the networks, and all the defenses were built against that sort of attack precisely because the drones and guard patrols were typically enough for the outside.
“Follow me,” he said. “We have to move quickly.”
The scuffed search pattern didn’t even cover the door, but the logs had already been falsified to make it seem as if they had been. Whoever had done this was on another level entirely – he truly could not have done better.
The fact that this break-in had occurred so recently seemed impossible to be a coincidence. He had to see the data to try and get an idea of what they had been up to – but if they were this good he might not find any clues at all.
Making their way down the halls, avoiding the drones, they entered a server room he thought most likely to have at least some of the camera data from around the shop.
Racks of servers lined the walls, cooling tubes going between them, with barely enough space between the racks for a person to walk. Each server was about the size of two human hands and about as thick, stacked on the cooling racks only a centimeter apart, going up almost three meters into the air. Tens of thousands of the machines in this room alone, able to carry and sort tremendous amounts of data.
Aside from indicator lights on the servers to show their status, there was almost no light. But that was fine. With a few sonar pulses he’d mapped the room, confirmed that there were no security drones present, and then connected.
Checking locality data, he found that he’d guessed right. Looking to the data around the aug shop, though . . .
He found no evidence of himself and Kell at all.
“Someone’s already been here,” he said. “They’ve . . . helped us.”
“Hm,” Kell commented, seeming unimpressed.
“Doesn’t that disturb you?”
“Not particularly,” the Shoggoth replied. “It sounds convenient.”
Urle grumbled but said no more. Instead, he began probing deeper into the servers in the room, trying to find an abnormality in the data, a track – something that might give him a clue about the person who had been in here before them . . .
They were not sloppy, he realized.
And then he triggered the flag.
He hadn’t even detected it in the files; it was keyed to his hardware ID, which was insane; it meant that they knew that he himself would come here.
He almost reflexively disconnected, but the program that executed was only a single line of text.
Cautiously, he took it in.
RACK 37 | SHELF 5 | SERVER 12 | MANUAL CONNECT
Then it deleted itself.
“What has alarmed you?” Kell asked.
“. . . the person who was in here left a message for me, specifically. They knew I’d come here.”
“They know much,” Kell replied, a note of curiosity in his voice.
“An insane amount,” Urle said. “They know my personal identifier code, knew I’d come here, and their work deleting the data was better than what I could have done.”
He toggled his vision of the real-world back on and looked around. Everything could be booby-trapped and he’d not even see it. Hell, he could already have gotten a virus and not know it . . .
Would he take the risk of manually connecting to the server they’d told him . . . ?
Taking a deep breath, he disconnected and walked over, counting the racks until he’d found 37.
Kneeling down, he found the twelfth server on the fifth shelf. It appeared entirely normal from the outside, aside from some very slight wear on the edges of its external port. Someone had been manually jacking into this one lately . . .
He connected, putting up all the security he could manage, and found that the actual contents of the server was nothing like what the main directory indicated. It should have been serving to route data from one of the bulk import sections, but instead . . .


You must be logged in to post a comment.