Incident: Malware Infection via Third-Party Ads on Drudge Report.

Published Date: 2010-03-09

Postmortem Analysis
Timeline 1. The software failure incident happened in March 2010. [1307]
System 1. Ad networks and ad delivery firms (such as Google's DoubleClick, YieldManager, and ValueClick's Fastclick network) failed to prevent malware from being distributed through ads [1307].
Responsible Organization 1. Third-party ad networks delivering malware through ads on websites, including Google's DoubleClick, YieldManager, and ValueClick's Fastclick network [1307].
Impacted Organization 1. Visitors to the Drudge Report website were impacted by the software failure incident as they encountered fake antivirus warnings and potential malware infections [1307]. 2. The Senate computers were also affected by the malware, with the Senate Committee on Environment and Public Works issuing an urgent email warning about viruses popping up throughout the Senate and advising staff to avoid certain websites, including Drudge Report and WhitePages.com [1307].
Software Causes 1. The software failure incident was caused by malware being delivered through ads served by third-party ad networks on the Drudge Report website [1307]. 2. The malware specifically included a variant of the Win32/Alureon Trojan horse that was dropped onto machines, leading to the installation of other malware [1307]. 3. The incident involved a malicious applet class file (jar-cache10802-tmp) that was detected as "Troj/JavaDl-G" by Sophos [1307].
Non-software Causes 1. The malware was likely coming from ads delivered by a third-party ad network and not the Drudge Report website itself [1307]. 2. The malware was distributed through ads served by ad networks such as Google's DoubleClick, YieldManager, and ValueClick's Fastclick network [1307]. 3. The malware incident was associated with pop-up ads appearing through websites like DrudgeReport.com and WhitePages.com [1307].
Impacts 1. Users visiting the Drudge Report were exposed to malware, specifically a fake antivirus warning, potentially leading to their systems being infected [1307]. 2. The incident caused concern and inconvenience for visitors who had to disinfect their devices after encountering the malware [1307]. 3. The reputation of the Drudge Report was negatively affected as it was accused by a Senate committee of spreading viruses, leading to a statement denying the allegations [1307]. 4. The incident prompted the Senate committee to issue an urgent email advising staff to avoid certain websites, including the Drudge Report, to prevent further virus infections on Senate computers [1307].
Preventions 1. Implementing stricter ad network security measures to prevent malicious ads from being served on the website [1307]. 2. Conducting regular security audits and checks on third-party ad networks to ensure they are not distributing malware [1307]. 3. Utilizing ad blockers or script blockers to prevent potentially harmful scripts from running on the website [1307]. 4. Educating users on safe browsing practices and warning them about the risks of clicking on unknown or suspicious ads [1307].
Fixes 1. Implement stricter ad network security measures to prevent malicious ads from being served on the website [1307]. 2. Conduct regular security audits and checks on the website to detect and remove any potential malware or malicious scripts [1307]. 3. Consider limiting or blocking JavaScript and Active Content, like Flash ads, on the website to reduce the risk of similar incidents occurring in the future [1307].
References 1. CNET reader who provided a screenshot and personal experience [1307] 2. Matt Drudge, owner of the Drudge Report denying the site's involvement in infecting visitors [1307] 3. IDG News Service reporting on the malware hidden in ads distributed by Google's DoubleClick, YieldManager, and ValueClick's Fastclick network [1307] 4. Senate Committee on Environment and Public Works accusing the Drudge Report of spreading malware [1307] 5. Sophos researcher Boris Lau providing information on the detection of the malicious file [1307] 6. Mary Landesman, a senior security researcher at ScanSafe, commenting on the issue of allowing JavaScript and Active Content on sites [1307]

Software Taxonomy of Faults

