Blaming the #Flame

I’ve been getting a kick out of all the #flamefacts going around Twitter, especially the tweets that place Flame at the scene of some of history’s major events (and fiction’s major events, too). One of my Twitter connections, a Brazilian infosec practitioner who goes by the handle @anchisesbr, is full of them this morning.

Since we can always use a chuckle on Mondays, I thought I’d share the witticisms he’s sent me and some others:

Mayan calendar ends in 2012 because they predicted #flame malware #flamefacts — @anchisesbr

A beta version of #flame malware blew up Chernobyl reactor #flamefacts  — @anchisesbr

First version of #flame created in 1997 and took down an entire alien fleet at Independence Day #flamefacts — @anchisesbr

#flame stole LinkedIn passwords (and #flame has a module to decrypt them!) #flamefacts — @anchisesbr

#Flame infected Bruce Schneier’s computer #flamefacts #schneierfacts

When Flame first started dominating the headlines a couple weeks ago, the barbs were about who created this so-called child of Stuxnet and Duqu. Some of my favorites were:

@gattaca: We here at Liquidmatrix discovered #Flame in 1984. #funfauxfacts

@gattaca: To be fair, my ancestors found the code for #Flame in a cave painting.

@threatagent: BBQ was discovered a few hours after #Flame

Another tweeter to to @gattaca: Dude, I discovered #flame in 1976. We shared a placenta.

If you don’t have a sense of humor after focusing on information security for a few years, your ticker probably won’t make it.

Enjoy the week, folks.