The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Short answer: A federal judge did set aside Timothy Lloyd’s computer-sabotage conviction in July 2000, but that was a new-trial order—not a final acquittal. On October 12, 2001, the U.S. Court of Appeals for the Third Circuit reversed the order, reinstated the conviction and directed sentencing. The Justice Department later reported a 41-month prison sentence.
The Omega Engineering sabotage
Timothy Allen Lloyd was Omega Engineering’s network administrator and network programmer for about 11 years. Prosecutors said he used that trusted insider position to place destructive software, described as a “time bomb,” on Omega’s central file server before his employment ended.
When Omega started its manufacturing network on July 31, 1996, approximately 1,200 design and production programs were deleted or purged. The files included specifications for molds and templates and programs used to operate manufacturing machinery. Contemporary reporting attributed more than $10 million in losses, about $2 million in reprogramming costs and roughly 80 layoffs to company or government testimony; the Third Circuit more cautiously described millions of dollars in lost sales and contracts. Those figures should be understood as reported estimates and testimony, not as a single independently audited total. Computerworld’s contemporaneous account provides the reported figures.
Why the alleged time bomb mattered
The government’s theory was that Lloyd planted code while he had legitimate access, left it dormant and arranged for it to trigger after his departure. That mechanism did not require the person who wrote the code to be physically present when the damage occurred. The defense disputed whether Lloyd could access Omega’s network after he was fired and argued that an accident or another employee could have caused the deletion.
Recommended Free Tools
#1 Best Overall
The 2000 trial and verdict
Lloyd was tried in the U.S. District Court for the District of New Jersey from April 19 through May 9, 2000. The prosecution presented the case as an insider computer-sabotage attack. The later appellate record identifies evidence the government relied on, including commands on Lloyd’s home hard drive that prosecutors described as identical to commands used to purge Omega’s network, evidence that the alleged time bomb had been tested repeatedly, and employment-related evidence offered to show motive and timing. These were prosecution evidence and arguments, not separate findings that each item independently established guilt. The Third Circuit opinion is available at United States v. Lloyd, 269 F.3d 228 (3d Cir. 2001).
The jury convicted Lloyd on the computer-sabotage count and acquitted him on a separate count involving transportation of allegedly stolen computer hardware and software equipment. Contemporary coverage described the prosecution as the first federal criminal computer-sabotage case, a characterization that should be attributed to that period’s reporting rather than treated as a universal historical finding.
Why the trial judge set the verdict aside
After the verdict, a juror told the court that she had seen a television report about the “Love Bug” computer virus during the trial or deliberations. She was unsure whether that outside information had affected her view of whether Lloyd could have remotely activated the alleged time bomb.
Judge William H. Walls investigated the disclosure and granted Lloyd’s motion for a new trial in July 2000. The legal issue was not whether watching television was itself misconduct. It was whether a juror received information outside the courtroom, whether that information was discussed or affected deliberations, and whether the risk of prejudice justified undoing the verdict.
Free tools Windows power users keep installed
One-click scans. No signup required.
What “set aside” meant
The order vacated the jury’s result temporarily and authorized another trial. It did not declare Lloyd innocent, enter a final acquittal or erase the government’s ability to appeal. The government argued that the television report was unrelated to the evidence and that the judge’s inquiry improperly intruded into the privacy of jury deliberations. The defense argued that the juror’s exposure to information about computer viruses and remote activation could have influenced the decision.
The Love Bug was not the malware alleged to have destroyed Omega’s files. It was outside information that the juror said might have affected her understanding of the technical possibility at issue.
Rank #3
The case’s decisive timeline
| Date | Event |
|---|---|
| July 31, 1996 | Omega’s manufacturing network suffered the deletion of design and production files. |
| January 1998 | Lloyd was indicted on computer-sabotage and transportation-of-stolen-goods counts. |
| April 19–May 9, 2000 | Federal jury trial in New Jersey. |
| May 2000 | Jury convicted Lloyd of computer sabotage and acquitted him on the second count. |
| July 2000 | Judge Walls granted a new trial after the juror disclosed exposure to television information. |
| April 19, 2001 | Third Circuit heard argument on the government’s appeal. |
| October 12, 2001 | Third Circuit reversed the new-trial order and reinstated the computer-sabotage conviction. |
| February 26, 2002 | Justice Department announced a 41-month sentence. |
What the Third Circuit decided
The government appealed the new-trial order to the Third Circuit. The appellate question was whether the juror’s exposure to the Love Bug report created a legally sufficient likelihood that the verdict had been improperly influenced and whether the district judge had properly exercised his authority.
On October 12, 2001, the court reversed the grant of a new trial, reinstated Lloyd’s conviction on count one and ordered the district court to proceed to sentencing. The court concluded that the outside information did not create a substantial likelihood of improper influence. It also observed that information about remote access could have supported the defense theory that someone else might have caused the sabotage, rather than necessarily strengthening the prosecution’s case.
The decision reviewed the trial judge’s new-trial ruling; it was not a second jury trial and did not independently retry whether Lloyd wrote or triggered the code. The appellate disposition is also reproduced at this case record.
The final sentence
The Justice Department reported that Lloyd was sentenced to 41 months in federal prison and ordered to surrender on May 1, 2002. The conviction therefore remained in force despite the 2000 order setting it aside. The sentencing announcement is archived at justice.gov.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.The legal and technical significance
A model insider-threat problem
The alleged attack illustrates why insider sabotage can be difficult to investigate. A trusted administrator may possess legitimate credentials, plant code before termination and rely on a delayed trigger. If backups are incomplete, a single event can destroy years of manufacturing data. Investigators may need to compare source code and commands, review access logs and system timing, establish who possessed relevant credentials, and distinguish a deliberate payload from an equipment failure.
Juror exposure and deliberation privacy
The case also shows the difference between a juror’s contact with outside information and proof that the information changed a verdict. Courts can examine possible external influence, but they must balance that inquiry against the rule protecting the confidentiality of jury deliberations. The Third Circuit’s ruling limited the trial court’s decision in this case; it did not establish that media exposure can never justify a new trial.
Best Value
The statute has changed
The charge was brought under the version of 18 U.S.C. § 1030(a)(5)(A) then in effect, which covered knowingly causing transmission of a program, information, code or command that intentionally caused unauthorized damage to a protected computer. Computer-crime statutes and their interpretation have evolved since the 2000–2001 prosecution, so the case is historical context rather than a complete guide to a present-day malware or insider-threat prosecution.
How to describe the outcome accurately
- Accurate: “The trial judge set aside the conviction and ordered a new trial in July 2000.”
- Accurate: “The Third Circuit reversed that order and reinstated the conviction on October 12, 2001.”
- Inaccurate: “Lloyd was acquitted,” “the conviction was permanently overturned” or “the Love Bug caused the Omega attack.”
- More precise than “hacking case”: “an alleged insider computer-sabotage prosecution involving malicious code.”
The complete story is therefore a temporary post-verdict setback followed by appellate restoration and a federal prison sentence—not a final clearing of the defendant.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
