Zero Day_ A Novel - Mark Russinovich [46]
BIOS, or the Basic Input/Output System, was the code programmed into the computer itself that started the computer and was responsible for reading the initial part of the operating system code from the first sector of the hard disk into memory and executing it. Modern computers had BIOS that could be “flashed” or reprogrammed with new instructions. Computer manufacturers sometimes made BIOS updates available that fixed bugs or improved the computer’s start-up performance.
But a virus that knew how to reprogram the BIOS could erase its contents, making the computer unbootable. Repairing such a computer was tedious and sometimes even impossible. Part of this virus was missing, he realized, either because it had already been deleted or because it wasn’t part of the variant installed on the law firm computer. Still, the sheer scope of this attack on a system with all the standard safeguards in place was astounding and underlined the enormity of the problem he faced.
Sue took a break, then returned, freshly scrubbed, munching on a candy bar. “Still at it, I see? Did you read about that ship in Japan?”
“No. What happened?”
“Its computer guidance and navigation systems failed. The ship slammed into Nagasaki, killing some people. I saw a video. The harbor is just filled with crude oil. There’s speculation it was a virus of some kind. What do you think?”
“It’s possible, but there’s no way of telling if it’s what we have here.”
“Okay, expert. What can you tell me?”
Matter-of-factly, Jeff walked her through what he’d uncovered.
“I’m confused,” she said, wadding up the candy-bar wrapper and pitching it toward the trash basket, missing by a foot. “Does it want to steal our financial information? Destroy our records? Or destroy our computers?”
“Good questions all. The answer is, I don’t know.” Jeff frowned. “I’ve seen no evidence of stealing information, but it both destroyed records and destroyed computers. It’s malicious and destructive but, from what I can see, it’s got no clear purpose.”
“What triggered it?” Sue looked every bit as confused as Jeff felt.
He shook his head. “I don’t know.”
“Can you find it in our backup? I’m under a great deal of pressure here. Clients have figured out we’ve got a problem and are threatening to leave.” Her face was creased with concern.
Jeff hesitated. “I should be able to locate what I’ve found here. But it’s like proving a negative. If I find it, then the backup records are tainted and of no use. But if I don’t find what I’ve got here, that doesn’t necessarily mean something else isn’t buried somewhere. I have no sense of how much I’ve discovered, and I’m almost certain to have missed something. I’m beginning to think there’re at least two viruses here. And I’m dealing with cloaking. A great deal could still be concealed from me.”
“But if you find nothing, that’s a good sign?”
Jeff understood Sue’s need to get this problem solved. Her job likely depended on it. He wanted to sound encouraging, but experience taught him otherwise. Cautiously he said, “Yes, as far as it goes. You could make a copy of the backup, I’ll check it for what I’ve learned. If it seems clean, or if I delete the evidence of what I’ve learned here, I might disable the viruses, allowing you to boot up and see what you’ve got.”
Sue brightened. “I like the sound of that.”
“Don’t get your hopes up too far. That’s going to eat up a lot of time with no guarantee. I’d feel better if I knew more.”
“If you crack this too late to do us any good, what’s the point?”
Jeff hesitated. “There may be clues in the calling cards the cracker’s left in his code. If we know more, maybe we can determine if the backup is secure before putting in all that time.”
Sue stared at him a moment, then seemed to reach a conclusion. “‘Super Freak.’ My guess is, that’s our key.”
18
MANHATTAN, NEW YORK CITY
CENTRAL PARK
WEDNESDAY, AUGUST 16
7:36 A.M.
Jeff placed his foot on the cement bench and methodically began his stretching