by Mike Masnick
Mon, Aug 23rd 2010 8:22am
As someone who flies all too frequently, I'd be lying if I said I wasn't a bit spooked by a report that the Spanair flight 5022 crash from two years ago may have been caused -- at least in part -- by malware on a computer that failed to detect three technical problems. Apparently, the computer which monitored those things got some sort of trojan horse, and may have failed to set off the necessary alarms because of this. As for how the computer got infected... it sounds like investigators still are not sure, but someone sticking in an infected USB stick or some other remote network connection seem like the most likely culprit. Of course, the reports seem woefully lacking in details. It's unclear how a trojan would block some software from alerting the crew that there was a problem with the aircraft. Honestly, the report seems to raise a lot more questions than it answers, and if it's actually true, it makes me wonder why we're relying on software that can be disabled via some random malware to watch for life-and-death safety issues on airplanes...
If you liked this post, you may also be interested in...
- Judge: FBI's NIT Warrant Invalid And IP Addresses Do Have An Expectation Of Privacy, But No Suppression Granted
- Ransomware Attack Left DC Police Surveillance Blind Shortly Before The Innauguration
- Malware Purveyor Serving Up Ransomware Via Bogus ICANN Blacklist Removal Emails
- Judge Says FBI's Child Porn Investigation Bordered On 'Outrageous,' Lets It Keep All Of Its Evidence
- FBI's NIT Hit 8,000 Computers In 120 Countries... As Did The Child Porn It Was Redistributing