#pwned by Project World Awareness; Jackson Hole, Wyoming

pwned by Project World Awareness; Jackson Hole, Wyoming #tcot

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
@SpottyX, 12/29/10 8:39 PM
5 months ago

Posted
Conversation
5 months ago

Posted
Conversation thread 2 #verified
5 months ago

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 month
about 1 month ago

Failed
Elyssa Durant || NIRA Directory on Think …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in about 1 month
about 1 month ago

Failed
Mind – When Parents Are Too Toxic to Tol …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@rockingjude, 11/27/10 3:14 PM hacking @ …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@SpottyX, 12/29/10 8:39 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Charges dismissed against reformed-mob-b …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Police scandal in Philadelphia tips off …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Facebook conspiracy: Data mining for the …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@spademaccool @badjerry @heyjude408 @hey …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@rockingjude, 12/30/10 8:39 PM “loll”
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
12/30/10 8:50 PM @longhawl || ACCOUNT S …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
12/30/10 5:16 PM @heywho #TwitterGate
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Conversation
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Conversation thread 2 #verified
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Conversation thread 1
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Conversation
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Facebook conspiracy: Data mining for the …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@rockingjude, 11/27/10 3:14 PM hacking @ …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
12/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 months
5 months ago

Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
#E “hunting?”
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @longhawl dm root
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @JasonBWhitman
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @JasonBWhitman
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @longhawl
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @rockingjude
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @JasonBWhitman
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @rockingjude
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @JasonBWhitman
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Stalked on Facebook too! New attachment
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@yagbebi, 12/29/10 12:35 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@ElyssaD, 12/29/10 5:07 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@ElyssaD, 12/29/10 5:08 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@ElyssaD, 12/29/10 5:11 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@ElyssaD, 12/29/10 5:15 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@Reenit, 12/29/10 6:20 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@ElyssaD, 12/29/10 6:30 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@SpottyX, 12/29/10 7:59 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@papakelt, 12/29/10 6:37 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@ElyssaD, 12/29/10 6:38 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@firetown, 12/29/10 6:52 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@ElyssaD, 12/29/10 6:59 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@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 months
5 months ago

Failed
Conversation @heyjude408 @safeworld4wome …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@Dobroyeutro, 12/29/10 7:35 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@DickAmateur, 12/29/10 8:58 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@ElyssaD, 12/29/10 9:16 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@SpottyX, 12/29/10 8:38 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@HeyJude408, 12/29/10 10:01 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@HeyJude408, 12/29/10 9:54 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@rockingjude, 11/24/10 12:05 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@HeyJude408, 12/29/10 10:01 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@ElyssaD, 11/28/10 2:55 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@rockingjude, 11/24/10 12:05 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@rockingjude, 10/17/10 9:13 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@badjerry, 11/26/10 11:49 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
, 11/24/10 12:05 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Excuses, 11/24/10 12:05 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@wired, 3/9/10 8:05 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@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 months
5 months ago

Failed
@netlibertaire, 11/20/10 5:39 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@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 months
5 months ago

Failed
@CelticFire69, 11/28/10 8:35 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@ElyssaD, 12/28/10 11:14 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@ElyssaD, 12/28/10 11:19 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@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 months
5 months ago

Failed
Conversation
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@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 months
5 months ago

Failed
@SpottyX, 12/29/10 8:39 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@DickAmateur, 12/29/10 8:58 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@icpchad, 7/26/10 5:12 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@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 months
5 months ago

Failed
@ElyssaD, 12/29/10 5:08 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@ElyssaD, 12/29/10 5:21 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@ElyssaD, 12/29/10 6:30 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@SpottyX, 12/29/10 7:59 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@ElyssaD, 12/29/10 5:08 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@ElyssaD, 12/29/10 5:11 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@ElyssaD, 12/29/10 5:15 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@Reenit, 12/29/10 6:20 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@ElyssaD, 12/29/10 5:07 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Conversation too little too late. #verif …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@JasonBWhitman, 12/28/10 5:47 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Conversation hiding the evidence ?
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@rockingjude, 12/28/10 6:44 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@rockingjude, 12/28/10 6:59 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@rockingjude, 12/24/10 9:33 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@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 months
5 months ago

Failed
Mike Dammann (@firetown) @ElyssaD no mor …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@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 months
5 months ago

Failed
@firetown, 12/20/10 11:42 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@firetown, 12/21/10 11:34 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Conversation
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
@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 months
5 months ago

Failed
@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 months
5 months ago

