Misplaced Pages

Flame (malware): Difference between revisions

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
Browse history interactively← Previous editNext edit →Content deleted Content addedVisualWikitext
Revision as of 02:02, 25 April 2013 editHydrargyrum (talk | contribs)Extended confirmed users43,643 editsmNo edit summary← Previous edit Revision as of 03:30, 2 July 2013 edit undoDl2000 (talk | contribs)Autopatrolled, Extended confirmed users, New page reviewers, Pending changes reviewers, Rollbackers821,587 edits correct format drift (MOS:DATEUNIFY)Next edit →
Line 130: Line 130:


== Origin == == Origin ==
On June 19, 2012, ] published an article claiming that Flame was jointly developed by the U.S. ], ] and Israel’s military at least five years prior. The project was said to be part of a classified effort code-named ], which was intended to collect intelligence in preparation for a cyber-sabotage campaign aimed at slowing Iranian nuclear efforts.<ref name="nakashima2012june">{{Cite web |url=http://www.washingtonpost.com/world/national-security/us-israel-developed-computer-virus-to-slow-iranian-nuclear-efforts-officials-say/2012/06/19/gJQA6xBPoV_story.html |title=U.S., Israel developed Flame computer virus to slow Iranian nuclear efforts, officials say |work=The Washington Post |date=June 19, 2012 |accessdate=June 20, 2012 |author=Nakashima, Ellen}}</ref> On 19 June 2012, ] published an article claiming that Flame was jointly developed by the U.S. ], ] and Israel’s military at least five years prior. The project was said to be part of a classified effort code-named ], which was intended to collect intelligence in preparation for a cyber-sabotage campaign aimed at slowing Iranian nuclear efforts.<ref name="nakashima2012june">{{Cite web |url=http://www.washingtonpost.com/world/national-security/us-israel-developed-computer-virus-to-slow-iranian-nuclear-efforts-officials-say/2012/06/19/gJQA6xBPoV_story.html |title=U.S., Israel developed Flame computer virus to slow Iranian nuclear efforts, officials say |work=The Washington Post |date=19 June 2012 |accessdate=20 June 2012 |author=Nakashima, Ellen}}</ref>


According to Kaspersky's chief malware expert, "the geography of the targets and also the complexity of the threat leaves no doubt about it being a nation-state that sponsored the research that went into it."<ref name=Lee/> Kaspersky initially said that the malware bears no resemblance to Stuxnet, although it may have been a parallel project commissioned by the same attackers.<ref name=T295>{{cite news |title=Flame Virus: Who is Behind the World's Most Complicated Espionage Software? |url=http://www.telegraph.co.uk/technology/news/9296827/Flame-virus-who-is-behind-the-worlds-most-complicated-espionage-software.html |newspaper=The Daily Telegraph |date=29 May 2012 |accessdate=29 May 2012 |archiveurl=http://www.webcitation.org/6834RDamf |archivedate=30 May 2012 |deadurl=no}}</ref> According to Kaspersky's chief malware expert, "the geography of the targets and also the complexity of the threat leaves no doubt about it being a nation-state that sponsored the research that went into it."<ref name=Lee/> Kaspersky initially said that the malware bears no resemblance to Stuxnet, although it may have been a parallel project commissioned by the same attackers.<ref name=T295>{{cite news |title=Flame Virus: Who is Behind the World's Most Complicated Espionage Software? |url=http://www.telegraph.co.uk/technology/news/9296827/Flame-virus-who-is-behind-the-worlds-most-complicated-espionage-software.html |newspaper=The Daily Telegraph |date=29 May 2012 |accessdate=29 May 2012 |archiveurl=http://www.webcitation.org/6834RDamf |archivedate=30 May 2012 |deadurl=no}}</ref>
After analysing the code further, Kaspersky later said that there is a strong relationship between Flame and Stuxnet; the early version of Stuxnet contained code to propagate via USB drives that is nearly identical to a Flame module that exploits the same ].<ref>{{cite web|url=http://www.kaspersky.com/about/news/virus/2012/Resource_207_Kaspersky_Lab_Research_Proves_that_Stuxnet_and_Flame_Developers_are_Connected|title=Resource 207: Kaspersky Lab Research Proves that Stuxnet and Flame Developers are Connected|date=11 June 2012|publisher=Kaspersky Lab}}</ref> After analysing the code further, Kaspersky later said that there is a strong relationship between Flame and Stuxnet; the early version of Stuxnet contained code to propagate via USB drives that is nearly identical to a Flame module that exploits the same ].<ref>{{cite web|url=http://www.kaspersky.com/about/news/virus/2012/Resource_207_Kaspersky_Lab_Research_Proves_that_Stuxnet_and_Flame_Developers_are_Connected|title=Resource 207: Kaspersky Lab Research Proves that Stuxnet and Flame Developers are Connected|date=11 June 2012|publisher=Kaspersky Lab}}</ref>


Iran's CERT described the malware's encryption as having "a special pattern which you only see coming from Israel".<ref>{{cite news |title=Iran Confirms Attack by Virus That Collects Information |first=Thomas |last=Erdbrink |url=http://www.nytimes.com/2012/05/30/world/middleeast/iran-confirms-cyber-attack-by-new-virus-called-flame.html?_r=1&hp |newspaper=The New York Times |date=29 May 2012 |accessdate=30 May 2012 |archiveurl=http://www.webcitation.org/6834RnDda |archivedate=30 May 2012 |deadurl=no}}</ref> '']'' reported that due to Flame's apparent targets—which included Iran, Syria, and the ]—Israel became "many commentators' prime suspect". Other commentators named ] and the U.S. as possible perpetrators.<ref name=T295/> ], a commentator critical of Israeli policies, stated that he had confirmed with a "senior Israeli source" that the malware was created by Israeli computer experts.<ref name=T295 /><ref>{{cite news |title=Flame: Israel’s New Contribution to Middle East Cyberwar |first=Richard |last=Silverstein |url=http://www.richardsilverstein.com/tikun_olam/2012/05/28/flame-israels-new-contribution-to-middle-east-cyberwar/ |work=] |date=28 May 2012 |accessdate=29 May 2012 |archiveurl=http://www.webcitation.org/6834SJAE8 |archivedate=30 May 2012 |deadurl=no}}</ref> '']'' wrote that Israel's Vice Prime Minister ] appeared to have hinted that his government was responsible,<ref name=T295 /> but an Israeli spokesperson later denied that this had been implied.<ref>{{cite web |url=http://www.washingtonpost.com/business/technology/flame-cyberweapon-written-using-gamer-code-report-says/2012/05/31/gJQAkIB83U_story.html |title=Flame cyberweapon written using gamer code, report says |author=Tsukayama, Hayley |date=31 May 2012 |work=The Washington Post |accessdate=31 May 2012}}</ref> Unnamed Israeli security officials suggested that the infected machines found in Israel may imply that the virus could be traced to the U.S. or other Western nations.<ref>{{cite news |url=http://techland.time.com/2012/05/31/iran-flame-virus-fight-began-with-oil-attack/ |title=Iran: ‘Flame’ Virus Fight Began with Oil Attack |agency=Associated Press |date=May 31, 2012 |work=] |accessdate=31 May 2012}}</ref> The U.S. has officially denied responsibility.<ref>{{cite news |url=http://www.bbc.co.uk/news/technology-18277555 |title=Flame: Israel rejects link to malware cyber-attack |publisher=BBC News |date=31 May 2012 |accessdate=3 June 2012}}</ref> Iran's CERT described the malware's encryption as having "a special pattern which you only see coming from Israel".<ref>{{cite news |title=Iran Confirms Attack by Virus That Collects Information |first=Thomas |last=Erdbrink |url=http://www.nytimes.com/2012/05/30/world/middleeast/iran-confirms-cyber-attack-by-new-virus-called-flame.html?_r=1&hp |newspaper=The New York Times |date=29 May 2012 |accessdate=30 May 2012 |archiveurl=http://www.webcitation.org/6834RnDda |archivedate=30 May 2012 |deadurl=no}}</ref> '']'' reported that due to Flame's apparent targets—which included Iran, Syria, and the ]—Israel became "many commentators' prime suspect". Other commentators named ] and the U.S. as possible perpetrators.<ref name=T295/> ], a commentator critical of Israeli policies, stated that he had confirmed with a "senior Israeli source" that the malware was created by Israeli computer experts.<ref name=T295 /><ref>{{cite news |title=Flame: Israel’s New Contribution to Middle East Cyberwar |first=Richard |last=Silverstein |url=http://www.richardsilverstein.com/tikun_olam/2012/05/28/flame-israels-new-contribution-to-middle-east-cyberwar/ |work=] |date=28 May 2012 |accessdate=29 May 2012 |archiveurl=http://www.webcitation.org/6834SJAE8 |archivedate=30 May 2012 |deadurl=no}}</ref> '']'' wrote that Israel's Vice Prime Minister ] appeared to have hinted that his government was responsible,<ref name=T295 /> but an Israeli spokesperson later denied that this had been implied.<ref>{{cite web |url=http://www.washingtonpost.com/business/technology/flame-cyberweapon-written-using-gamer-code-report-says/2012/05/31/gJQAkIB83U_story.html |title=Flame cyberweapon written using gamer code, report says |author=Tsukayama, Hayley |date=31 May 2012 |work=The Washington Post |accessdate=31 May 2012}}</ref> Unnamed Israeli security officials suggested that the infected machines found in Israel may imply that the virus could be traced to the U.S. or other Western nations.<ref>{{cite news |url=http://techland.time.com/2012/05/31/iran-flame-virus-fight-began-with-oil-attack/ |title=Iran: ‘Flame’ Virus Fight Began with Oil Attack |agency=Associated Press |date=31 May 2012 |work=] |accessdate=31 May 2012}}</ref> The U.S. has officially denied responsibility.<ref>{{cite news |url=http://www.bbc.co.uk/news/technology-18277555 |title=Flame: Israel rejects link to malware cyber-attack |publisher=BBC News |date=31 May 2012 |accessdate=3 June 2012}}</ref>


==See also== ==See also==

Revision as of 03:30, 2 July 2013

Not to be confused with Stoned (computer virus) § Flame/Stamford, or Olympic Torch (virus hoax).

Flame, also known as Flamer, sKyWIper, and Skywiper, is modular computer malware discovered in 2012 that attacks computers running the Microsoft Windows operating system. The program is being used for targeted cyber espionage in Middle Eastern countries.

Its discovery was announced on 28 May 2012 by MAHER Center of Iranian National Computer Emergency Response Team (CERT), Kaspersky Lab and CrySyS Lab of the Budapest University of Technology and Economics. The last of these stated in its report that it "is certainly the most sophisticated malware we encountered during our practice; arguably, it is the most complex malware ever found."

Flame can spread to other systems over a local network (LAN) or via USB stick. It can record audio, screenshots, keyboard activity and network traffic. The program also records Skype conversations and can turn infected computers into Bluetooth beacons which attempt to download contact information from nearby Bluetooth-enabled devices. This data, along with locally stored documents, is sent on to one of several command and control servers that are scattered around the world. The program then awaits further instructions from these servers.

According to estimates by Kaspersky in May 2012, Flame had initially infected approximately 1,000 machines, with victims including governmental organizations, educational institutions and private individuals. At that time 65% of the infections happened in Iran, Israel, Sudan, Syria, Lebanon, Saudi Arabia, and Egypt, with a "huge majority of targets" within Iran. Flame has also been reported in Europe and North America. Flame supports a "kill" command which wipes all traces of the malware from the computer. The initial infections of Flame stopped operating after its public exposure, and the "kill" command was sent.

History

Flame was identified in May 2012 by MAHER Center of Iranian National CERT, Kaspersky Lab and CrySyS Lab (Laboratory of Cryptography and System Security) of the Budapest University of Technology and Economics when Kaspersky Lab was asked by the United Nations International Telecommunication Union to investigate reports of a virus affecting Iranian Oil Ministry computers. As Kaspersky Lab investigated, they discovered an MD5 hash and filename that appeared only on customer machines from Middle Eastern nations. After discovering more pieces, researchers dubbed the program "Flame" after the name of one of its modules.

According to Kaspersky, Flame had been operating in the wild since at least February 2010. CrySyS Lab reported that the file name of the main component was observed as early as December 2007. However, its creation date could not be determined directly, as the creation dates for the malware's modules are falsely set to dates as early as 1994.

Computer experts consider it the cause of an attack in April 2012 that caused Iranian officials to disconnect their oil terminals from the Internet. At the time the Iranian Students News Agency referred to the malware that caused the attack as "Wiper", a name given to it by the malware's creator. However, Kaspersky Lab believes that Flame may be "a separate infection entirely" from the Wiper malware. Due to the size and complexity of the program—described as "twenty times" more complicated than Stuxnet—the Lab stated that a full analysis could require as long as ten years.

On 28 May, Iran's CERT announced that it had developed a detection program and a removal tool for Flame, and had been distributing these to "select organizations" for several weeks. After Flame's exposure in news media, Symantec reported on 8 June that some Flame command and control (C&C) computers had sent a "suicide" command to infected PCs to remove all traces of Flame.

According to estimates by Kaspersky in May 2012, initially Flame had infected approximately 1,000 machines, with victims including governmental organizations, educational institutions and private individuals. At that time the countries most affected were Iran, Israel, Sudan, Syria, Lebanon, Saudi Arabia, and Egypt.

Operation

Name Description
List of code names for various families of modules in Flame's source code and their possible purpose
Flame Modules that perform attack functions
Boost Information gathering modules
Flask A type of attack module
Jimmy A type of attack module
Munch Installation and propagation modules
Snack Local propagation modules
Spotter Scanning modules
Transport Replication modules
Euphoria File leaking modules
Headache Attack parameters or properties

Flame is an uncharacteristically large program for malware at 20 megabytes. It is written partly in the Lua scripting language with compiled C++ code linked in, and allows other attack modules to be loaded after initial infection. The malware uses five different encryption methods and an SQLite database to store structured information. The method used to inject code into various processes is stealthy, in that the malware modules do not appear in a listing of the modules loaded into a process and malware memory pages are protected with READ, WRITE and EXECUTE permissions that make them inaccessible by user-mode applications. The internal code has few similarities with other malware, but exploits two of the same security vulnerabilties used previously by Stuxnet to infect systems. The malware determines what antivirus software is installed, then customises its own behaviour (for example, by changing the filename extensions it uses) to reduce the probability of detection by that software. Additional indicators of compromise include mutex and registry activity, such as installation of a fake audio driver which the malware uses to maintain persistence on the compromised system.

Flame is not designed to deactivate automatically, but supports a "kill" function that makes it eliminate all traces of its files and operation from a system on receipt of a module from its controllers.

Flame was signed with a fraudulent certificate purportedly from the Microsoft Enforced Licensing Intermediate PCA certificate authority. The malware authors identified a Microsoft Terminal Server Licensing Service certificate that inadvertently was enabled for code signing and that still used the weak MD5 hashing algorithm, then produced a counterfeit copy of the certificate that they used to sign some components of the malware to make them appear to have originated from Microsoft. A successful collision attack against a certificate was previously demonstrated in 2008, but Flame implemented a new variation of the chosen-prefix collision attack.

Property Value
Compromised Microsoft certificate using the weak MD5 algorithm, and the unintended code-signing usage.
Version V3
Serial number 3a ab 11 de e5 2f 1b 19 d0 56
Signature algorithm md5RSA
Signature hash algorithm md5
Issuer CN = Microsoft Root Authority,OU = Microsoft Corporation,OU = Copyright (c) 1997 Microsoft Corp.
Valid from Thursday,10 December 2009 11:55:35 AM
Valid to Sunday,23 October 2016 6:00:00 PM
Subject CN = Microsoft Enforced Licensing Intermediate PCA,OU = Copyright (c) 1999 Microsoft Corp.,O = Microsoft Corporation,L = Redmond,S = Washington,C = US
Public key 30 82 01 0a 02 82 01 01 00 fa c9 3f 35 cb b4 42 4c 19 a8 98 e2 f4 e6 ca c5 b2 ff e9 29 25 63 9a b7 eb b9 28 2b a7 58 1f 05 df d8 f8 cf 4a f1 92 47 15 c0 b5 e0 42 32 37 82 99 d6 4b 3a 5a d6 7a 25 2a 9b 13 8f 75 75 cb 9e 52 c6 65 ab 6a 0a b5 7f 7f 20 69 a4 59 04 2c b7 b5 eb 7f 2c 0d 82 a8 3b 10 d1 7f a3 4e 39 e0 28 2c 39 f3 78 d4 84 77 36 ba 68 0f e8 5d e5 52 e1 6c e2 78 d6 d7 c6 b9 dc 7b 08 44 ad 7d 72 ee 4a f4 d6 5a a8 59 63 f4 a0 ee f3 28 55 7d 2b 78 68 2e 79 b6 1d e6 af 69 8a 09 ba 39 88 b4 92 65 0d 12 17 09 ea 2a a4 b8 4a 8e 40 f3 74 de a4 74 e5 08 5a 25 cc 80 7a 76 2e ee ff 21 4e b0 65 6c 64 50 5c ad 8f c6 59 9b 07 3e 05 f8 e5 92 cb d9 56 1d 30 0f 72 f0 ac a8 5d 43 41 ff c9 fd 5e fa 81 cc 3b dc f0 fd 56 4c 21 7c 7f 5e ed 73 30 3a 3f f2 e8 93 8b d5 f3 cd 0e 27 14 49 67 94 ce b9 25 02 03 01 00 01
Enhance key usage Code Signing (1.3.6.1.5.5.7.3.3)
Key Pack Licenses (1.3.6.1.4.1.311.10.6.1)
License Server Verification (1.3.6.1.4.1.311.10.6.2)
Authority identifier Certificate Issuer: CN=Microsoft Root Authority, OU=Microsoft Corporation, OU=Copyright (c) 1997 Microsoft Corp.| Certificate SerialNumber=00 c1 00 8b 3c 3c 88 11 d1 3e f6 63 ec df 40
Subject key identifier 6a 97 e0 c8 9f f4 49 b4 89 24 b3 e3 d1 a8 22 86 aa d4 94 43
Key usage Digital Signature
Certificate Signing
Off-line CRL Signing
CRL Signing (86)
Basic constraints Subject Type=CA
Path Length Constraint=None
Thumbprint algorithm sha1
Thumbprint 2a 83 e9 02 05 91 a5 5f c6 dd ad 3f b1 02 79 4c 52 b2 4e 70

Deployment

Like the previously known cyber weapons Stuxnet and Duqu, it is employed in a targeted manner and can evade current security software through rootkit functionality. Once a system is infected, Flame can spread to other systems over a local network or via USB stick. It can record audio, screenshots, keyboard activity and network traffic. The program also records Skype conversations and can turn infected computers into Bluetooth beacons which attempt to download contact information from nearby Bluetooth enabled devices. This data, along with locally stored documents, is sent on to one of several command and control servers that are scattered around the world. The program then awaits further instructions from these servers.

Unlike Stuxnet, which was designed to sabotage an industrial process, Flame appears to have been written purely for espionage. It does not appear to target a particular industry, but rather is "a complete attack toolkit designed for general cyber-espionage purposes".

Using a technique known as sinkholing, Kaspersky demonstrated that "a huge majority of targets" were within Iran, with the attackers particularly seeking AutoCAD drawings, PDFs, and text files. Computing experts said that the program appeared to be gathering technical diagrams for intelligence purposes.

A network of 80 servers across Asia, Europe and North America has been used to access the infected machines remotely.

Origin

On 19 June 2012, The Washington Post published an article claiming that Flame was jointly developed by the U.S. National Security Agency, CIA and Israel’s military at least five years prior. The project was said to be part of a classified effort code-named Olympic Games, which was intended to collect intelligence in preparation for a cyber-sabotage campaign aimed at slowing Iranian nuclear efforts.

According to Kaspersky's chief malware expert, "the geography of the targets and also the complexity of the threat leaves no doubt about it being a nation-state that sponsored the research that went into it." Kaspersky initially said that the malware bears no resemblance to Stuxnet, although it may have been a parallel project commissioned by the same attackers. After analysing the code further, Kaspersky later said that there is a strong relationship between Flame and Stuxnet; the early version of Stuxnet contained code to propagate via USB drives that is nearly identical to a Flame module that exploits the same zero-day vulnerability.

Iran's CERT described the malware's encryption as having "a special pattern which you only see coming from Israel". The Daily Telegraph reported that due to Flame's apparent targets—which included Iran, Syria, and the West Bank—Israel became "many commentators' prime suspect". Other commentators named China and the U.S. as possible perpetrators. Richard Silverstein, a commentator critical of Israeli policies, stated that he had confirmed with a "senior Israeli source" that the malware was created by Israeli computer experts. The Jerusalem Post wrote that Israel's Vice Prime Minister Moshe Ya'alon appeared to have hinted that his government was responsible, but an Israeli spokesperson later denied that this had been implied. Unnamed Israeli security officials suggested that the infected machines found in Israel may imply that the virus could be traced to the U.S. or other Western nations. The U.S. has officially denied responsibility.

See also

External links

Notes

  1. "Flame" is one of the strings found in the code, a common name for attacks, most likely by exploits
  2. The name "sKyWIper" is derived from the letters "KWI" which are used as a partial filename by the malware
  3. MS10-061 and MS10-046

References

  1. ^ "sKyWIper: A Complex Malware for Targeted Attacks". Budapest University of Technology and Economics. 28 May 2012. Archived from the original (PDF) on 30 May 2012. Retrieved 29 May 2012. {{cite web}}: Unknown parameter |deadurl= ignored (|url-status= suggested) (help)
  2. "Flamer: Highly Sophisticated and Discreet Threat Targets the Middle East". Symantec. Archived from the original on 30 May 2012. Retrieved 30 May 2012. {{cite web}}: Unknown parameter |deadurl= ignored (|url-status= suggested) (help)
  3. ^ Lee, Dave (28 May 2012). "Flame: Massive Cyber-Attack Discovered, Researchers Say". BBC News. Archived from the original on 30 May 2012. Retrieved 29 May 2012. {{cite news}}: Unknown parameter |deadurl= ignored (|url-status= suggested) (help)
  4. McElroy, Damien; Williams, Christopher (28 May 2012). "Flame: World's Most Complex Computer Virus Exposed". The Daily Telegraph. Archived from the original on 30 May 2012. Retrieved 29 May 2012. {{cite news}}: Unknown parameter |deadurl= ignored (|url-status= suggested) (help)
  5. ^ "Identification of a New Targeted Cyber-Attack". Iran Computer Emergency Response Team. 28 May 2012. Archived from the original on 30 May 2012. Retrieved 29 May 2012. {{cite web}}: Unknown parameter |deadurl= ignored (|url-status= suggested) (help)
  6. ^ Gostev, Alexander (28 May 2012). "The Flame: Questions and Answers". Securelist. Archived from the original on 30 May 2012. Retrieved 29 May 2012. {{cite web}}: Unknown parameter |deadurl= ignored (|url-status= suggested) (help)
  7. ^ Zetter, Kim (28 May 2012). "Meet 'Flame,' The Massive Spy Malware Infiltrating Iranian Computers". Wired. Archived from the original on 30 May 2012. Retrieved 29 May 2012. {{cite news}}: Unknown parameter |deadurl= ignored (|url-status= suggested) (help)
  8. ^ Lee, Dave (4 June 2012). "Flame: Attackers 'sought confidential Iran data'". BBC News. Retrieved 4 June 2012.
  9. Murphy, Samantha (5 June 2012). "Meet Flame, the Nastiest Computer Malware Yet". Mashable.com. Retrieved 8 June 2012.
  10. ^ "Flame malware makers send 'suicide' code". BBC News. 8 June 2012. Retrieved 8 June 2012.
  11. Hopkins, Nick (28 May 2012). "Computer Worm That Hit Iran Oil Terminals 'Is Most Complex Yet'". The Guardian. Archived from the original on 30 May 2012. Retrieved 29 May 2012. {{cite news}}: Unknown parameter |deadurl= ignored (|url-status= suggested) (help)
  12. Erdbrink, Thomas (23 April 2012). "Facing Cyberattack, Iranian Officials Disconnect Some Oil Terminals From Internet". The New York Times. Archived from the original on 30 May 2012. Retrieved 29 May 2012. {{cite news}}: Unknown parameter |deadurl= ignored (|url-status= suggested) (help)
  13. ^ Kindlund, Darien (30 May 2012). "Flamer/sKyWIper Malware: Analysis". FireEye. Archived from the original on 31 May 2012. Retrieved 31 May 2012. {{cite web}}: Unknown parameter |deadurl= ignored (|url-status= suggested) (help)
  14. ^ "Microsoft releases Security Advisory 2718704". Microsoft. 3 June 2012. Retrieved 4 June 2012.
  15. Sotirov, Alexander; Stevens, Marc; Appelbaum, Jacob; Lenstra, Arjen; Molnar, David; Osvik, Dag Arne; de Weger, Benne (30 December 2008). "MD5 Considered Harmful Today". Retrieved 4 June 2011.{{cite web}}: CS1 maint: multiple names: authors list (link)
  16. Stevens, Marc (7 June 2012). "CWI Cryptanalist Discovers New Cryptographic Attack Variant in Flame Spy Malware". Centrum Wiskunde & Informatica. Retrieved 9 June 2012.
  17. Cohen, Reuven (28 May 2012). "New Massive Cyber-Attack an 'Industrial Vacuum Cleaner for Sensitive Information'". Forbes. Archived from the original on 30 May 2012. Retrieved 29 May 2012. {{cite news}}: Unknown parameter |deadurl= ignored (|url-status= suggested) (help)
  18. Albanesius, Chloe (28 May 2012). "Massive 'Flame' Malware Stealing Data Across Middle East". PC Magazine. Archived from the original on 30 May 2012. Retrieved 29 May 2012. {{cite news}}: Unknown parameter |deadurl= ignored (|url-status= suggested) (help)
  19. "Flame virus: Five facts to know". The Times of India. Reuters. 29 May 2012. Archived from the original on 30 May 2012. Retrieved 30 May 2012. {{cite news}}: Unknown parameter |deadurl= ignored (|url-status= suggested) (help)
  20. Nakashima, Ellen (19 June 2012). "U.S., Israel developed Flame computer virus to slow Iranian nuclear efforts, officials say". The Washington Post. Retrieved 20 June 2012.
  21. ^ "Flame Virus: Who is Behind the World's Most Complicated Espionage Software?". The Daily Telegraph. 29 May 2012. Archived from the original on 30 May 2012. Retrieved 29 May 2012. {{cite news}}: Unknown parameter |deadurl= ignored (|url-status= suggested) (help)
  22. "Resource 207: Kaspersky Lab Research Proves that Stuxnet and Flame Developers are Connected". Kaspersky Lab. 11 June 2012.
  23. Erdbrink, Thomas (29 May 2012). "Iran Confirms Attack by Virus That Collects Information". The New York Times. Archived from the original on 30 May 2012. Retrieved 30 May 2012. {{cite news}}: Unknown parameter |deadurl= ignored (|url-status= suggested) (help)
  24. Silverstein, Richard (28 May 2012). "Flame: Israel's New Contribution to Middle East Cyberwar". Tikun Olam. Archived from the original on 30 May 2012. Retrieved 29 May 2012. {{cite news}}: Unknown parameter |deadurl= ignored (|url-status= suggested) (help)
  25. Tsukayama, Hayley (31 May 2012). "Flame cyberweapon written using gamer code, report says". The Washington Post. Retrieved 31 May 2012.
  26. "Iran: 'Flame' Virus Fight Began with Oil Attack". Time. Associated Press. 31 May 2012. Retrieved 31 May 2012.
  27. "Flame: Israel rejects link to malware cyber-attack". BBC News. 31 May 2012. Retrieved 3 June 2012.
Hacking in the 2010s
← 2000s Timeline 2020s →
Major incidents
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
Hacktivism
Advanced
persistent threats
Individuals
Major vulnerabilities
publicly disclosed
Malware
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
Malware topics
Infectious malware
Concealment
Malware for profit
By operating system
Protection
Countermeasures

Categories: