The attackers behind the complex Flame cyberespionage toolkit, believed to be a state-sponsored operation, used an extensive list of fake identities to register at least 86 domains, which they used as part of their command-and-control center, according to researchers at Russia-based antivirus firm Kaspersky Lab.Map showing the number and geographical location of Flame infections on Kaspersky customer machines. Courtesy of Kaspersky Lab
Kaspersky says the size of the command-and-control infrastructure, which appears to have been still partially active a few days ago even after the operation was publicly exposed, exceeds anything they’ve seen before.
“The huge amount of fake domains and fake identities used to run this infrastructure is pretty much unprecedented and unlike any other malware that we have seen before,” said Roel Schouwenberg, senior antivirus researcher at Kaspersky Lab. “In my opinion, it’s an indication of the huge resources which went into this project.”
Many of the domains, set up as early as 2008 in some cases and as late as April this year, were registered with the GoDaddy registrar service, and used fake addresses in Germany and Austria, with Vienna being a particularly popular choice for the attackers, according to research done by Kaspersky. A lot of the addresses tracked to places like hotels, medical offices, and shops. At least one address was for the British library in Paris and shops. Other addresses did not appear to exist at all.
The domains pointed to 24 IP addresses, at various times, that were located in Germany, Poland, Malaysia, Latvia, Switzerland, Turkey, the Netherlands, Hong Kong and other places.
The attackers used each identity only two or three times on average to register a domain, before choosing a new one. It’s not clear what they used to pay for the domains. Kaspersky referred the question to GoDaddy, but the registrar did not respond to a request for comment.
Cybercriminals often use stolen credit card numbers to pay for domains used in their operations, but since Flame is believed to be a state-run operation, the attackers likely used pre-paid cards issued under fake names to register the domains.
Although the domains went dark about an hour after news of the operation broke worldwide last Monday, suggesting the attackers were shutting down the mission, at least three infected machines in Iran, Iraq, and Lebanon were upgraded by the attackers with new versions of the malware after this occurred, Schouwenberg said, suggesting a certain boldness on their part.
Two of the machines went from having version 2.212 of Flame installed on them to suddenly having version 2.242.
“This means basically that this week, after the [news] announcement, the Flame command-and-control network was still operational and sending updates, possibly commands, to the victims,” Schouwenberg said. “Which, in my opinion, this is quite amazing, that despite all this noise and the story being everywhere, they’re still using the command-and-control infrastructure to send updates.”
Flame has a hardcoded password, 'LifeStyle2', that infected machines use to connect to command-and-control servers. Courtesy of Kaspersky
New findings also show that the attackers were particularly interested in stealing AutoCAD drawings from infected machines, according to the types of stolen files Kaspersky has seen infected machines trying to upload to the attackers’ domains.
AutoCAD is a popular software program that is used to render computerized models and schematics for architectural designs and consumer products, as well for the layout of machinery and networks at plants and factories, including critical infrastructure facilities.
The interest in AutoCAD documents is something Flame shares with DuQu, another espionage tool that was discovered on machines in various countries last year and is closely related to Stuxnet, the groundbreaking infrastructure-sabotaging malware that is believed to have wreaked havoc on Iran’s nuclear program in 2009 and 2010.
Flame is a 20MB malicious toolkit that consists of at least 20 known modules that can be swapped in and out to provide various functionality for the attackers – such as eavesdropping on conversations via the internal microphone on an infected computer, stealing documents or taking screenshots of email and instant message communications — depending on what the attackers want to do on a particular machine.
The toolkit is believed be part of a parallel project created by contractors who were hired by the same nation-state team that was behind Stuxnet and DuQu.
Flame appears to have been operating in the wild as early as March 2010, though there are clues that the malware may have been active as early as 2007. It was only discovered about three weeks ago by Kaspersky. It’s believed to have infected about 1,000 machines in the Middle East and elsewhere.
After news of Flame broke last Monday and the attackers shut down their domains, infected machines contacting the servers to report in and receive commands were met with 403/404 errors.
The researchers had already set up a sinkhole, however, and worked with GoDaddy and OpenDNS to divert traffic for about 30 of the domains to their sinkhole instead. This means that stolen files that would have landed in the hands of the attackers, are now being delivered to Kaspersky, though they’re encrypted by the malware before they’re sent out to Kaspersky.
The researchers got their first hit from an infected machine late that first evening after the redirect was completed, and have received communication from 118 infected systems from 18 countries and the Occupied West Bank since then.
Chart showing the domains the attackers registered for Flame and the registration dates. Courtesy of OpenDNS
Because antivirus firms distributed signatures and tools to detect and remove Flame quickly last week, the machines contacting the sinkhole are ones that either didn’t have antivirus installed on them, or don’t have updated signatures installed and are therefore still infected. These include 45 machines in Iran, 21 in Lebanon, 14 in Sudan, and 8 in the United States.
Each time an infected machine tries to contact the attack domains, they use a hardcoded password, LifeStyle2, to identify themselves as a Flame-infected machine. The password is coded into the malware’s configuration file, but can be changed.
Once a connection is established, the infected machine begins uploading compressed and encrypted packages of data, including an activity log that records everything the malware has done on the infected machine as well as a list of files it has sent to the attackers.
To avoid uploading entire documents from an infected machine to the attackers — which would mean collecting a lot of data in which they have no interest — the attackers designed their malware to just parse through PDFs, Excel and word-processing documents and extract a 1-kilobyte sample of the text. The malware then compresses and uploads the sample text to a command-and-control domain where, presumably, the attackers would pick through the contents and instruct the malware to then grab only specific documents that interested them.
Kaspersky still hasn’t figured out definitively if Flame is related to a piece of malware called “Wiper” that Iran reported had deleted files from machines at its Oil Ministry in April. The researchers have not found any module for Flame that wipes out files in the way that “Wiper” reportedly did, but have not ruled out that a wiper module may exist for Flame that they haven’t found yet.
One final new tidbit about Flame: the researchers previously reported that a kill module for Flame, called “browse32,” can be sent out by the attackers to wipe Flame off of systems. The kill module, they previously stated, searches for every trace of the malware on the system, including stored files full of screenshots and data stolen by the malware, and eliminates them, leaving nothing of the malware left behind.
The researchers now say that there is a mistake in the kill module and instead of deleting every trace of Flame, it leaves one file behind. The file is named “~DEB93D.tmp.” It’s the same file that Kaspersky has been instructing users to look for on their systems to determine if they are infected with Flame.
Saturday, June 30, 2012
A Massive Web of Fake Identities and Websites Controlled Flame Warfare
via wired.com
Fed Plotting to Monitor Critics, Tailor Propaganda
Fed Plotting to Monitor Critics, Tailor Propaganda
by Alex Newm, theunhivedmind.comSeptember 27th 2011 2:35 PM
The Federal Reserve is seeking contractors to build a tool that will monitor and analyze blogs, news reports, and social-media chatter about the central bank and its policies, with a goal of being able to use “public relations” strategies to counter the growing barrage of negative publicity. But critics quickly added to the institution’s troubled image as the news spread by lambasting the half-baked scheme as “Orwellian” spying and “intimidation.”
The Fed’s “Request for Proposal” explains that the institution needs a platform to “monitor billions of conversations” and “identify and reach out to key bloggers and influencers.” Information collected will be used to measure the effectiveness of the central bank’s “public relations” and “communication strategies” — known in laymen’s terms as propaganda operations.
“There is need for the Communications Group to be timely and proactively aware of the reactions and opinions expressed by the general public as it relates to the Federal Reserve and its actions on a variety of subjects,” the document states. News outlets, Facebook, Twitter, forums, blogs, YouTube, and other social media platforms will all be targeted.
“A system like this is not cheap,” noted The Economic Collapse Blog, which called the Fed’s plan a “very creepy” part of a disturbing trend. “What the ‘authorities’ want is for us to shut up, sit in our homes and act as if nothing wrong is happening. Meanwhile, they seem determined to watch us more closely than ever.”
The system being sought, which the Fed calls a “Sentiment Analysis And Social Media Monitoring Solution,” should be able to gauge the sentiment and tone expressed by the public. And it must be able to gather information from different countries and regions in multiple languages.
“The solution must provide real-time monitoring of relevant conversations,” the Fed demanded, saying it should also be able to offer summaries or overviews of public sentiment on a variety of topics. An “alerting mechanism” that automatically sends out notifications based on a “predefined trigger” must be incorporated in the system, too.
Other demands listed by the central bank include the ability to track the reach and spread of its propaganda, “handle crisis situations,” and identify emerging trends in Fed-related discussions online. The desired system would also be able to differentiate between “influencers versus followers,” and gauge the true impact of specific anti-Fed criticism beyond simply comparing online traffic data generated by a particular source.
The financial analysis site ZeroHedge, apparently the first media outlet to uncover and expose the scheme, fiercely ridiculed the central bank and its tactics. But it also noted that “the Fed has just entered the counterespionage era and will be monitoring everything written about it anywhere in the world.”
The central bank, however, is not alone. Numerous critics of the plan have compared it to President Obama’s recently unveiled “Attack Watch,” a service for Americans to report negative statements about the administration or its policies. The citizen-snitching operation, as it has been dubbed, also prompted ridicule — but grave concern as well.
And as The New American reported in March, the U.S. military was exposed earlier this year seeking a tool that would allow a single government agent to operate multiple fake social-media characters simultaneously. The objective, similar to the Fed’s desired “solution,” is to monitor critics and influence public opinion through propaganda.
Analysts said authorities’ growing interest in tracking and manipulating public sentiment expressed online is a sign that the alternative media is becoming increasingly powerful as the “mainstream media” continues to implode. Others said the efforts also appear to be desperate intimidation tactics aimed at quieting the growing wave of public outrage aimed at the Fed, the undeclared wars, and the Obama administration.
Fury over the privately owned central banking system and its policies — multi-trillion-dollar secret bailouts, mass manipulation of markets, wild money printing, resisting a government audit, and more — has been steadily rising for years. Official documents released in 2009 revealed that even the U.S. military was concerned about the growing “End the Fed” movement.
But according to analysts, it was becoming clear that the central bank and its owners were on the defensive well before news of the coming spying and propaganda operations made headlines. In mid-2009, for instance, the Fed was forced to hire a top lobbyist to defend the cartel’s interests on Capitol Hill.
Experts predict that as the economy and the U.S. dollar continue to tumble, anti-Fed outrage will only intensify. Recent revelations about the central bank’s secret bailouts of foreign firms have certainly not helped its already-poor public image — and analysts say the worse is yet to come.
Proposals and bids from potential suppliers of the secretive “solution” being sought by the Fed are due on September 23. It remains unclear how much the system may cost.
Original Page: http://theunhivedmind.com/wordpress/?p=3427
Um, yeah! I noticed!
אל
Four Ways to Protect Kids From Mobile Threats
By teaching your kids some basic mobile safety precautions, you can feel confident about letting your kids enjoy Internet on the go.
You probably think your kids are more tech-savvy than you are. And let’s be honest, they might just be. But just because they’re good at text messaging, Facebook, and Angry Birds doesn’t mean they know everything they need to know. In fact, when it comes to mobile security, most kids don’t have a clue.
For example, do they know how to password-protect their smartphones so mischievous friends don’t mess with them? Do they know that hackers are increasingly attacking mobile devices, and what to do about it? Can they spot a fraudulent email or Web link? And have they backed up their data in case their school laptop gets lost or stolen?
Time to step in, parents. It’s up to you to help keep your kids safe from the growing number of mobile threats that can strike laptops, tablets, smartphones — and your kids themselves. Follow these four key steps to help ensure that your kids’ devices and data don’t fall into the wrong hands.
1. Explain the dangers of sharing personal information
How many stories have you heard about online predators and the kids who unwittingly fall victim to them? This happens because kids don’t recognize the dangers of communicating with strangers via email, text messages, online chat and social networks — all of which can happen on their mobile devices, without your knowledge.
Indeed, while preschoolers are warned of “stranger danger,” older kids need to learn that the same principle applies to online strangers. So have a five-minute talk about it. Knowledge is power, and this is a lesson tweens and teens need to learn: Let them know that it’s never a good idea to respond to anyone they don’t know online. Since they never know when a suspicious adult is misrepresenting him- or herself as a peer, make sure your kids know not to give out any personal information online. Ever.
2. Insist on protection — password protection.
Mobile devices can easily get lost or stolen. That’s a problem for any number of reasons, not the least of which is that it can reveal your child’s personal information to others. (And if that “other” is a prankster peer, it might lead to unauthorized photo sharing, bogus status updates and tweets, and the like — any of which could get your child in trouble for something he or she didn’t do, or, worse, make him or her the target of cyber-bullying.)
One simple fix: demand password protection for all smartphones and tablets. On Android devices, launch the Settings app, then tap Location & Security, Set up screen lock. Here you’ll see a choice of security options: password, numeric PIN, or pattern. (This last lets you trace a pattern to unlock the screen.) Choose one, then follow the prompts to configure it.
On iOS devices, tap Settings, General, Passcode Lock. The default lock option is a four-digit numeric password, but if you switch Simple Passcode to Off, you can upgrade your protection with any alphanumeric password you want. Either way, tap Turn Passcode On, then follow the prompts.
3. Install a kid-safe mobile browser
The Web has its share of unsavory — and unsafe — destinations. Unfortunately, the average mobile Web browser offers no protections of any kind, no filters that block unsuitable content or parental controls for restricting certain kinds of sites.
Thankfully, you can minimize Web threats by installing a family-friendly mobile browser, one that offers a familiar interface backed by various protections. These browsers will filter inappropriate search-engine results and block access to inappropriate sites (whether accessed intentionally or accidentally).
McAfee offers several security features for smartphones.
4. Install security apps
Mobile security doesn’t end with a watchful Web browser. Hacker attacks on smartphones and tablets are on the rise, and they can result in the theft of private data, personal photos, and even money. That’s why it’s essential to outfit your kids’ mobile devices with anti-malware software, which can protect against threats like viruses, spyware, and phishing.
- See more like this:
- wireless security,
- apple iphone,
- android
via pcworld.com
Twittergate: Project World Awareness; aka @ rocking jude Exhibit 3
Failed“The Roof is on Fire” and Philadelph ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in about 1 monthabout 1 month agoFailedElyssa Durant || NIRA Directory on Think ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in about 1 monthabout 1 month agoFailedMind - When Parents Are Too Toxic to Tol ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@rockingjude, 11/27/10 3:14 PM hacking @ ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@SpottyX, 12/29/10 8:39 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedCharges dismissed against reformed-mob-b ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedPolice scandal in Philadelphia tips off ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedFacebook conspiracy: Data mining for the ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@spademaccool @badjerry @heyjude408 @hey ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@rockingjude, 12/30/10 8:39 PM "loll"
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed12/30/10 8:50 PM @longhawl || ACCOUNT S ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed12/30/10 5:16 PM @heywho #TwitterGate
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedConversation
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedConversation thread 2 #verified
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedConversation thread 1
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedConversation
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedFacebook conspiracy: Data mining for the ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@rockingjude, 11/27/10 3:14 PM hacking @ ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed12/29/10 9:49 PM how to catch a cybersta ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed#E "hunting?"
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @longhawl dm root
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @JasonBWhitman
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @JasonBWhitman
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @rockingjude
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @JasonBWhitman
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @rockingjude
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @JasonBWhitman
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedStalked on Facebook too! New attachment
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@yagbebi, 12/29/10 12:35 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@ElyssaD, 12/29/10 5:07 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@ElyssaD, 12/29/10 5:08 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@ElyssaD, 12/29/10 5:11 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@ElyssaD, 12/29/10 5:15 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@Reenit, 12/29/10 6:20 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@ElyssaD, 12/29/10 6:30 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@SpottyX, 12/29/10 7:59 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@papakelt, 12/29/10 6:37 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@ElyssaD, 12/29/10 6:38 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@firetown, 12/29/10 6:52 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@ElyssaD, 12/29/10 6:59 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@rockingjude, 11/24/10 12:05 PM now publ ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedConversation @heyjude408 @safeworld4wome ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@Dobroyeutro, 12/29/10 7:35 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@DickAmateur, 12/29/10 8:58 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@ElyssaD, 12/29/10 9:16 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@SpottyX, 12/29/10 8:38 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@HeyJude408, 12/29/10 10:01 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@HeyJude408, 12/29/10 9:54 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@rockingjude, 11/24/10 12:05 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@HeyJude408, 12/29/10 10:01 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@ElyssaD, 11/28/10 2:55 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@rockingjude, 11/24/10 12:05 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@rockingjude, 10/17/10 9:13 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@badjerry, 11/26/10 11:49 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed, 11/24/10 12:05 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedExcuses, 11/24/10 12:05 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@wired, 3/9/10 8:05 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@q_pq look what i found 10/17/10 9:13 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@netlibertaire, 11/20/10 5:39 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@badjerry, 11/26/10 11:49 AM I knew
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@CelticFire69, 11/28/10 8:35 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@ElyssaD, 12/28/10 11:14 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@ElyssaD, 12/28/10 11:19 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@HeyJude408, 12/29/10 1:33 AM you gave i ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedConversation
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@d_is, 12/29/10 4:39 AM another witness
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@SpottyX, 12/29/10 8:39 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@DickAmateur, 12/29/10 8:58 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@icpchad, 7/26/10 5:12 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@ElyssaD, 12/28/10 11:19 PM wanna talk i ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@ElyssaD, 12/29/10 5:08 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@ElyssaD, 12/29/10 5:21 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@ElyssaD, 12/29/10 6:30 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@SpottyX, 12/29/10 7:59 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@ElyssaD, 12/29/10 5:08 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@ElyssaD, 12/29/10 5:11 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@ElyssaD, 12/29/10 5:15 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@Reenit, 12/29/10 6:20 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@ElyssaD, 12/29/10 5:07 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedConversation too little too late. #verif ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@JasonBWhitman, 12/28/10 5:47 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedConversation hiding the evidence ?
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@rockingjude, 12/28/10 6:44 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@rockingjude, 12/28/10 6:59 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@rockingjude, 12/24/10 9:33 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@ElyssaD, 12/17/10 10:42 AM no second ch ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedMike Dammann (@firetown) @ElyssaD no mor ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@SpottyX, 12/26/10 5:20 AM @q_pq redirec ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@firetown, 12/20/10 11:42 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@firetown, 12/21/10 11:34 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedConversation
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@HeyJude408, 12/29/10 2:50 PM we saw too
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@srbijadanas, 12/29/10 3:00 PM me thinks ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailed@earthspeakorg, 12/29/10 4:16 PM Retweet
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedPWA Exposed disinfo provocateur & gang s ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedGuilty
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTwitter server unavailable ? Wanna bet?
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedDMs hacked: 6 months wiped (or so she th ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedEvidence reveals hoax staged by @rocking ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedCo-conspirators @rockingjude @longhawl # ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedIllegal tampering of tweets? GTFO @rocki ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedAuthentication Error during attack
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedProject World Awareness Disinformation A ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedPapua New Guinea
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @d_is @rockingjude dm
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @ElyssaD
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedDisinformation agent exposed! Breaking !
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @rockingjude get your paws ou ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @rockingjude addtoany #verifi ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @ElyssaD using tweetdeck dupl ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @rockingjude via @loghawl add ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @rockingjude
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @rockingjude addtoany
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @rockingjude via add to any
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @rockingjude add to any
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @rockingjude addtoany
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @rockingjude adtoany
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @rockingjude
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @rockingjude
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @rockingjude
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @ElyssaD addtoany guilty
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @ElyssaD fire
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @ElyssaD @heyjude408 @thefeeg
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @uksmallbiz apparently not
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @gnudarwin 3rd party replies ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @ElyssaD #verified again #uk
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @ElyssaD #verified
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @SpottyX attacked through bot ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @rockingjude she is using Twe ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @rockingjude TweetDeck
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @rockingjude add to any not v ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @rockingjude via @longhawl us ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @rockingjude now using TweedD ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @rockingjude using TweetDeck ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @rockingjude v @longhawl addt ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @rockingjude
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @uksmallbiz
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedElyssaD sick. Twisted. map. #USA #VERIF ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet @Mtmk102 #USA #infosec alert
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @longhawl @rockingjude you ne ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @ElyssaD
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTwisted
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedTweet from @rockingjude
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedThe Powers That Beat: ACCORDING TO EXPER ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedDemocrazy USA
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months5 months agoFailedBACKUP! Fwd: Tweet from @rockingjude ø� ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailed400 Bad Request OMG!
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailed2010: The Year the Internet Went to War ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedWikileaks: This Is Just The Beginning | ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailed#CHAOS Chaos Computer Club & Wikileaks
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedGadgets Bring New Opportunities for Hack ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedRT @srbijadanas, 12/27/10 12:25 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedRule #1 @ElyssaD, 12/23/10 4:50 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailed
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedDo Aliens Exist? If So, Will They Kill U ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedBrits Release UFO Docs : Discovery News
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedNo way Jose!
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedRule #1
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailed@d_is, 12/17/10 11:39 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedHactivist Code of Ethics: RULE #1
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedConversation passport
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailed@ElyssaD, 12/23/10 10:35 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailed@longhawl, 12/25/10 8:52 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailed[Firetown.com] New attachment
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedTwitter / Suspended [damn... i'm good!] ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedFULL TEXT ... @WIKILEAKS Sanity for Supe ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedFirst they Came for...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedWikileaks: Who Rules by the Code, Will F ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedUntitled
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedFormer CIA Officials Admit To Faking Bin ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedRumor: Microsoft Working on New Windows ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedAirPlay Hack Streams Non-iTunes Video Be ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedSync Adds Voice Control of Smartphone Ap ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedGoogle Buys Giant New York Building for ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedApple Bans Lame WikiLeaks App | Threat L ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedMobile Prison Guard Towers Coming to a W ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedVictims of CyberBull: Defending Victims ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedThe Reason I Stay
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedVictims of CyberBull: Defending Victims ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedReality Bytes: IN MY COUNTRY
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedWhyoming Part I: HOPE
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedConversation
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedVictims of CyberBull: Defending Victims ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedVictims of CyberBull: Defending Victims ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedTransaction Analysis: Conversation 12/17 ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedOh noes!
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedInternet Crime Complaint Center (IC3) #N ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedInternet Crime Complaint Center (IC3) | ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedCYBERCRIMES vs. HACKTIVISM KNOW YOUR RIG ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedUS Spying on its Citizens | via @FIRETOW ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedHaiti/Chile EarthQuake H.A.A.R.P 2010 | ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedReality Bytes: IN MY COUNTRY
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedSocial Security Fraud: Abuse of Process ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedWhyoming Part I: HOPE
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailed"to help protect your privacy?" GTFO
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedConversation 12/20
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedConversation 12/20
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedTWEETDECK SECURITY FLAW iPAD fix... DEAU ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedTWEETDECK SECURITY FLAW iPAD fix... DEAU ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedConversation 12/20
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedTWEETDECK SECURITY FLAW iPAD fix... DEAU ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailed@almostvisible still listening... List ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedConversation
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedConversation 12/20
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedTWEETDECK SECURITY FLAW iPAD fix... DEAU ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedConversation 12/20
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedConversation
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailed@almostvisible still listening... List ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedGeorge Orwell #1984 #quote
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedWhen psychiatry tells you your kids are ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailed@almostvisible still listening... List ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedHunger in America: Where are our taxes g ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedTwitter / @Elyssa Durant: Check this vid ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedReality Bytes: Is Equal Opportunity Just ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedCyberBUSTED [Reality Bytes] 12/21/2010 0 ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailed"to help protect your privacy?" GTFO
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedAbscam Operation | Socyberty
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedCOINTELPRO targets [ listed under operat ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedWhyoming Part I: HOPE
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedHow are you feeling today? @yagbebi, 12/ ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedCyberBusted @rockingjude
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedSocial Security Fraud: Abuse of Process ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedReality Bytes: IN MY COUNTRY
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedHaiti/Chile EarthQuake H.A.A.R.P 2010 | ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedRothschild daughter WARNS of bomb attack ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedUS Spying on its Citizens | via @FIRETOW ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedWikileaks claims: US did find Iraq WMD | ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedCYBERCRIMES vs. HACKTIVISM KNOW YOUR RIG ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedInternet Crime Complaint Center (IC3) #N ...
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedOh noes!
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedCyberBusted @rockingjude
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedGeorge Orwell #1984 #quote
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedredemption
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedOperation Chaos #payback #FreE
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months agoFailedLocation data
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months6 months ago
Failed
“The Roof is on Fire” and Philadelph ...
Reason: Tumblr::API::AuthError
Next attempt in about 1 month
about 1 month ago
Failed
Elyssa Durant || NIRA Directory on Think ...
Reason: Tumblr::API::AuthError
Next attempt in about 1 month
about 1 month ago
Posted
Crash JP MORGAN: BUY SILVER… | via @r ...
4 months ago
Posted
@rockingjude, 11/27/10 3:14 PM hacking @ ...
5 months ago
Posted
@SpottyX, 12/29/10 8:39 PM
5 months ago
Posted
Police scandal in Philadelphia tips off ...
5 months ago
Posted
@spademaccool @badjerry @heyjude408 @hey ...
5 months ago
Posted
@rockingjude, 12/30/10 8:39 PM "loll"
5 months ago
Posted
12/30/10 8:50 PM @longhawl || ACCOUNT S ...
5 months ago
Posted
12/30/10 5:16 PM @heywho #TwitterGate
5 months ago
Posted
Conversation
5 months ago
Posted
Conversation thread 2 #verified
5 months ago
Subscribe to:
Posts (Atom)