Category Option Rationale
Recurring one_organization, multiple_organization (a) The software failure incident of visitors getting malware from the Drudge Report has happened again within the same organization. This incident occurred for the second time in less than six months, indicating a recurring issue with malware being delivered through ads on the Drudge Report website [1307]. (b) The incident of malware being delivered through ads has also affected other organizations. The article mentions that prominent sites like The New York Times have been affected by malware hidden in ads, with the Drudge Report being one of the sites impacted by malware distributed by Google's DoubleClick, YieldManager, and ValueClick's Fastclick network [1307].
Phase (Design/Operation) design, operation (a) The software failure incident in the article is related to the design phase. The incident was caused by malware being delivered through ads served by third-party ad networks on websites like the Drudge Report. The malware was hidden in ads distributed by Google's DoubleClick, YieldManager, and ValueClick's Fastclick network, which dropped a variant of the Win32/Alureon Trojan horse onto machines, leading to the installation of other malware [1307]. (b) The software failure incident is also related to the operation phase. Users visiting the Drudge Report were affected by malware due to clicking on certain elements on the website, which triggered fake antivirus warnings and attempted infections on their systems. This aspect of the failure can be attributed to the operation or interaction of users with the website, leading to the malware infiltration [1307].
Boundary (Internal/External) within_system, outside_system (a) within_system: The software failure incident at the Drudge Report was likely caused by malware coming from ads delivered by a third-party ad network and not the site itself [1307]. The malware appeared as a fake antivirus warning that popped up on the website, indicating that the issue originated within the system due to the ads being served on the site. (b) outside_system: The incident also involved external factors contributing to the failure. Ad networks and ad delivery firms have been used to deliver malware to websites, affecting even prominent sites like The New York Times. In the case of the Drudge Report, the malware was hidden in ads distributed by Google's DoubleClick, YieldManager, and ValueClick's Fastclick network, indicating that the failure was influenced by factors originating from outside the system [1307].
Nature (Human/Non-human) non-human_actions, human_actions (a) The software failure incident in this case was primarily due to non-human actions, specifically the delivery of malware through ads served by third-party ad networks [1307]. (b) Human actions also played a role in this incident as users interacted with the website by clicking on certain elements that triggered the fake antivirus warnings, leading to potential malware infections [1307].
Dimension (Hardware/Software) software (a) The software failure incident reported in the articles was primarily due to contributing factors originating in software rather than hardware. The incident involved malware being delivered through ads on the Drudge Report website, potentially via third-party ad networks like Google's DoubleClick, YieldManager, and ValueClick's Fastclick network [1307]. The malware was designed to infect visitors' systems with malicious software, such as the Win32/Alureon Trojan horse, which could then install other malware on the affected machines. Additionally, the incident led to accusations from a Senate committee that the Drudge Report was responsible for viruses affecting Senate computers, further emphasizing the software-related nature of the failure [1307].
Objective (Malicious/Non-malicious) malicious (a) The software failure incident reported in Article 1307 is malicious in nature. The incident involved malware being distributed through ads delivered by a third-party ad network on the Drudge Report website. The malware appeared as a fake antivirus warning designed to scare people into paying for unnecessary software. The malware was identified as a variant of the Win32/Alureon Trojan horse, which could install other malware on affected machines. Additionally, the incident led to accusations against the Drudge Report by a Senate committee for spreading viruses throughout the Senate, prompting caution regarding visiting certain websites to prevent infections [1307].
Intent (Poor/Accidental Decisions) poor_decisions (a) The intent of the software failure incident related to poor_decisions: - The software failure incident on the Drudge Report website was primarily due to the delivery of malware through ads served by third-party ad networks [1307]. - The incident involved malware being distributed through ads from Google's DoubleClick, YieldManager, and ValueClick's Fastclick network, leading to the installation of malicious software on visitors' machines [1307]. - The incident highlighted the risks associated with allowing JavaScript and Active Content, like Flash ads, on websites, which can facilitate the spread of malware [1307]. (b) The intent of the software failure incident related to accidental_decisions: - The incident on the Drudge Report website where visitors encountered malware was not intentional on the part of the website itself but rather a result of ads containing malware served by third-party ad networks [1307]. - Visitors to the website inadvertently encountered the fake antivirus warnings and malware without any deliberate action on the part of the website [1307]. - The incident was more of an unintended consequence of allowing ads from external networks, rather than a deliberate decision to infect visitors with malware [1307].
Capability (Incompetence/Accidental) accidental (a) The software failure incident reported in the articles is more aligned with the accidental category rather than development incompetence. The incident involved malware being delivered through ads served by third-party ad networks on websites like the Drudge Report. The malware was not intentionally introduced by the development team but rather infiltrated through the ad delivery mechanism. This is evident from the fact that the Drudge Report denied being responsible for spreading malware and attributed the issue to ads distributed by networks like Google's DoubleClick and others [1307]. (b) The accidental nature of the software failure incident is further highlighted by the fact that the Drudge Report denied accusations of spreading malware and even the Senate committee mentioned that it was not exactly clear where the increase in viruses was coming from. The incident was not a result of intentional actions or incompetence on the part of the development team but rather an unintended consequence of malicious ads being served through the website [1307].
Duration temporary The software failure incident reported in Article 1307 can be categorized as a temporary failure. The incident involved visitors to the Drudge Report encountering malware, specifically fake antivirus warnings, which were likely delivered through third-party ads on the website. The malware was not directly caused by the website itself but rather by the ads served by external ad networks. This indicates that the failure was due to contributing factors introduced by certain circumstances (third-party ad networks) but not all circumstances (the website itself) [1307].
Behaviour value, other (a) crash: The incident described in the articles does not specifically mention a system crash where the system loses state and stops performing its intended functions. (b) omission: The incident does not directly relate to a failure caused by the system omitting to perform its intended functions at an instance(s). (c) timing: The incident does not involve a failure due to the system performing its intended functions correctly but too late or too early. (d) value: The software failure incident in the articles is related to the system performing its intended functions incorrectly. Users visiting the Drudge Report were exposed to malware through fake antivirus warnings, indicating a failure in the system's ability to protect users from malicious content [1307]. (e) byzantine: The incident does not exhibit a byzantine failure where the system behaves erroneously with inconsistent responses and interactions. (f) other: The behavior of the software failure incident can be categorized as a failure in cybersecurity measures. The system failed to prevent the delivery of malware through ads served by third-party networks, leading to users being exposed to fake antivirus warnings and potential malware infections [1307].

