<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>Comments on: Flame virus sensationalism</title>
	<atom:link href="http://www.epanorama.net/blog/2012/06/01/flame-virus-sensationalism/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.epanorama.net/blog/2012/06/01/flame-virus-sensationalism/</link>
	<description>All about electronics and circuit design</description>
	<lastBuildDate>Wed, 15 Apr 2026 22:25:15 +0000</lastBuildDate>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.9.14</generator>
	<item>
		<title>By: nice</title>
		<link>https://www.epanorama.net/blog/2012/06/01/flame-virus-sensationalism/comment-page-1/#comment-23840</link>
		<dc:creator><![CDATA[nice]]></dc:creator>
		<pubDate>Wed, 02 Oct 2013 18:58:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.epanorama.net/blog/?p=11688#comment-23840</guid>
		<description><![CDATA[magnificent issues altogether, you simply received a new reader.
What would you recommend about your put up that you simply made some days ago?
Any positive?]]></description>
		<content:encoded><![CDATA[<p>magnificent issues altogether, you simply received a new reader.<br />
What would you recommend about your put up that you simply made some days ago?<br />
Any positive?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karen Millen</title>
		<link>https://www.epanorama.net/blog/2012/06/01/flame-virus-sensationalism/comment-page-1/#comment-23839</link>
		<dc:creator><![CDATA[Karen Millen]]></dc:creator>
		<pubDate>Sun, 01 Sep 2013 17:09:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.epanorama.net/blog/?p=11688#comment-23839</guid>
		<description><![CDATA[You should not enhance and even preserve energy prior to you understand is actually. ]]></description>
		<content:encoded><![CDATA[<p>You should not enhance and even preserve energy prior to you understand is actually. </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2012/06/01/flame-virus-sensationalism/comment-page-1/#comment-23838</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Tue, 16 Oct 2012 07:18:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.epanorama.net/blog/?p=11688#comment-23838</guid>
		<description><![CDATA[Kaspersky Lab researchers have discovered a new malicious program &quot;MiniFlame&quot;/&quot;SPE&quot;, which was probably part of cyber operation against Iran.  Code suggests that it is built on the same platform as its &quot;big brother&quot; and was designed to carry out continuous monitoring.

&quot;We can assume that this program was part of the same operation as the Flame and Gauss, and that the operation was carried out in several waves,&quot; Kaspersky told.

In the first wave as many computers as possible was infected. They were used to collect information to attack important targets.

Source: http://www.tietoviikko.fi/kaikki_uutiset/tietoturvayritys+loysi+vakoiluohjelma+flamen+pikkuveljen/a847541?s=r&amp;wtm=tietoviikko/-16102012&amp;]]></description>
		<content:encoded><![CDATA[<p>Kaspersky Lab researchers have discovered a new malicious program &#8220;MiniFlame&#8221;/&#8221;SPE&#8221;, which was probably part of cyber operation against Iran.  Code suggests that it is built on the same platform as its &#8220;big brother&#8221; and was designed to carry out continuous monitoring.</p>
<p>&#8220;We can assume that this program was part of the same operation as the Flame and Gauss, and that the operation was carried out in several waves,&#8221; Kaspersky told.</p>
<p>In the first wave as many computers as possible was infected. They were used to collect information to attack important targets.</p>
<p>Source: <a href="http://www.tietoviikko.fi/kaikki_uutiset/tietoturvayritys+loysi+vakoiluohjelma+flamen+pikkuveljen/a847541?s=r&#038;wtm=tietoviikko/-16102012&#038;amp" rel="nofollow">http://www.tietoviikko.fi/kaikki_uutiset/tietoturvayritys+loysi+vakoiluohjelma+flamen+pikkuveljen/a847541?s=r&#038;wtm=tietoviikko/-16102012&#038;amp</a>;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2012/06/01/flame-virus-sensationalism/comment-page-1/#comment-23837</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Tue, 18 Sep 2012 07:33:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.epanorama.net/blog/?p=11688#comment-23837</guid>
		<description><![CDATA[Kaspersky finds three Flame-related malware threats
Firm warns at least one is still operating in the wild
http://www.theinquirer.net/inquirer/news/2206078/kaspersky-finds-three-flame-related-malware-threats

SECURITY OUTFIT Kaspersky Lab has discovered three Flame spyware related malware threats that it said use &quot;sophisticated encryption methods&quot;.

&quot;Sophisticated encryption methods were utilised so that no one, but the attackers, could obtain the data uploaded from infected machines,&quot; the firm&#039;s statement read.

Following the discovery of the three new related programs, Kaspersky&#039;s chief malware expert Vitaly Kamluk told The INQUIRER that Flame is not the only one in this big family.

&quot;There are others and they aren&#039;t just other known malwares such as Stuxnet, Gauss or Duqu,&quot; he said. &quot;They stay in the shadows and no one has published anything about them yet. Others were probably used for different campaigns.&quot;

Kamluk added that it is &quot;very possible&quot; there are more than the three listed in Kaspersky&#039;s report.]]></description>
		<content:encoded><![CDATA[<p>Kaspersky finds three Flame-related malware threats<br />
Firm warns at least one is still operating in the wild<br />
<a href="http://www.theinquirer.net/inquirer/news/2206078/kaspersky-finds-three-flame-related-malware-threats" rel="nofollow">http://www.theinquirer.net/inquirer/news/2206078/kaspersky-finds-three-flame-related-malware-threats</a></p>
<p>SECURITY OUTFIT Kaspersky Lab has discovered three Flame spyware related malware threats that it said use &#8220;sophisticated encryption methods&#8221;.</p>
<p>&#8220;Sophisticated encryption methods were utilised so that no one, but the attackers, could obtain the data uploaded from infected machines,&#8221; the firm&#8217;s statement read.</p>
<p>Following the discovery of the three new related programs, Kaspersky&#8217;s chief malware expert Vitaly Kamluk told The INQUIRER that Flame is not the only one in this big family.</p>
<p>&#8220;There are others and they aren&#8217;t just other known malwares such as Stuxnet, Gauss or Duqu,&#8221; he said. &#8220;They stay in the shadows and no one has published anything about them yet. Others were probably used for different campaigns.&#8221;</p>
<p>Kamluk added that it is &#8220;very possible&#8221; there are more than the three listed in Kaspersky&#8217;s report.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomi</title>
		<link>https://www.epanorama.net/blog/2012/06/01/flame-virus-sensationalism/comment-page-1/#comment-23836</link>
		<dc:creator><![CDATA[Tomi]]></dc:creator>
		<pubDate>Mon, 17 Sep 2012 17:56:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.epanorama.net/blog/?p=11688#comment-23836</guid>
		<description><![CDATA[Flame espionage weapon linked to MORE mystery malware
Command systems weren&#039;t just directing data-raiding worm
http://www.theregister.co.uk/2012/09/17/flame_analysis/

Forensic analysis of two command-and-control servers behind the Flame espionage worm has revealed that the infamous malware has been around for longer than suspected

Flame was built by a group of at least four developers as early at December 2006, according to freshly published joint research by Symantec, Kaspersky Lab and the United Nations&#039; International Telecommunication Union.

Over the last six years, the team behind Flame used the command servers to communicate with the malware on the compromised machines and order them to launch attacks

C&amp;C servers were disguised to look like a common content management system

&quot;They [the command servers] are all dead,&quot;

There&#039;s no evidence to suggest that Flame&#039;s command servers were used to control other known cyber-weapons - such as Stuxnet or Gauss - but they were used to operate a mystery malware strain, codenamed &quot;SPE&quot; by its authors.

Unnamed US officials told the Washington Post that Flame was created as part of the same covert programme that spawned cyber-weapon weapon Stuxnet, codenamed Olympic Games. Flame was described as a reconnaissance tool that was used to map networks associated with Iran&#039;s controversial nuclear enrichment programme. This information was used by Stuxnet to target its nuke centrifuge cyber-sabotage mission.]]></description>
		<content:encoded><![CDATA[<p>Flame espionage weapon linked to MORE mystery malware<br />
Command systems weren&#8217;t just directing data-raiding worm<br />
<a href="http://www.theregister.co.uk/2012/09/17/flame_analysis/" rel="nofollow">http://www.theregister.co.uk/2012/09/17/flame_analysis/</a></p>
<p>Forensic analysis of two command-and-control servers behind the Flame espionage worm has revealed that the infamous malware has been around for longer than suspected</p>
<p>Flame was built by a group of at least four developers as early at December 2006, according to freshly published joint research by Symantec, Kaspersky Lab and the United Nations&#8217; International Telecommunication Union.</p>
<p>Over the last six years, the team behind Flame used the command servers to communicate with the malware on the compromised machines and order them to launch attacks</p>
<p>C&amp;C servers were disguised to look like a common content management system</p>
<p>&#8220;They [the command servers] are all dead,&#8221;</p>
<p>There&#8217;s no evidence to suggest that Flame&#8217;s command servers were used to control other known cyber-weapons &#8211; such as Stuxnet or Gauss &#8211; but they were used to operate a mystery malware strain, codenamed &#8220;SPE&#8221; by its authors.</p>
<p>Unnamed US officials told the Washington Post that Flame was created as part of the same covert programme that spawned cyber-weapon weapon Stuxnet, codenamed Olympic Games. Flame was described as a reconnaissance tool that was used to map networks associated with Iran&#8217;s controversial nuclear enrichment programme. This information was used by Stuxnet to target its nuke centrifuge cyber-sabotage mission.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The traditional antivirus era is over? &#171; Tomi Engdahl&#8217;s ePanorama blog</title>
		<link>https://www.epanorama.net/blog/2012/06/01/flame-virus-sensationalism/comment-page-1/#comment-23835</link>
		<dc:creator><![CDATA[The traditional antivirus era is over? &#171; Tomi Engdahl&#8217;s ePanorama blog]]></dc:creator>
		<pubDate>Thu, 13 Sep 2012 05:37:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.epanorama.net/blog/?p=11688#comment-23835</guid>
		<description><![CDATA[[...] points out that conventional security software is powerless against sophisticated attacks like Flame, but alternative approaches are only just getting started. &#8220;There&#8217;s nothing you can [...] ]]></description>
		<content:encoded><![CDATA[<p>[...] points out that conventional security software is powerless against sophisticated attacks like Flame, but alternative approaches are only just getting started. &#8220;There&#8217;s nothing you can [...] </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2012/06/01/flame-virus-sensationalism/comment-page-1/#comment-23834</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Mon, 27 Aug 2012 09:59:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.epanorama.net/blog/?p=11688#comment-23834</guid>
		<description><![CDATA[Security biz U-turns on Gauss, Flame joint cyberspy hub claim
http://www.theregister.co.uk/2012/08/24/fireeye_gauss_reverse_ferret/

Computer security biz FireEye has withdrawn claims that the Gauss and Flame super-viruses may be linked.

This is after it emerged that what FireEye had thought was a shared command-and-control server, used to send instructions to PCs compromised by the malware, was actually a &quot;sinkhole&quot; maintained by rival researchers at Kaspersky Lab.

FireEye had noticed communications from both virus strains were heading to the same IP address – but this was a system set up by the Russian lab, which had asked DNS providers to redirect data sent from the two software nasties so as to examine their network traffic.

&quot;In light of new information shared by the security community, we now know that our original conclusions were incorrect and we cannot associate these two malware families based solely upon these common CnC coordinates,&quot; FireEye researchers conceded in an updated blog post.]]></description>
		<content:encoded><![CDATA[<p>Security biz U-turns on Gauss, Flame joint cyberspy hub claim<br />
<a href="http://www.theregister.co.uk/2012/08/24/fireeye_gauss_reverse_ferret/" rel="nofollow">http://www.theregister.co.uk/2012/08/24/fireeye_gauss_reverse_ferret/</a></p>
<p>Computer security biz FireEye has withdrawn claims that the Gauss and Flame super-viruses may be linked.</p>
<p>This is after it emerged that what FireEye had thought was a shared command-and-control server, used to send instructions to PCs compromised by the malware, was actually a &#8220;sinkhole&#8221; maintained by rival researchers at Kaspersky Lab.</p>
<p>FireEye had noticed communications from both virus strains were heading to the same IP address – but this was a system set up by the Russian lab, which had asked DNS providers to redirect data sent from the two software nasties so as to examine their network traffic.</p>
<p>&#8220;In light of new information shared by the security community, we now know that our original conclusions were incorrect and we cannot associate these two malware families based solely upon these common CnC coordinates,&#8221; FireEye researchers conceded in an updated blog post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2012/06/01/flame-virus-sensationalism/comment-page-1/#comment-23833</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Thu, 23 Aug 2012 12:39:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.epanorama.net/blog/?p=11688#comment-23833</guid>
		<description><![CDATA[Former CIA Director Michael Hayden had industrial malware a good idea of ​​the 60 Minutes program. He thinks that Stuxnet worm, which caused problems in Iran&#039;s nuclear program is a good idea. According to him, the world will see that there is someone who clearly had decided to be acceptable in such activities. Hayden said that he did not know who was behind Stuxnet.

Hayden was director of the CIA from April 2005 to May 2006. Before that, he was the head of NSA since 1999.

Source: http://www.itviikko.fi/uutiset/2012/03/05/entinen-cia-johtaja-tykkaa-stuxnetista/201224554/7]]></description>
		<content:encoded><![CDATA[<p>Former CIA Director Michael Hayden had industrial malware a good idea of ​​the 60 Minutes program. He thinks that Stuxnet worm, which caused problems in Iran&#8217;s nuclear program is a good idea. According to him, the world will see that there is someone who clearly had decided to be acceptable in such activities. Hayden said that he did not know who was behind Stuxnet.</p>
<p>Hayden was director of the CIA from April 2005 to May 2006. Before that, he was the head of NSA since 1999.</p>
<p>Source: <a href="http://www.itviikko.fi/uutiset/2012/03/05/entinen-cia-johtaja-tykkaa-stuxnetista/201224554/7" rel="nofollow">http://www.itviikko.fi/uutiset/2012/03/05/entinen-cia-johtaja-tykkaa-stuxnetista/201224554/7</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2012/06/01/flame-virus-sensationalism/comment-page-1/#comment-23832</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Wed, 20 Jun 2012 07:31:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.epanorama.net/blog/?p=11688#comment-23832</guid>
		<description><![CDATA[Report: US and Israel Behind Flame Espionage Tool
http://www.wired.com/threatlevel/2012/06/us-and-israel-behind-flame/

The United States and Israel are responsible for developing the sophisticated espionage rootkit known as Flame, according to anonymous Western sources quoted in a news report.

The malware was designed to provide intelligence about Iran’s computer networks and spy on Iranian officials through their computers as part of an ongoing cyberwarfare campaign, according to the Washington Post.

The program was a joint effort of the National Security Agency, the CIA and Israel’s military, which also produced the Stuxnet worm that is believed to have sabotaged centrifuges used for Iran’s uranium enrichment program in 2009 and 2010.

“This is about preparing the battlefield for another type of covert action,” a former high-ranking US intelligence official told the Post. “Cyber collection against the Iranian program is way further down the road than this.”

Kaspersky disclosed last week that Flame in fact contained some of the same code as Stuxnet, directly tying the two pieces of malware together.

According to the Post Flame was designed to infiltrate highly secure networks in order to siphon intelligence from them, including information that would help the attackers map a target network. Flame, as previously reported, can activate a computer’s internal microphone to record conversations conducted via Skype or in the vicinity of the computer. It also contains modules that log keyboard strokes, take screen shots of what’s occurring on a machine, extract geolocation data from images and turn an infected computer into a Bluetooth beacon to siphon information from Bluetooth-enabled phones that are near the computer.

Flame exploited a vulnerability in Microsoft’s terminal service system to allow the attackers to obtain a fraudulent Microsoft digital certificate to sign their code, so that it could masquerade as legitimate Microsoft code and be installed on a target machine via the Microsoft software update function.

Flame was developed at least five years ago as part of a classified program code-named Olympic Games, the same program that produced Stuxnet.

“It is far more difficult to penetrate a network, learn about it, reside on it forever and extract information from it without being detected than it is to go in and stomp around inside the network causing damage,” said Michael V. Hayden, a former NSA director and CIA director who left office in 2009, told the Post.

It’s still unclear whether the malware used to attack computers in Iran’s oil ministry is the same malware now known as Flame.]]></description>
		<content:encoded><![CDATA[<p>Report: US and Israel Behind Flame Espionage Tool<br />
<a href="http://www.wired.com/threatlevel/2012/06/us-and-israel-behind-flame/" rel="nofollow">http://www.wired.com/threatlevel/2012/06/us-and-israel-behind-flame/</a></p>
<p>The United States and Israel are responsible for developing the sophisticated espionage rootkit known as Flame, according to anonymous Western sources quoted in a news report.</p>
<p>The malware was designed to provide intelligence about Iran’s computer networks and spy on Iranian officials through their computers as part of an ongoing cyberwarfare campaign, according to the Washington Post.</p>
<p>The program was a joint effort of the National Security Agency, the CIA and Israel’s military, which also produced the Stuxnet worm that is believed to have sabotaged centrifuges used for Iran’s uranium enrichment program in 2009 and 2010.</p>
<p>“This is about preparing the battlefield for another type of covert action,” a former high-ranking US intelligence official told the Post. “Cyber collection against the Iranian program is way further down the road than this.”</p>
<p>Kaspersky disclosed last week that Flame in fact contained some of the same code as Stuxnet, directly tying the two pieces of malware together.</p>
<p>According to the Post Flame was designed to infiltrate highly secure networks in order to siphon intelligence from them, including information that would help the attackers map a target network. Flame, as previously reported, can activate a computer’s internal microphone to record conversations conducted via Skype or in the vicinity of the computer. It also contains modules that log keyboard strokes, take screen shots of what’s occurring on a machine, extract geolocation data from images and turn an infected computer into a Bluetooth beacon to siphon information from Bluetooth-enabled phones that are near the computer.</p>
<p>Flame exploited a vulnerability in Microsoft’s terminal service system to allow the attackers to obtain a fraudulent Microsoft digital certificate to sign their code, so that it could masquerade as legitimate Microsoft code and be installed on a target machine via the Microsoft software update function.</p>
<p>Flame was developed at least five years ago as part of a classified program code-named Olympic Games, the same program that produced Stuxnet.</p>
<p>“It is far more difficult to penetrate a network, learn about it, reside on it forever and extract information from it without being detected than it is to go in and stomp around inside the network causing damage,” said Michael V. Hayden, a former NSA director and CIA director who left office in 2009, told the Post.</p>
<p>It’s still unclear whether the malware used to attack computers in Iran’s oil ministry is the same malware now known as Flame.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2012/06/01/flame-virus-sensationalism/comment-page-1/#comment-23831</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Wed, 13 Jun 2012 07:02:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.epanorama.net/blog/?p=11688#comment-23831</guid>
		<description><![CDATA[Microsoft overhauls certificate management in response to Flame PKI hack
A new Windows auto-update will flag certs that are “no longer trustworthy.”
http://arstechnica.com/security/2012/06/microsoft-overhauls-certificate-management-in-response-to-flame-pki-hack/

As part of its monthly “Patch Tuesday” security updates for June, Microsoft announced changes in how Windows manages certificates. These changes include a new automatic updater tool for Windows 7 and Windows Vista that will flag stolen or known forged certificates. This shift will have a huge impact on companies and software vendors who use Microsoft’s implementation of public key infrastructure as part of their authentication and software distribution—especially if they haven’t followed best practices for certificates in the past.

The changes come on the heels of revelations about the recently discovered Flame malware, which used a rogue certificate authority that masqueraded as Microsoft in order to hijack the Windows Update mechanism.

On June 8, Microsoft made changes to its Update service to prevent such attacks in the future. The changes announced on June 11 go even further]]></description>
		<content:encoded><![CDATA[<p>Microsoft overhauls certificate management in response to Flame PKI hack<br />
A new Windows auto-update will flag certs that are “no longer trustworthy.”<br />
<a href="http://arstechnica.com/security/2012/06/microsoft-overhauls-certificate-management-in-response-to-flame-pki-hack/" rel="nofollow">http://arstechnica.com/security/2012/06/microsoft-overhauls-certificate-management-in-response-to-flame-pki-hack/</a></p>
<p>As part of its monthly “Patch Tuesday” security updates for June, Microsoft announced changes in how Windows manages certificates. These changes include a new automatic updater tool for Windows 7 and Windows Vista that will flag stolen or known forged certificates. This shift will have a huge impact on companies and software vendors who use Microsoft’s implementation of public key infrastructure as part of their authentication and software distribution—especially if they haven’t followed best practices for certificates in the past.</p>
<p>The changes come on the heels of revelations about the recently discovered Flame malware, which used a rogue certificate authority that masqueraded as Microsoft in order to hijack the Windows Update mechanism.</p>
<p>On June 8, Microsoft made changes to its Update service to prevent such attacks in the future. The changes announced on June 11 go even further</p>
]]></content:encoded>
	</item>
</channel>
</rss>