Failed
@earthspeakorg, 12/29/10 4:16 PM Retweet
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
PWA Exposed disinfo provocateur & gang s …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Guilty
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Twitter server unavailable ? Wanna bet?
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
DMs hacked: 6 months wiped (or so she th …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Evidence reveals hoax staged by @rocking …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Co-conspirators @rockingjude @longhawl # …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Illegal tampering of tweets? GTFO @rocki …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Authentication Error during attack
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Project World Awareness Disinformation A …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Papua New Guinea
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @d_is @rockingjude dm
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @ElyssaD
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Disinformation agent exposed! Breaking !
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @rockingjude get your paws ou …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @rockingjude addtoany #verifi …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @ElyssaD using tweetdeck dupl …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @rockingjude via @loghawl add …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @rockingjude
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @rockingjude addtoany
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @rockingjude via add to any
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @rockingjude add to any
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @rockingjude addtoany
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @rockingjude adtoany
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @rockingjude
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @rockingjude
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @rockingjude
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @ElyssaD addtoany guilty
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @ElyssaD fire
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @ElyssaD @heyjude408 @thefeeg
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @uksmallbiz apparently not
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @gnudarwin 3rd party replies …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @ElyssaD #verified again #uk
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @ElyssaD #verified
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @SpottyX attacked through bot …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @rockingjude she is using Twe …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @rockingjude TweetDeck
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @rockingjude add to any not v …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @rockingjude via @longhawl us …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @rockingjude now using TweedD …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @rockingjude using TweetDeck …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @rockingjude v @longhawl addt …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @rockingjude
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @uksmallbiz
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
ElyssaD sick. Twisted. map. #USA #VERIF …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet @Mtmk102 #USA #infosec alert
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @longhawl @rockingjude you ne …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @ElyssaD
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Twisted
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Tweet from @rockingjude
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
The Powers That Beat: ACCORDING TO EXPER …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
Democrazy USA
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 5 months
5 months ago

Failed
BACKUP! Fwd: Tweet from @rockingjude ø� …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
400 Bad Request OMG!
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
2010: The Year the Internet Went to War …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Wikileaks: This Is Just The Beginning | …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
#CHAOS Chaos Computer Club & Wikileaks
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Gadgets Bring New Opportunities for Hack …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
RT @srbijadanas, 12/27/10 12:25 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Rule #1 @ElyssaD, 12/23/10 4:50 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Facebook
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Do Aliens Exist? If So, Will They Kill U …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Brits Release UFO Docs : Discovery News
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
No way Jose!
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Rule #1
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
@d_is, 12/17/10 11:39 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Hactivist Code of Ethics: RULE #1
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Conversation passport
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
@ElyssaD, 12/23/10 10:35 AM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
@longhawl, 12/25/10 8:52 PM
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
[Firetown.com] New attachment
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Twitter / Suspended [damn… i’m good!] …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
FULL TEXT … @WIKILEAKS Sanity for Supe …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
First they Came for…
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Wikileaks: Who Rules by the Code, Will F …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Untitled
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Former CIA Officials Admit To Faking Bin …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Rumor: Microsoft Working on New Windows …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
AirPlay Hack Streams Non-iTunes Video Be …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Sync Adds Voice Control of Smartphone Ap …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Google Buys Giant New York Building for …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Apple Bans Lame WikiLeaks App | Threat L …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Mobile Prison Guard Towers Coming to a W …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Victims of CyberBull: Defending Victims …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
The Reason I Stay
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Victims of CyberBull: Defending Victims …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Reality Bytes: IN MY COUNTRY
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Whyoming Part I: HOPE
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Conversation
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Victims of CyberBull: Defending Victims …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Victims of CyberBull: Defending Victims …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Transaction Analysis: Conversation 12/17 …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Oh noes!
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Internet Crime Complaint Center (IC3) #N …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Internet Crime Complaint Center (IC3) | …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
CYBERCRIMES vs. HACKTIVISM KNOW YOUR RIG …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
US Spying on its Citizens | via @FIRETOW …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Haiti/Chile EarthQuake H.A.A.R.P 2010 | …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Reality Bytes: IN MY COUNTRY
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Social Security Fraud: Abuse of Process …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Whyoming Part I: HOPE
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
“to help protect your privacy?” GTFO
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Conversation 12/20
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Conversation 12/20
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
TWEETDECK SECURITY FLAW iPAD fix… DEAU …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
TWEETDECK SECURITY FLAW iPAD fix… DEAU …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Conversation 12/20
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
TWEETDECK SECURITY FLAW iPAD fix… DEAU …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
@almostvisible still listening… List …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Conversation
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Conversation 12/20
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
TWEETDECK SECURITY FLAW iPAD fix… DEAU …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Conversation 12/20
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Conversation
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
@almostvisible still listening… List …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
George Orwell #1984 #quote
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
When psychiatry tells you your kids are …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
@almostvisible still listening… List …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Hunger in America: Where are our taxes g …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Twitter / @Elyssa Durant: Check this vid …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Reality Bytes: Is Equal Opportunity Just …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
CyberBUSTED [Reality Bytes] 12/21/2010 0 …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
“to help protect your privacy?” GTFO
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Abscam Operation | Socyberty
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
COINTELPRO targets [ listed under operat …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Whyoming Part I: HOPE
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
How are you feeling today? @yagbebi, 12/ …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
CyberBusted @rockingjude
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Social Security Fraud: Abuse of Process …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Reality Bytes: IN MY COUNTRY
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Haiti/Chile EarthQuake H.A.A.R.P 2010 | …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Rothschild daughter WARNS of bomb attack …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
US Spying on its Citizens | via @FIRETOW …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Wikileaks claims: US did find Iraq WMD | …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
CYBERCRIMES vs. HACKTIVISM KNOW YOUR RIG …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Internet Crime Complaint Center (IC3) #N …
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Oh noes!
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
CyberBusted @rockingjude
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
George Orwell #1984 #quote
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
redemption
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Operation Chaos #payback #FreE
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

Failed
Location data
Reason: request error 403: Invalid AuthSub token. Invalid AuthSub token. Error 403
Next attempt in 6 months
6 months ago

http://bit.ly/reW2dq

LulzSec Calls It Quits: PROPAGANDA #disinfo

hackers

LulzSec Calls It Quits

Avatar for Kwame Opam LulzSec, after having wreaked all sorts of global havoc over the last several weeks, has officially declared that they’re hanging up their top hats. The AntiSec movement that they revived, however, lives on.

Here is the full text of their announcement:

Friends around the globe,

We are Lulz Security, and this is our final release, as today marks something meaningful to us. 50 days ago, we set sail with our humble ship on an uneasy and brutal ocean: the Internet. The hate machine, the love machine, the machine powered by many machines. We are all part of it, helping it grow, and helping it grow on us.

For the past 50 days we’ve been disrupting and exposing corporations, governments, often the general population itself, and quite possibly everything in between, just because we could. All to selflessly entertain others – vanity, fame, recognition, all of these things are shadowed by our desire for that which we all love. The raw, uninterrupted, chaotic thrill of entertainment and anarchy. It’s what we all crave, even the seemingly lifeless politicians and emotionless, middle-aged self-titled failures. You are not failures. You have not blown away. You can get what you want and you are worth having it, believe in yourself.

While we are responsible for everything that The Lulz Boat is, we are not tied to this identity permanently. Behind this jolly visage of rainbows and top hats, we are people. People with a preference for music, a preference for food; we have varying taste in clothes and television, we are just like you. Even Hitler and Osama Bin Laden had these unique variations and style, and isn’t that interesting to know? The mediocre painter turned supervillain liked cats more than we did.

Again, behind the mask, behind the insanity and mayhem, we truly believe in the AntiSec movement. We believe in it so strongly that we brought it back, much to the dismay of those looking for more anarchic lulz. We hope, wish, even beg, that the movement manifests itself into a revolution that can continue on without us. The support we’ve gathered for it in such a short space of time is truly overwhelming, and not to mention humbling. Please don’t stop. Together, united, we can stomp down our common oppressors and imbue ourselves with the power and freedom we deserve.

So with those last thoughts, it’s time to say bon voyage. Our planned 50 day cruise has expired, and we must now sail into the distance, leaving behind – we hope – inspiration, fear, denial, happiness, approval, disapproval, mockery, embarrassment, thoughtfulness, jealousy, hate, even love. If anything, we hope we had a microscopic impact on someone, somewhere. Anywhere.

Thank you for sailing with us. The breeze is fresh and the sun is setting, so now we head for the horizon.

Let it flow…

Lulz Security – our crew of six wishes you a happy 2011, and a shout-out to all of our battlefleet members and supporters across the globe

Along with their fond farewell comes unencrypted internal data from AOL and AT&T, as well as the user information of literally hundred of thousands of users of different provenance. The full leak’s contents are:

50 Days of Lulz.txt 2.64 KiB
booty/AOL internal data.txt 63.6 KiB
booty/AT&T internal data.rar 314.59 MiB
booty/Battlefield Heroes Beta (550k users).csv 24.67 MiB
booty/FBI being silly.txt 3.82 KiB
booty/Hackforums.net (200k users).sql 111.2 MiB
booty/Nato-bookshop.org (12k users).csv 941.8 KiB
booty/Office networks of corporations.txt 3.87 KiB
booty/Private Investigator Emails.txt 2.52 KiB
booty/Random gaming forums (50k users).txt 6.08 MiB
booty/Silly routers.txt 67.7 KiB
booty/navy.mil owned.png 240.51 KiB

http://gizmodo.com/5815546/lulzsec-calls-it-quits

THIS IS DISINFORMATION. THEY PLANNED IT. TOTAL SCRIPT AND YOU FOOLS BOUGHT IT HOOK LINE AND SINKER!

IN TOTO, I TELL YOU RIGHT HERE, RIGHT NOW,

“WOOF! WOOF!’

yours truly,

Just me,

e

@ELyssaD
http://information4sale.blogspot.com/

LulzSec Calls It Quits: PROPAGANDA #disinfo

hackers

LulzSec Calls It Quits

Avatar for Kwame Opam LulzSec, after having wreaked all sorts of global havoc over the last several weeks, has officially declared that they’re hanging up their top hats. The AntiSec movement that they revived, however, lives on.

Here is the full text of their announcement:

Friends around the globe,

We are Lulz Security, and this is our final release, as today marks something meaningful to us. 50 days ago, we set sail with our humble ship on an uneasy and brutal ocean: the Internet. The hate machine, the love machine, the machine powered by many machines. We are all part of it, helping it grow, and helping it grow on us.

For the past 50 days we’ve been disrupting and exposing corporations, governments, often the general population itself, and quite possibly everything in between, just because we could. All to selflessly entertain others – vanity, fame, recognition, all of these things are shadowed by our desire for that which we all love. The raw, uninterrupted, chaotic thrill of entertainment and anarchy. It’s what we all crave, even the seemingly lifeless politicians and emotionless, middle-aged self-titled failures. You are not failures. You have not blown away. You can get what you want and you are worth having it, believe in yourself.

While we are responsible for everything that The Lulz Boat is, we are not tied to this identity permanently. Behind this jolly visage of rainbows and top hats, we are people. People with a preference for music, a preference for food; we have varying taste in clothes and television, we are just like you. Even Hitler and Osama Bin Laden had these unique variations and style, and isn’t that interesting to know? The mediocre painter turned supervillain liked cats more than we did.

Again, behind the mask, behind the insanity and mayhem, we truly believe in the AntiSec movement. We believe in it so strongly that we brought it back, much to the dismay of those looking for more anarchic lulz. We hope, wish, even beg, that the movement manifests itself into a revolution that can continue on without us. The support we’ve gathered for it in such a short space of time is truly overwhelming, and not to mention humbling. Please don’t stop. Together, united, we can stomp down our common oppressors and imbue ourselves with the power and freedom we deserve.

So with those last thoughts, it’s time to say bon voyage. Our planned 50 day cruise has expired, and we must now sail into the distance, leaving behind – we hope – inspiration, fear, denial, happiness, approval, disapproval, mockery, embarrassment, thoughtfulness, jealousy, hate, even love. If anything, we hope we had a microscopic impact on someone, somewhere. Anywhere.

Thank you for sailing with us. The breeze is fresh and the sun is setting, so now we head for the horizon.

Let it flow…

Lulz Security – our crew of six wishes you a happy 2011, and a shout-out to all of our battlefleet members and supporters across the globe

Along with their fond farewell comes unencrypted internal data from AOL and AT&T, as well as the user information of literally hundred of thousands of users of different provenance. The full leak’s contents are:

50 Days of Lulz.txt 2.64 KiB
booty/AOL internal data.txt 63.6 KiB
booty/AT&T internal data.rar 314.59 MiB
booty/Battlefield Heroes Beta (550k users).csv 24.67 MiB
booty/FBI being silly.txt 3.82 KiB
booty/Hackforums.net (200k users).sql 111.2 MiB
booty/Nato-bookshop.org (12k users).csv 941.8 KiB
booty/Office networks of corporations.txt 3.87 KiB
booty/Private Investigator Emails.txt 2.52 KiB
booty/Random gaming forums (50k users).txt 6.08 MiB
booty/Silly routers.txt 67.7 KiB
booty/navy.mil owned.png 240.51 KiB

http://gizmodo.com/5815546/lulzsec-calls-it-quits

THIS IS DISINFORMATION. THEY PLANNED IT. TOTAL SCRIPT AND YOU FOOLS BOUGHT IT HOOK LINE AND SINKER!

IN TOTO, I TELL YOU RIGHT HERE, RIGHT NOW,

“WOOF! WOOF!’

yours truly,

Just me,

e

@ELyssaD
http://information4sale.blogspot.com/

BBC News – Met Police Commissioner Sir Paul Stephenson quits

Met Police Commissioner Sir Paul Stephenson quits

Sir Paul Stephenson announced his resignation in a short, filmed statement

Metropolitan Police Commissioner Sir Paul Stephenson has resigned following the phone hacking scandal.

Britain’s most senior police officer has faced criticism for hiring former News of the World executive Neil Wallis – who has been questioned by police investigating hacking – as an adviser.

He said there were lessons to be learned from the affair, but he was leaving with his integrity intact.

It came after discussions with his employer, London Mayor Boris Johnson.

In standing down, Sir Paul said he had no knowledge of the extent of the phone hacking.

Home Secretary Theresa May said she was “sorry” he had resigned and thanked him for all the work he had done during his time in office.

She said: “Sir Paul has led the force through difficult times and although current circumstances show that there are still serious issues to be addressed, I believe that the force is operationally stronger today now than it was when he took over.”

Earlier, she said she would address MPs on Monday about her “concerns” over the closeness of the relationship between News International and police.

‘Great sadness’

Sir Paul said in a statement: “I have taken this decision as a consequence of the ongoing speculation and accusations relating to the Met’s links with News International at a senior level and in particular in relation to Mr Neil Wallis.”

He added: “Let me state clearly, I and the people who know me, know that my integrity is completely intact.

“I may wish we had done some things differently, but I will not lose sleep over my personal integrity.”

It is expected that Sir Paul’s deputy Tim Godwin will take charge of the Met with almost immediate effect, before the process to find a new commissioner is started.

Prime Minister David Cameron said Sir Paul had enjoyed “a long and distinguished career in the police”.

He added: “What matters most of all now is that the Metropolitan Police and the Metropolitan Police Authority do everything possible to ensure the investigations into phone hacking and alleged police corruption proceed with all speed, with full public confidence and with all the necessary leadership and resources to bring them to an effective conclusion.”

In other developments:

  • Ex-News International chief executive Rebekah Brooks was arrested on Sunday by police investigating phone hacking and bribery at the News of the World. After being held for 12 hours, Mrs Brooks was released at midnight
  • Labour leader Ed Miliband calls for new media ownership rules to limit Rupert Murdoch’s “dangerous” and “unhealthy” concentration of power
  • An advert placed by News International in national newspapers on Sunday describes how the company is “putting right what’s gone wrong”
  • Several Sunday newspapers feature promotions in an attempt to woo former readers of the News of the World, which was the UK’s best-selling newspaper
  • News International says it has set up an independent management and standards committee to see how the company can prevent similar instances happening again
  • John Whittingdale, chairman of the Commons media select committee, says former News International chief executive Rebekah Brooks will probably be spoken to separately from Rupert and James Murdoch on Tuesday when they appear before MPs, adding that the committee should not act as a “lynch mob”

Sir Paul has also faced questions over his stay with his wife at a luxury health spa which employed Mr Wallis.

The journalist was working as a public relations consultant for Champneys spa when Sir Paul recuperated from surgery there earlier this year.

The Met acknowledged Sir Paul had stayed there for free while he recovered from a fractured leg caused by an operation to remove a pre-cancerous tumour and said Sir Paul had been unaware that Mr Wallis had worked as Champneys’ PR consultant.

Analysis

Downing Street sources have denied that Sir Paul Stephenson was forced to resign.

“He was not pushed,” said a source.

The sources also rejected suggestions that Mr Cameron was furious at Sir Paul’s failure to inform him of his connections with former News of the World deputy editor Neil Wallis.

“The PM was not in some rage. He was not furious. He was slightly surprised,” a source added.

Number 10 was taken by surprise by Sir Paul’s resignation and was not informed until about half an hour before his public statement.

Downing Street has also dismissed suggestions that Andy Coulson’s position was in any way comparable to that of Neil Wallis – as suggested by Sir Paul.

In his resignation statement Sir Paul said:” Unlike Mr Coulson, Mr Wallis had not resigned from News of the World or, to the best of my knowledge been in any way associated with the original phone hacking investigation.”

A Number 10 source said Mr Coulson resigned, not as an admission of guilt but because he was editor of the News of the World at the time.

It added that the free stay had been recorded in the senior officer’s gifts and hospitality register, due to be published shortly, when he returned to his post.

Sir Paul said he had informed Buckingham Palace, Ms May and his employer, London Mayor Boris Johnson, about his decision to resign.

He and Mr Johnson had several discussions over the weekend, BBC Political Editor Nick Robinson said.

The mayor also warned the prime minister he was considering serious action.

On Sunday, Mr Johnson said he accepted Sir Paul’s resignation with “great sadness and reluctance” and he had no reason to doubt his “complete integrity”.

He said: “We have got to get on with bringing crime down, and although Paul has done a fantastic job over the last three years, he felt that with the distractions of all these committee hearings, this inquiry, the judge-led inquiry, one thing and another, he was endlessly going to be focused on phone hacking when he wanted to get on with other things.

“So he felt that it would be better to let a fresh pair of hands, fresh pair of eyes, get on with that job, fighting crime, getting London ready for the Olympics rather than being distracted. In the end I agreed to that.”

The chairman of the Home Affairs Select Committee – Keith Vaz – said he was “genuinely shocked” by the announcement.

“He was very keen that people realised that his integrity was intact, and I think what he basically said was, he was concerned about the leadership of the Met at this time,” he said.

“It is a very brave decision, and I’m shocked by it, actually, because I don’t think there’s anything in the statement in particular that points to any wrongdoing or inappropriateness on the part of the commissioner.”

Contract cancelled

Shadow Culture Secretary Ivan Lewis said Sir Paul had made the right decision and done the “honourable thing”.

“He recognises that things have happened on his watch, which mean there will always be questions about his leadership,” he said.

Sir Paul hired former News of the World deputy editor Mr Wallis as a PR consultant for the Met.

His media consultancy company – Chamy Media – was used by the force from October 2009 until September last year.

He was paid £24,000 to work as a two-day-a-month PR, until his contract was cancelled four months before the launch of the Operation Weeting investigation into phone hacking began in January this year.

As part of the contract, Mr Wallis advised the Commissioner’s Office, and the Directorate of Public Affairs and Specialist Operations, working closely with Assistant Commissioner John Yates, who led an earlier Met inquiry into News of the World phone hacking.

UMMMMM….. Paid Disinfo Agent “Ken Doc”.9/11 characters get protected by 9/11 fame seekers | FIRETOWN

With an open mind I have published Let’s Roll Forums: “William Rodriguez – Last Man Out: Discovered a Fraud” and was quite undecided until William Rodriguez, the alleged 9/11 hero replied with the same IP using a different name alleging Phil Jayhan was arrested with a minor.
From that moment on, William Rodriguez stopped replying so when I saw a discussion on a mutual friend’s thread on Facebook, I have decided to ask him the following:

As you can see, it took over 24 hours for William to reply and then my comment was removed by Ken Doc who also runs a large group on Facebook and he defriended me making it impossible to reply further:

In private, Ken acknowledges how William Rodriguez changes his story:

But in public he protects him:

A gatekeeper is a person who controls access to something, for example via a city gate. In the late 20th century the term came into metaphorical use, referring to individuals who decide whether a given message will be distributed by a mass medium.
Wiki

Ken Doc will never go against the bigger names. He will enjoy a role as a truth seeker in the eyes of many and the fact that he backs William Rodriguez shows me he will likely move up.

This is an example of how facts are being blocked.

Any questions?

Popularity: 5% [?]

This entry was posted on Tuesday, March 22nd, 2011 and is filed under Curiosities. You can follow any responses to this entry through the RSS 2.0 feed. Responses are currently closed, but you can trackback from your own site.

16 Responses to “Paid Disinfo Agent “Ken Doc”. How William Rodriguez and other questionable 9/11 characters get protected by 9/11 fame seekers”

  1. Gaddafi

    Well you have no reason to publish private communication without permission. You lost my respect. Of course, this will not be published, correct?

  2. firetown

    As I have just posted in my Facebook group:

    The problem on Facebook is that most of the people who are in some sort of truth leadership position, are hungry for fame and will protect shills knowing that’s their way to the bank:

    How William Rodriguez and other questionable 9/11 characters get protected by 9/11 fame seekers | FI
    http://www.firetown.com
    15 minutes ago · Like · · Share · Unsubscribe
    Mitchell Launes Ford likes this.
    Michael Dammann and yes, i did publish his private message to me, and no: do not trust me. If you protect shills that is.

  3. Gaddafi

    Well it seem you have the same problem, judging by the photos on your profile on FB. You seem to like to be “famous”. No, I do not trust you or anybody else for that matter. You may be the biggest shill here for all I know. Keeping screen caps of this in case is not published ( I learned from you!).

  4. firetown

    How about you go ahead and ask William the question I did if you claim to seek truth.

  5. Brian Good

    People are afraid to challenge Willie because he and his supporters libel those who do. They are also reluctant to be perceived as making an ugly personal attack on one of our own.

    It is not a personal attack to call someone out for his lies. And how can someone claim to be one of us in the truth movement when his status is based on lies and fraud?

    Many of those in the movement who know Willie is a liar go easy on him, minimizing the importance of his discrediting behavior and rationalizing their conflict-avoidance as service to movement unity. Willie’s very corrupting effect on the movement’s integrity may have done more damage to us than his degrading of our credibility has.

  6. ElenQ

    @Brian Good, aren’t you the alledge famous sex stalker in Love with Rodriguez? Sorry for asking, but doesn’t most of the real leaders of the 9/11 movement wants nothing to do with you? I did google your name and was surprised! So your attacks on others have no validity with me. You should learn to respect women and for that matter, married ones! I guess everybody is saving screen shots saved here!

  7. firetown

    Who are the real leaders? Alex Jones? Also: Please post a link to the proof of any allegation you make towards people in here.

  8. Brian Good

    ElenQ, I have humiliated Dr. Barrett many times–even on his own blog–by exposing his lies, incompetent scholarship, juvenile sense of humor, blatant bigotry, faulty logic, and irresponsible violence-fetish.

    Since he can’t refute me using real facts, he tries to discredit me with invented claims. In Barrett’s last TV interview (I hope it’s his last, and very likely it will be) on 9/11/09 for Russia Today he lied four times in the first four minutes. Allegations are easily made, and once made, difficult to retract. I was thus very slow to accuse William Rodriguez of lying, and didn’t do so until I could prove it. I don’t think I’ve ever seen Barrett admit he was wrong, ever, and I don’t expect I ever will.

    The ones who need to learn to respect women are the narcissistic, pathological liars Barrett and Rodriguez, who have done enormous damage to the credibility of the truth movement and who, when called on it, lie, and hide behind the skirts of a woman.

  9. Anon

    Hey Mike, Why did you bail on the show tonight. You had your chance to confront William and you ran like a coward.

    and BTW, it’s screenshots like this which prove you are not to be trusted by anyone.

    Last point – Quit posting disinfo on your site. You are only showing everyone your shill colors.

  10. firetown

    “Hey Mike, Why did you bail on the show tonight. You had your chance to confront William and you ran like a coward.”

    http://www.firetown.com/blog/2011/04/02/my-apologies-to-the-listeners-at-free-think-radio/

    You’re calling me a coward while you are too afraid to use your real name commenting? Hilarious.

    “and BTW, it’s screenshots like this which prove you are not to be trusted by anyone.”

    I cannot be trusted by people who have no character and protect potential frauds. I can also not be trusted by two faces who mislead the public intentionally.

    “Last point – Quit posting disinfo on your site. You are only showing everyone your shill colors.”

    Very common comment from the Alex Jones type crew. Give an example or be happy with the check you cash.

  11. Anon

    “I will inform you when my access will be completely restored and hopefully the conversation can be continued”

    Fully restored? Thats a cop out. and you know it.. Your connection seems to be just fine as you are posting on your own website.

    “I cannot be trusted by people who have no character and protect potential frauds.”
    So now you are saying “potential”. Get over yourself loser. You said you had proof that William is a NWO shill. Now you are saying “potential”. You are the only fraud here.

    Now as for disinfo all over your site…….

    9/11 Pentagon Impact Captured From Helicopter
    http://www.firetown.com/blog/2011/03/16/911-pentagon-impact-captured-from-helicopter/

    I think you should watch the video’s you release because if you watch the “missile” from the helicopter….. any fool can see that it is a fake. Look where that “missile” impacted the Pentagon and match it up to the real hole.

    You are disinfo and I will call you out.

    Next time, you better …… “put up or shut up”

    Damann is a fraud to the movement.

  12. Anon

    “Jayhan has bad teeth.”

    Are you kidding me dude? Is this all you brought with you last night?

    You are a joke. Stop attacking real truthers and start attacking those that pulled off 9/11!

  13. firetown

    Sorry boy, reveal your identity before you talk to me. Unless you are Ken Doc yourself.

    Country: Canada
    State/Region: Ontario
    City: Toronto
    Latitude: 43.6667
    Longitude: -79.4167

    http://www.facebook.com/people/Ken-Doc/100000214085869

    Same city?

  14. firetown

    There is a difference between making a mistake and misleading people intentionally, Ken. I have made a mistake and it’s evident from the screenshots above that you have been misleading your followers fully knowing and 100% intentionally.

    A “real truther”?

    You are a clown, Ken and you got caught with your pants down. Deal with it. Nobody reading this will ever look at you the same.

    You are calling yourself a TRUTHer when it’s proven now that you think one thing and say the opposite? Wow, I sure hope they’re paying you well.

    Otherwise this would make you one hell of a gutless worm.

    The funny thing is I was trying to talk with you back then, but you defriended me to protect William. You and people like you are the reason why it is so easy for celebrities to lie to people. You are the voluntary gate keeper.

    Added: In the past few days, “Ken Doc” has created several aliases in order to flood this post with attacks while avoiding responses towards his public outing as a spineless fraud as proven in this post. If you wish to talk about this, please pass on the information to your friends to help them become aware of his lack of trustworthiness.

    The commenting section is now closed. If you want to get deeper into this subject, put him on the spot on his profile and ask him why he wants to protect someone else’s lies while claiming to be a truth seeker and why he promotes We Are Change and encourages people following heroes and submitting themselves to the program of an organization rather than standing up on their own.

    My work is done. Go get him :)

  15. Anon

    “Nobody reading this will ever look at you the same.”

    You have no clue do you. I can;t wait for Chris to give me the audio from last night so I can post it for everyone to hear!

    I am the one with nothing to hide, you are. You proved that by ducking from the show and blaming it that your computer crashed while you were still making posts on FB.

    “The funny thing is I was trying to talk with you back then, but you defriended me to protect William..”
    Who are you and how did you get on my list to begin with? I am very close with a large portion on my list. You have never contacted me before this at all. The day I added William was the day you started attacking me! You are the one accusing people of being NWO shills with ZERO evidence.

    Anyways, your days are up. You have been exposed as a disinfo agent. How? by continuing to post misleading links and articles on this site!

    Helicopter shot of the missile…… Who are you kidding? The “missile” didn;t even hit the same spot. LOL

  16. firetown

    “I am the one with nothing to hide, you are. ”

    You cannot even use your real name when commenting, you clown.

oh this could be fun! pot, kettle, black! FUCK YOU FIRETOWN!

BBC News – Mobile ‘pinging’ claim raises legal questions

A former News of the World journalist’s allegation the newspaper paid police to track mobile phones raises serious questions about the UK’s eavesdropping laws, according to experts.

Sean Hoare said it was possible to “ping” a handset’s location for £300.

While there is no firm evidence to support the accusation, if true it would undermine safeguards within the Regulation of Investigatory Powers Act.

The law outlines a system of checks intended to prevent it being abused.

Police can ask mobile networks to determine the location of a phone, based on information from nearby radio masts.

Only a handful of officers in each force is authorised to make such enquiries, and their requests are supposed to be approved by a senior colleague.

Poor compliance

The system is regulated and audited by the Interception of Communications Commissioner, Sir Paul Kennedy.

In his most recent report, Sir Paul found in 10% of cases where law enforcement bodies sought communications information, there was poor compliance with the rules.

Such audits are based on a sampling of police requests – something that leaves the system open to abuse, according to solicitor advocate Simon McKay, author of Covert Policing: Law and Practice.

“The resources of the commissioner empowered by statute to review it are fairly restrictive, so circumstances dictate that a tiny proportion of authorisations obtained will ever be reviewed meaningfully or critically by the commissioner,” he told BBC News.

Mr McKay added he would not be surprised if leaks had been made in return for cash.

Pinging

Mobile phone networks have the ability to locate their customers’ handsets.

At a basic level, they can determine which cell the phone is using. In a city, that might narrow-down the location to a few hundred metres. In the countryside it could be several kilometres.

It is also possible to triangulate the position of a phone more precisely using its relative position to several masts.

Additionally, many modern phones contain GPS technology to help determine their exact longitude and latitude.

Mobile operators are reluctant to discuss exactly what level of detail they are able to provide to law enforcement, although there are examples of police tracking criminals, accident victims and missing persons by their mobile phones.

“You are generally dealing with people that are experienced in using and deploying covert policing techniques and therefore their tradecraft equips them particularly well to minimise the risk of detection,” he said.

Freedom law

A new law, currently being considered by parliament – the Protection of Freedoms Bill – would require judicial approval for some Regulation of Investigatory Powers Act (RIPA) disclosures, but not those requested by police.

The BBC approached the government to see if it planned to ask Sir Paul to re-examine the safeguards around police use of RIPA.

A Home Office spokesman said it would not be taking such action before the prime minister had outlined the terms of reference for his two enquiries into the phone-hacking scandal.

Daniel Hamilton, the director of campaign group Big Brother Watch, said he was happy to wait, provided there was eventually a review.

“I would have preferred if action had been taken earlier and intercepts had not been used on such a wide basis, but I think it makes sense now an inquiry has been set up and we have received assurances from the PM and the police that there will be a thorough investigation.

“I hope at the end it will be an opportune time to revisit these processes,” he said.

http://www.bbc.co.uk/news/technology-14141809

Lessons from LIGATT

Lessons from LIGATT

Monday, July 11, 2011

Contributed By:
Ben Rothke

D9d968536525db2cf6ac805403260d61

I have been writing book reviews on information security and technology books for quite a while.  Topics such as authentication, security design, operational resilience, biometrics and security policy are rather tame and most of the reviews don’t generate a huge amount of controversy.

In fact, before June 2010, no book review I wrote ever lead to being interviewed by a major network for an expose of theirs, or a personal attack by the author (including being called a racist and a stock basher) against myself, Chris John Riley, Sam Bowne and others.  These critiques by aforementioned and others were never a personal issue, and this article is simply a record of lessons learned.

Writing book reviews is something I do as a pastime, and with that, I generally refrain from writing negative book reviews.  But occasionally, some books are so problematic that one can’t remain silent. 

That is what lead to my June 2010 review of How to be the World’s #1 Hacker, written by Gregory D. Evans of LIGATT Security International (and SPOOFEM.COM and High Tech Crime Solutions Inc.). I demonstrated (as did Brian Baskin) that significant amounts of the book were plagiarized. This was based on the use of the iThenticate service.  iThenticate is one of the leading plagiarism detection services that provides impartial content analysis.  I published the book review and thought that was the end of it. 

For those who need a briefing on the LIGATT saga, Attrition notes that Evans describes himself as a hi-tech hustler, The World’s No. 1 Hacker and a convicted felon. Attrition further writes that Evans has invented himself as some form of hacker with the ability to break into anything and spin that supposed knowledge into advising companies on security.

It is the common opinion of industry experts that Evans and his company have little real knowledge beyond pedestrian hacking techniques found in plagiarized books and beginner hacking texts. LIGATT offers products that are simply bloated version of common tools such as ping and nmap.

Due to a variety of unexpected events that took place, my book review did not simply end there. I ultimately learned a considerable amount about a number of topics, from fair useto securities law and more, and met a lot of smart people along the way.  I would like to share those lessons with you.

Twitter is a powerhouse for action

Details

From as early as 2009, the use of Twitter for organized student protests significantly changed the dynamics of mass communications.  In 2011, we saw the use of Twitter to overthrow the corrupt Tunisian government and fight the oppressive Syrian regime.  Twitter is indeed a powerhouse for action. 

Twitter and other social media outlets are changing the way business and marketing are done.

Lesson

While Fox, Bloomberg and other media outlets had Evans on their show, Twitter was often the medium for those that did not view Evans as the number 1 security expert to get the word out via the #Ligatt hash tag.  People and organizations such as Attrition, 0ph3lia, Sam Bowne, Marcus Carey, Chris John Riley and krypt3ia used the #LIGATT hashtag to get their message across.

Self-publishing

Details

Indie movies came about due to the frequent inability for smaller movie producers to get the attention of the major studios. When it comes to books, self-publishing is often a great way to bypass traditional publishers and quickly get a book into print.

But with that ability, many authors will self-publish; bypassing the editing, fact checking and rigorous plagiarism checking that a traditional publishing house will typically perform.

Rich O’Hanley, publisher at Auerbach Publications and CRC Press, notes that plagiarism continues to plague both his firm and the entire industry, thanks to the self-publishing and the web, and its ethos that information should be free. The reality is that it is far too easy for authors to use whatever is available.

O’Hanley is not sure if the motivation to plagiarize is driven by ignorance of copyright rules, or simply the perception that they won’t be caught.  Even authors whose careers predate the web, fall victim to this and use material they can cut-and-paste that they likely wouldn’t use if they had to retype it.  CRC Press has tightened the whole permissions process, but it’s still a matter of trusting the author and his or her attestations. 

Lesson

Had How to be the World’s #1 Hacker been sent to a traditional publisher, it likely would have been flagged immediately and never allowed into print.

Evans has claimed in interviews and self-made YouTube videos to have had permission from the sources he used.  But as of July 2011, he has yet to show a single document, email or contract that entitled him to re-publish the works of others.

Fair use

Details

The US judicial system (see 17 U.S.C. § 106 and 17 U.S.C. § 106A) allows for the fair use of copyrighted content. While there is no definitive level of where fair use ends and plagiarism begins, How to be the World’s #1 Hacker crosses the line according to a reasonable assessment of what fair use is.

In An Independent Plagiarism Review of How to Become the World’s No. 1 Hacker, Brian Baskin noted that you will find that many of the references are from NMRC; a site run by Simple Nomad. Simple Nomad developed the basic structure that Evans used to plan his table of contents, as well as originally developed the material used by Evans in his book. This was excellently written material, but is dated originally from 2000.

What Evans also did was modify some of the text that Simple Nomad wrote, to make it look like he was in fact the true author.

Ron Coleman, Partner, Head of Intellectual Property Department at Goetz Fitzpatrick LLP and general counsel of the Media Bloggers Association, notes that even seasoned attorneys are often at sea about where a quotation crosses the line from fair use to copyright infringement. 

Coleman observed that “fair use is a very fact-specific inquiry, where courts are often asked to weigh a lot of factors at the same time.  The tricky part is that while judges are making very subjective decisions about liability, the copyright statute is designed — with mandatory awards of attorneys’ fees and in some cases of statutory damages — to punish every infringer as if he knew in advance how that equation would come out.  In the close cases, that’s simply impossible.”

Lesson:

Before I wrote my review, I was not aware of the fine details of fair use With How to be the World’s #1 Hacker, objective analysis demonstrated that there was lot of use, and very little of it fair.

Copyrights

Details

A copyright is a set of exclusive rights granted by a state to the creator of an original work or their assignee for a limited period of time in exchange for public disclosure of the work. This includes the right to copy, distribute and adapt the work. 

Without copyright protection, most artists and authors would not create music or books, if their works could not be protected.  With that, copyright owners have the exclusive statutory right to exercise control over copying and other exploitation of the works for a specific period of time, after which the work is said to enter the public domain. Uses covered under limitations and exceptions to copyright, such as fair use, do not require permission from the copyright owner. All other uses require permission.

The notion of a copyright has its roots in the United States Constitution; where it states in Article I, Section 8, Clause 8 (known as the Copyright Clause) that empowers the United States Congress to “promote the Progress of Science and useful Arts, by securing for limited Times to Authors and Inventors the exclusive Right to their respective Writings and Discoveries”.

Lesson

As detailed in Gregory D. Evans, Copyright Violations for Over a Year, Evans has been plagiarizing content for his Twitter feed and associated web sites, here and here  

The copyright violations are that the LIGATT sites scrape entire news articles, including the graphics, without permission. While LIGATT ultimately gave give credit to the original source at the end of the article; that does not justify what he is doing or make it legal. Reproducing an entire piece of work without permission is a copyright violation.

One site LIGATT scraped a significant amount of content from is the Krypt3ia blog.  Note that the following statement on the blog site leaves little room for ambiguity:  All content of this site is copyright of Krypt3ia (Scot A. Terban) and not to be copied unless express consent is given in writing by its author.  LIGATT never received permission to use the content.

Blog owner Scot Terban observed that “it seems to be the standard of practice on the LIGATT sites that no original content is ever posted by Mr. Evans.  There are quite a few PR pieces and links to interviews he has done in the past.  But as far as his own original content, there is none.   Instead, there is an overabundance of scraped content from well-known information security web sites and noted authors; many of whom likely don’t know that their content has been copied”.

Penny stocks

Much of the spam you get is around weight loss and various schemes to make money.  Rarely will a day go by that you won’t receive numerous spam emails touting a hot stock tip.

Often these emails are used in pump-and-dump schemes (P&D).  The US Securities and Exchange Commission (SEC) define P&D as “the touting of a company’s stock (typically microcap companies) through false and misleading statements to the marketplace. After pumping the stock, fraudsters make huge profits by selling their cheap stock into the market”.

Since most of these companies being pumped are listed on the Pink Sheet (an unregulated market), a stock moving up just one cent (since these companies have as many as 5 billion shares of stock or more) can bring significant money to those pumping it, when they finally dump it.

How to Identify a Pump and Dump Stock Scam notes that if the stock trades on the OTC (Over The Counter) or Pink Sheet Exchanges, it is often an indicator of a scam. Stocks traded on these exchanges do not fulfill the rigorous requirements of the NYSE, NASDAQ, or American Stock Exchanges.

In Tips To Identify Pump And Dump Schemes at Motley Fool, a few quick tips to help identify P&D schemes are to:

  • look at the structure of the company
  • examine the trading and price history
  • take a close look at the founders of the company (previous experience, background, etc.)
  • look at the percentage ownership of the company (insider, retail, institutional)
  • look at any VC investors that have made investments in the company

Harry Domash writes in Beware of pump-and-dump stocks that promoters pump the stock by issuing copious media releases announcing the firm’s entry into a variety of promising businesses.

Domash notes that in truth, it is relatively easy to spot these risky stocks and lists six checks you can use to quickly rule out dangerous stocks, whether pump-and-dumpers or just bad ideas. He suggests ruling out any stock that fails to meet the following:

  1. Last price above 50 cents
  2. Last-quarter sales at least $10 million
  3. Market capitalization at least $50 million.
  4. Institutional ownership at least 15%
  5. Debt/equity ratio less than 3
  6. Maximum price/book ratio of 30

Ryk Edelstein, veteran entrepreneur and CEO at Cicada Security Technology has seen the dark side of P&D, having observed a well-intentioned business owner partner with less well intentioned partners who offered a promise of riches and success by simply letting them take the company public. To those in the high tech sector, there is no shortage of charlatans who will approach unsuspecting business owners, stoking their egos, and appealing to greed.

Consequently, as in the case of the well intentioned business owner, at the end of his partner’s cycle of P&D, he was left sucked dry holding a valueless corporate shell, debt, and facing the prospect of serious legal repercussions.

Lesson

Like many companies listed on the pink sheets, LIGATT (while not necessarily a P&D stock) seemed to consistently use myriad press releases as a method of garnering attention to the company, which would ostensibly serve to increase the perceived value of the company.

LIGATT press releases are somewhat unique in that many of them are unidirectional; in that the other party does not issue a corresponding press release.

One of countless examples of bidirectional press releases is the June 2011 strategic partnership of Juniper Networks and OnLive under which Juniper will be the exclusive networking provider for OnLive’s network infrastructure.  This was announced on both Juniper’s web site and correspondingly on OnLive’s web site.

When it comes to LIGATT, I could not find a company or organization mentioned in their press releases that has reciprocated with a similar press release.

 Notice the following:

Regulation has its limits

Details

Even with SOX, GLBA and other regulations, the consumer and investor ultimately can’t be fully protected. The finance system and financial markets in this country are so complex, with so many layers and with so many interrelated parts, that it is ripe for abuse.

Even with the SEC in place to regulate such entities, publicly traded companies on the Pink OTC Markets (Pink Sheets) are lower priority for investigations, for many reasons. 

Even the Food and Drug Administration (FDA) often finds itself limited, even with its regulatory powers.  As I wrote in New York News Radio, the Voice Of Bad Science, for the consumer, whenever they hear the following mandated FDA disclaimer, they should immediately be suspicious:  These statements have not been evaluated by the Food and Drug Administration. This product is not intended to diagnose, treat, cure or prevent any disease.  After such a disclaimer, an able person should ask himself or herself, if the product is not intended to diagnose, treat, cure or prevent any disease, why use it?  Nonetheless, even such regulatory disclaimers seem to go in one ear and out the other of most consumers.

Part of the reason regulation won’t work is that an investor with an insatiable appetite for profits, often finds that their ability to reason is occluded.  Combine this with the flash of mega-gains that the P&D maker’s supply and people will invariably find themselves on the losing end of the deal, with no recourse in which to recoup their losses. 

Corresponding to what Ryk Edelstein observed earlier about the well-intentioned business owner; there are many entities required to make a P&D work; from lawyers, securities underwriters, transfer agents and much more.  Any regulation that would encompass all of the myriad entities would have to be so draconian as to stop all market activities.  And such a thing will never happen.

Lesson:

Even with the many LIGATT lawsuits, including many frivolous cases filed by Evans, the most recent case on April 11, 2011,the legal case LIGATT filed was thrown out of court and the firm ordered to pay over $29,000 in legal costs to the other party. 

With all of this, as of July 2011, the SEC has not announced any sort of investigation against LIGATT.  Nor have any securities lawyers I consulted said they expect any investigation against the firm any time soon. 

Pink sheets are not for girls’ beds

While there is the NYSE, NASDAQ and other reputable exchanges, it should be noted that the Pink Sheets is not a stock exchange. In fact, firms have very little requirements in order to be quoted in the Pink Sheets.  Since many of these firms do not submit timely financial statements, nor perform third-party audits, it makes it difficult for the investor to really understand what they are getting into.

It is questionable why any novice investor would want to invest in a firm that can’t afford or won’t submit an audited financial statement. It is for these reasons and more, that Pink Sheet firms are extremely risky. Read: a place where naïve investors can lose their entire investment quickly and effortlessly.

This does not mean to imply that all Pink Sheet stocks should be avoided, as there are certainly many legitimate Pink Sheet companies.  Many are smaller firms with legitimate intentions of starting small and growing big.  But given there are so many that are not like that, the novice investor in the Pink Sheet market is going down a road fraught with financial risk.

Much of the hype of some of these Pink Sheet companies is often based on the charisma and hyperbole of the financial people and executives at the companies. Uneducated and unsophisticated investors, who lack the most basic financial wherewithal and fail to perform due diligence, become victims to these charlatans.

As noted in the previous paragraph, the very nature of Pink Sheets means they can never be fully and properly regulated. With that lack of common financial sense of basic investors, and Barnum’s observations, those people are for the most part doomed to losing their investment. 

Investors who are not comfortable with the underlying mechanics of how the financial markets operate should consider the pink sheet market just like a Vegas Casino; where the odds are stacked against them from the start. 

A market maker who works in the pink sheet world succinctly told me that “these stocks are garbage.  You buy a stock for a half a cent and hope if goes to a penny”.

Lesson:

LIGATT (LGTT.PK) is a pink sheet stock, better known as a penny stock. As to LIGATT and Pink Sheets, the following screen shot says it all:

Rothke-Ligatt 1

On any given day, hundreds of media outlets need content to fill their airwaves.  Radio stations, newspapers, periodicals and a never ending supply of cable channels need people they can interview on the air to use for external expertise.

Over the last year, LIGATT PR solicited numerous media outlets, who in turn had Evans appear as an expert and provide commentary.  Just a few weeks ago, their PR department sent the following email to many media outlets (click image to enlarge):

Rothke-Ligatt 2

Lesson

Numerous media outlets had Evans on air, irrespective of his false associations (Atlanta Hawks, Atlanta Thrashers, Los Angeles Clippers, Phillips Arena and more), false certifications, and authorship of plagiarized books to make him seem like he was indeed the “worlds #1 hacker”.

With that, one can pose the question – if the  major media outlets such as Fox, CNN, Bloomberg, et al, can’t get it right with a guest on technology, what does that say about their approach for foreign policy, investment news and more pressing concerns.

While the major media players ignored Evan’s qualifications, it is worth noting that the smaller media outlets such as The Register, Tech Herald  and CBS Atlanta affiliate did run exposes about the firm and its titular #1 hacker.

Racism in the USA

Not a Miley Cyrus song, but racism is a serious transgression.  It wasn’t that long ago that an African American couldn’t use a public restroom or drinking fountain in this country.  These racist inequalities were the driving force behind the establishment of the NAACP and other such organizations. 

In the 100 years since the founding of the NAACP, a lot has changed.  Take a look at the former Secretary of State, the current President and Attorney General; it is clear that state-sponsored racism is no longer an issue.

Perhaps fighting racism is no longer the raison d’être of the NAACP.  To a degree, the organization has been reduced to a business that produces the NAACP Image Awards.

The irony is that in March of this year, the NAACP had its image tarnished, as it found itself on the receiving end of a boycott, since Kid Rock received the NAACP Great Expectations award at the Detroit NAACP gala.

This award caused a dispute by some who believe that he should not have received the award.  Their opinion is that he is an inappropriate choice given his affiliation with the Civil War-era Confederate Army flag, which has been adopted by white supremacists, and have irked many civil rights activists. In fact, some supporters of the civil rights organization boycotted the annual fundraiser on May 1 because of the issue.

The singer has argued that the flag stands as a symbol of southern rock and roll, but many protesters don’t quite see it that way.  Dr. Boyce Watkins, Professor at Syracuse University writes that if anyone ever wants to understand why so many in the black community have lost faith in certain elements of the NAACP, you need to look no further than this incident.  He notes that It’s one thing for the NAACP to remain quiet about Kid Rock’s use of one of the most traumatic symbols in American history, but quite another for them to step up and give him an award for it.

Lesson

The NAACP presented Evans with its NAACP humanitarian award in 2002.

But LIGATT used press releases to accuse respected professionals who did deeper investigations and analysis into its activities of having a racist agenda and being some of the world’s worst cyberbullies.  Some examples include a blog posting in June 2010, How Can Computer Nerds Be Racist, where LIGATT accused this author and Chris John Riley of being racist, and emphasized the claims that criticism leveled at Evans’ and LIGATT are all racially motivated.  

For a full account, see Security firm fights racism in InfoSec while apparently profiting from it and World’s No. 1 hacker’ tome rocks security world – Plagiarism, racism, and fake Mitnickism alleged.

LIGATT even accused CBS Atlanta of having a racist agenda when they ran an expose against the firm.  While CBS Atlanta posted the response from LIGATT, it was somewhat ironic that portions of the response had to be redacted because of racially offensive language from LIGATT themselves.

Yet when his charges of racism where brought to the attention of the NAACP, they did not seem receptive to the issue, nor did they revoke the award.  Furthermore, despites our attempts to contact them they never return a phone call or replied to email.

Despite numerous emails, phone calls, conversations with the executive assistant to the president of the NAACP, or messages directly to the President of the organization would be invoke even the gesture of a courtesy reply. 

But big organizations have politics and bureaucracies like the best of them.  As for the NAACP, I was disappointed to see the organization ignore a complaint about one of their award winners making baseless accusations of racism.

Conclusion

I am currently writing a review on a book about cloud computing.  Something tells me (and I certainly hope) that it won’t be as much as an adventure as this review was. On the upside, I learned a lot more by writing the review than by reading Evans’ book. 
 
 

Ben Rothke CISSP, CISA (@benrothke) works in the information security field, writes the Security Reading Room blog and is the author of Computer Security: 20 Things Every Employee Should Know (McGraw-Hill).

https://www.infosecisland.com/blogview/15064-Lessons-from-LIGATT.html

Google is Your Friend – If You’re a Lulzer

Google is Your Friend – If You’re a Lulzer

Wednesday, June 29, 2011

Contributed By:
Kevin McAleavey

Ba829a6cb97f554ffb0272cd3d6c18a7

While the digital paparazzi were lined up waiting to snap photos of the Lulzboat crew getting vanned, some of us focused on how this collection of low tech script kiddies were able to knock over SONY, AT&T, the CIA, Arizona’s DPS and numerous other sites and make off with highly confidential contents again and again.

It turns out that they had an accomplice, Google. Now before the good townspeople grab their torches and pitchforks and beat a hasty path to Mountain View, let it be known that Google’s part in these massive hacks isn’t actually Google’s fault.

Or perhaps it can be if the public still wants to blame them anyway and question why this information is there on Google for the taking in the first place. But that’s not really the issue at all.

The blame in my opinion lies once again with the administrators of the sites which were attacked. Google merely indexed the available booty for the lulzers and others and left the cardboard box on the curb where it could be picked up by anyone who drove by.

After all, page crawls weren’t considered privileged information – they’re all part of the “public internet” available to anyone who drops by.

How could this be? How could Google allow these kids to troll the internet and easily locate SQLi vulnerabilities or remote logins, passwords or even entire databases for the taking without any real effort at all? Simple.

A little thing known as SEO, sitemaps and the little spiders that go bump in the night. Let’s look at the problem, along with a few specifics since the bad guys have been doing this for years and years and it’s not a secret at all. Then I will explain what site admins can do to see to it that this information is not left at the curb any longer.

The problem:

Copy and paste the following into a Google searches in a new window. I’ll wait:

filetype:sql hotmail gmail password

or

inurl:”login.(asp|php) inurl:”id=1”

You can try the above and substitute any of these too:

    * userid=
    * index=
    * form=
    * username=

You might even see some major security companies and governments turn up in there. For extra credit, use the “site:your website url here” and see what comes up on yours!

THIS is what the script kiddies do when they do their Google drive-bys. The victims of lulzsec and others fell because of such simple Google searches, and they’re made even easier when you have a target URL in mind to play “anybody home?”

As long as Google has it in their indexes, and you know the keywords to search for sites, then it certainly isn’t “nuclear brain science” when an injectable site is found.

There’s plenty of tools to automate the attacks on the database behind the site once you know how to POST or GET to it. I’ve seen apologists claim “we don’t use MYSQL.”

Rest assured that there are exploit GUI’s readily available for PostgreSQL, MSSQL and Oracle as well as lesser and older databases. If it’s there, and they can find it, and they can talk to it, and you’re not properly filtering what can get to it, your site could very well be the next breaking news story.

The Solution

Search results on Google come from two primary methods. The first one is web-crawlers which may or may not respect your “robots.txt” file in your website’s root. Most webmasters are well aware of the rules for “robots” but can’t always be expected to be aware of what dynamic web pages could contain from other parts of their site’s backend.

Therefore, some dynamic content might end up not being in the “robots.txt” file to be skipped in the first place. It is essential that those responsible for web sites ensure that the golden rule of “if you don’t want people to see it, don’t put it on the site in the first place” is properly enforced.

Some more “l33t” hackers have written their OWN webcrawlers and you cannot count on these critters to obey your “robots.txt” file in the first place. Google does usually, but don’t count on it EVER. There’s plenty more spiders in that basement and Google is but one of them.

The biggest risk of all though is SEO (“Search Engine Optimization” for my pointy-haired readers). It involves the creation of sitemaps using either Google’s own sitemapping tool, or risking using a third party SEO tool which will truly map everything it can find and then wrap it all up into a nice little XML file that the webmaster uploads to all the search engines.

Incredibly, a lot of not-so-experienced webmasters will run the SEO tool and never look at the final output file before sending it! If the XML indexes your databases or scripts, they’re all part of your sitemap ready for lulzing. PLEASE check your sitemap information before sending it, please?

Your Homework

Yes, there WILL be a test. And it will go down on your “permanent record.” Some useful reading on how your databases can be hit can be found here:

Google even has some nifty tools with which you can test your injectability quotient:

Bottom line: If you don’t want pirates on your poopdeck, remember the golden rule. If it’s ON your website, it’s there for the pickings. Do NOT toss your company’s wallet on the sidewalk and expect it to be there intact the following morning.

Know what’s on your website, know what’s being indexed and be certain that anything you don’t want anybody else to own isn’t there in the first place. Kinda depressing to even have to say any of this. May the lulz be your own, and not some idiot children with no leet in them at all.

About the author: Kevin McAleavey is the architect of the KNOS secure operating system ( http://www.knosproject.com ) and has been in antimalware research and security product development since 1996.

https://www.infosecisland.com/blogview/14829-Google-is-Your-Friend-If-Youre-a…