Free In Death 18 - Divided in Death by authors_sort

passcode his computers, lock the drawer in an already secured area. He—”
    “I said the unit wasn’t blocked.” He patted her knee and rose, resisting—though it was difficult—palming a couple of the goodies just for the fun of it. “It’s fried.”
    “What the hell do you mean ‘fried’?”
    “Fried, toasted, whacked, zapped, dead.”
    “I know what fried means, I meant—damn it.” She sprang up, kicked the drawer closed. “When? Can you tell when? When and how?”
    “I imagine so, given the right tools and a bit of time, but I can tell you this much just from this cursory exam: It was professionally and expertly fried.”
    “What does that mean?”
    “Simply, the main board was destroyed so that all data was corrupted. My first guess would be a very insidious worm, with specificity for this purpose. Likely contained on a disc, inserted into the drive, used to infect, then removed when the task was complete.”
    “Can you tell if data was removed first?”
    “Trickier, but we can certainly try.”
    “How about retrieving anything? Digging in and finding what data was on there, uncorrupting?”
    “Trickier yet.”
    “It’s there. It’s always there, no matter what. I know that from Feeney.”
    “Well, that may not be quite true. Eve, there’s a group of techno-terrorists. They call themselves the Doomsday Group.”
    “I know who they are. Glorified hackers, like to infiltrate systems, upload what they can, screw with the data. They’ve got some good, twisted brains and plenty of financial backing.”
    “A bit more than glorified,” he corrected. “They’re responsible for downing a number of private shuttles by skewing data in air-traffic control. They helped themselves to several works of art, and deliberately damaged others at the Louvre by shutting down their security. They killed twenty-six employees of a research lab in Prague by sabotaging their system, shutting down the air supply, and sealing all doors.”
    “I said they were twisted. I know they’re dangerous. What does it have to do with a fried unit in a dead man’s art studio?”
    “They’ve been working on a worm of just this nature for the past few years. Potent, portable. Its design is not simply to corrupt data or hijack it, but to eliminate it, and on a large scale. To network, to proliferate.”
    “How large a scale?”
    “Theoretically, a disc could be slipped into a drive on a networking unit—even a network with fail-safes and blocks, with virus detectors and bug zappers—and download the entire data bank from that network, then corrupt the units. An office, a building, a corporation. A country.”
    “Not possible. Even midlevel security detects intrusive viruses and bugs and shuts down before infection. You can’t download without detection from CompuGuard. Home units like this, okay, you might get it off and down before the security dropped on you. Small operations networks, maybe. Maybe even with the CompuGuard shields in place. But nothing over that.”
    “Theoretically,” he repeated. “And this faction is reputed to have some particularly brilliant minds on board this project. The intel indicates the worm is near completion, and could work.”
    “How do you know about this?”
    “I have connections.” He gave an easy shrug. “And it happens Roarke Industries is under government contract, a Code Red contract, to develop and create an exterminator program and shield against this potential threat.”
    She sat on the side of the bed. “You’re working for the government. Ours?”
    “Well, if by that you mean the U.S., yes. Actually, it’s also a conglomeration sort of thing. The U.S., the Euro Community, Russia, a few other concerned areas. Roarke Industries Securecomp arm has the contract, and R and D is working on it.”
    “And Reva Ewing works in R and D, for Roarke Industries Securecomp arm.”
    “She does. Eve, I said Code Red, that’s highest clearance. This isn’t something she’d