Artificial Condition (The Murderbot Diaries, #2)(16)
Then twenty-four minutes forty-seven seconds into the flight, as we were on approach, the bot pilot screamed and died as killware flooded its system. It was gone before ShuttleSecSys or I could react; I flung up a wall around us both and the killware bounced off. I saw it register task complete and then destroy itself.
Oh, shit. ART! I used ShuttleSecSys to grab the controls. We needed the course correction in seven point two seconds. The crew member, jolted out of her feed by the alarms, stared at the board in horror, then hit the emergency beacon. She couldn’t fly a shuttle. I can fly hoppers and other upper atmosphere aircraft, but I had never been given the education module for shuttles or other space-going vehicles. I nudged ShuttleSecSys, hoping for help, and it set off all the cabin alarms. Yeah, that didn’t help.
Let me in, ART said, as cool and calm as if we were discussing what show to watch next.
I had never given ART full access to my brain. I had let it alter my body, but not this. We had three seconds and counting. My clients, the other humans on the shuttle. I let it in.
It was like the sensation humans describe in books as having their heads shoved underwater. Then it was gone and ART was in the shuttle, using my connection with ShuttleSecSys to leap into the void left by the erased bot. ART flowed into the controls, made the course correction and adjusted our speed, then picked up the landing beacon and guided the shuttle into approach on the main RaviHyral port. The crew member had just managed to hail Port Authority, and was still hyperventilating. Port Authority had the ability to upload emergency landing routines, but the timing had been too tight. Nothing they could have done would have saved us.
Rami touched my arm and said, “Are you okay?”
I’d squeezed my eyes shut. “Yes,” I told ter. Remembering that humans usually want more than that from other humans, I pointed up to indicate the alarms and added, “I’ve got sensitive hearing.”
Rami nodded sympathetically. The others were worried, but there hadn’t been an announcement and they could see our route in the feed from the port, which was still giving us an on-time arrival.
The crew member tried to explain to Port Authority that there had been a catastrophic failure, the pilot bot was gone, and she didn’t know why the shuttle was following its normal route and not slamming into the surface of the moon. ShuttleSecSys tried to analyze ART and almost got itself deleted. I took over ShuttleSecSys, turned off the alarms, and deleted the entire trip out of its memory.
There were murmurs of relief from the passengers as the alarms stopped. I made a suggestion to ART, and it sent an error code to Port Authority, which assigned us a new priority and switched our landing site from the public dock to the emergency services dock. Since the killware had clearly been intended to destroy us en route, there might not be anybody waiting for us at our scheduled landing slot, but better safe than sorry.
The feed was giving us a visual of the port, which was inside a cavern, carved out of the side of a mountain, surrounded by the towers of a debris deflection grid. (An actual debris deflection system, as opposed to ART’s concealed rail gun or whatever it had.) The lights of multiple levels of the port installation gleamed in the darkness, and smaller shuttles whizzed out of our way as we curved down toward the Port Authority’s beacon.
Maro was watching me with narrowed eyes. When the notice of changed landing site came through the feed, she leaned forward and said, “You know what happened?”
Fortunately I remembered that nobody expected me to be compelled to answer all questions immediately. One of the benefits to being an augmented human security consultant rather than a construct SecUnit. I said, “We’ll talk about it when we’re off the shuttle,” and they all seemed satisfied.
*
ART landed us in the Port Authority’s slot. We left the shuttle crew member trying to explain to the emergency techs what had happened as they connected their diagnostic equipment. ART was already gone, deleting any evidence of its presence, and the ShuttleSecSys was confused, but at least still intact, unlike the poor pilot bot.
Emergency services personnel and bots milled around the small embarkation zone. I managed to herd my clients through and out onto the clear enclosed walkway to the main port before anyone thought to try to stop them. I had already downloaded a map from the public feed and was testing the robustness of the security system. The walkway had a view of the cavern, with the multiple levels of landing slots and a few shuttles coming and going. At the far end were the big haulers for the mining installations.
Security seemed to be intermittent and based on the level of paranoia of whatever contractor operated in the territory you were passing through. That could be both an advantage and an interesting challenge. The transit ring’s public info feed had warned that a lot of humans apparently carried weapons here, and there were no screening scans.
We came out into a central hub, which had a high clear dome allowing a view of the cavern arching overhead, with lights trained on it to show off the colorful mineral veins. I scanned to make sure nothing was recording us and stopped Rami. Te and the others looked up at me and I said, “The person you’re going to meet with just tried to kill you.”
Rami blinked, Maro went wide-eyed, and Tapan drew breath to argue. I said, “The shuttle was infected with killware. It destroyed the bot pilot. I was in contact with a friend who was able to use my augmented feed to download a new pilot module. That’s the only reason we didn’t crash.”