IoT System Layer

Layer Option Rationale
Perception None None
Communication None None
Application None None

Other Details

Category Option Rationale
Consequence property, non-human, theoretical_consequence, other (a) death: People lost their lives due to the software failure - There is no mention of any deaths resulting from the software failure incident reported in the articles. [1307] (b) harm: People were physically harmed due to the software failure - There is no mention of physical harm to individuals due to the software failure incident. [1307] (c) basic: People's access to food or shelter was impacted because of the software failure - There is no mention of people's access to food or shelter being impacted by the software failure incident. [1307] (d) property: People's material goods, money, or data was impacted due to the software failure - The software failure incident resulted in malware infecting visitors to the Drudge Report, potentially causing harm to their computer systems. This could impact people's data and potentially their money if they fell victim to scams related to the fake antivirus warnings. [1307] (e) delay: People had to postpone an activity due to the software failure - There is no mention of people having to postpone activities due to the software failure incident. [1307] (f) non-human: Non-human entities were impacted due to the software failure - The software failure incident affected the Drudge Report website and potentially infected visitors' computer systems with malware, which are non-human entities. [1307] (g) no_consequence: There were no real observed consequences of the software failure - The software failure incident did have consequences, such as malware infecting visitors' systems and potential impacts on data and security. [1307] (h) theoretical_consequence: There were potential consequences discussed of the software failure that did not occur - The articles discuss the potential consequences of malware infections through ads on websites like the Drudge Report, but these consequences did occur in this case. [1307] (i) other: Was there consequence(s) of the software failure not described in the (a to h) options? What is the other consequence(s)? - The software failure incident led to the spread of malware through ads on the Drudge Report website, potentially impacting the security and privacy of visitors' computer systems. This could result in data loss, financial harm, and compromised personal information. [1307]
Domain information, utilities, government (a) The failed system was related to the information industry as it involved the Drudge Report, a news aggregator website that provides information to its visitors [1307]. The incident involved malware being delivered through ads on the website, affecting visitors who accessed the site for news and information. (g) The incident also highlighted the issue of malware being distributed through online ads, impacting websites like The New York Times and the Drudge Report. This indicates a connection to the utilities industry, as websites rely on ad networks for revenue generation, and these networks inadvertently served malware to visitors [1307]. (l) The government sector was indirectly involved in the incident as a Senate committee accused the Drudge Report of spreading malware and issued an urgent email warning to hill staff to avoid the website. The Senate Help Desk mentioned DrudgeReport.com as a possible source of the malware affecting Senate computers, leading to caution regarding external websites [1307].

Sources

Back to List