http://twitter.com/#!/mdrache/status/476768527811366912

TweetDeck users were just minding their own business, when suddenly, all hell broke loose:

http://twitter.com/#!/flyoverangel/status/476769197666467841

According to Gizmodo, the issue was “an XSS vulnerability that allows attackers to execute code remotely on your computer just by tweeting it out.” Here’s what that looks like:

http://twitter.com/#!/mikeBithell/status/476766169907875840
http://twitter.com/#!/DefuseSec/status/476753443734835200
http://twitter.com/#!/einfal/status/476769629067436032

TweetDeck claimed to have fixed the problem:

http://twitter.com/#!/TweetDeck/status/476763638695743489

But users weren’t exactly convinced:

http://twitter.com/#!/flyoverangel/status/476770214768439296
http://twitter.com/#!/baseballcrank/status/476769391040684032

Hmmm.

http://twitter.com/#!/attackerman/status/476765474831994880

Nope. About half an hour after tweeting that the issue had been resolved, TweetDeck sent this update:

http://twitter.com/#!/TweetDeck/status/476770732987252736

Basically giving us the green light to freak out:

http://twitter.com/#!/staypuft/status/476765640188243968
http://twitter.com/#!/Ny_Nady/status/476752837993824256
http://twitter.com/#!/rihani/status/476783106142502913
http://twitter.com/#!/bccover/status/476768866409119744

Awww, don’t cry! TweetDeck may have been on life support, but our sense of humor never skipped a beat!

http://twitter.com/#!/baldingschemer/status/476768845755994112

Ha!

Supposedly, the problem’s been fixed for reals now:

http://twitter.com/#!/TweetDeck/status/476784927791280128

We’ll see about that.

http://twitter.com/#!/NathanWurtzel/status/476785789486247936

Read more: http://twitchy.com/2014/06/11/what-is-this-the-dark-ages-tweetdeck-goes-down-massive-freakout-ensues/