Wikipedia:Requests for checkuser/Case/Willy on Wheels

From Wikipedia, the free encyclopedia
If you are creating a new request about this user, please add it to the top of the page, above this notice. Don't forget to add
{{Wikipedia:Requests for checkuser/Case/Willy on Wheels}}
to the checkuser page here. Previous requests (shown below), and this box, will be automatically hidden on Requests for checkuser (but will still appear here).
The following discussion is preserved as an archive of a Request for checkuser. Please do not modify it.

Willy on Wheels[edit]

Willy888 (talk+ · tag · contribs · deleted contribs · logs · filter log · block user · block log · CA · CheckUser(log· investigate · cuwiki)

This user only created a user page, but I am very suspicious of this user. Bushcarrot (Talk·Desk) 02:02, 28 December 2006 (UTC)[reply]

fish CheckUser is not for fishing. Dmcdevit·t 08:32, 28 December 2006 (UTC)[reply]


Willy on Wheels[edit]

This vandal is creating attack usernames that are offensive towards me, as a result of my reporting of vandals at WP:AIV. Can you find out if it is an open proxy, and if so, block?? --TheM62Manchester 14:36, 28 August 2006 (UTC)[reply]

Done. Mackensen (talk) 15:20, 28 August 2006 (UTC)[reply]

What's the IP?? --TheM62Manchester 15:23, 28 August 2006 (UTC)[reply]
I think I am right in saying that checkuser information is not normally released except under exceptional circumstances. — FireFox (talk) 15:52, 28 August 2006
You are right; however, open proxy IP addresses ARE released. --TheM62Manchester 16:06, 28 August 2006 (UTC)[reply]
You're free to go look in my block log over the past day. Mackensen (talk) 11:22, 29 August 2006 (UTC)[reply]


Willy on Wheels[edit]

A user responsible for a number of blocked WOW socks has been going from one sock's talk page to the next posting the {{unblock}} template with the reason "I wish to write attack pages on the following: [insert names of various Wikipedians]". I noticed it because it triggered the IRC bot that notifies of any use of {{unblock}}; I've cleaned what I've found of it up, and after about the fourth one, I checkusered the accounts, determined them to be all from a single IP, and blocked it for six months. I don't expect any collateral damage (it appears to be fairly static) but just in case, it's 82.42.145.158. I strongly recommend against unblocking it unless a legitimate Wikipedian is affected; this vandal is having fun doing WOW moves and then causing trouble via thier talk pages once blocked. I don't doubt for a second they would try to instigate a wheel war over good-faith unblocking. Essjay (TalkConnect) 09:45, 5 July 2006 (UTC)[reply]

Didn't even get this message saved before he was at it: User talk: 82.42.145.158. Strongly urge against unblocking. Essjay (TalkConnect) 09:49, 5 July 2006 (UTC)[reply]
Oh, the story doth get better! After being denied the unblock via the IP's talk page by User:Bookofjude, he's now attempting to use a doppelganger, User talk:Sunholm1 to deceive someone into unblocking him. Why deceive? Because if he posted it from his actual account, User talk:Sunholm, the unblocking admin might see http://en.wikipedia.org/wiki/Special:Log/block?page=User:Sunholm and realize who he is and what he's been doing. (As User:Firefox did when denying the unblock).
At this point, I think there it's a good idea to discuss what to do with Sunholm & Sunholm1, as he's proven, beyond a shadow of a doubt, that he is the same user that has been doing the WOW vandalism; I held off on saying anything about those accounts because I had a strong feeling he would use them in a manner that would make a public connection between the WOW vandalism and the other accounts. I suggest indefblocks on both, but of course, yield to the judgment of the community. Essjay (TalkConnect) 10:46, 5 July 2006 (UTC)[reply]

btw sun holm is not like user:poolguy he seems to be good editor. i am probably what you call 'mete puppet' and think we should not complain. sunholm is not vandal. see notices on talk page for info. btw he is good user. see WP:ER on editor review it is chance to give sun holm some feedback. may be i am right. please try and see positive light of situation rather than try accuse him of being vandal. he is not sock puppet of any one. he has alternate account for if he use public terminals (which he does in frequently). i would hope u could be nice to him. he isnt wow whoever wow might be. oh and as for how he baned wow from his pc. well u just delete user using administrator acount in windows xp. can we try and be nice 2 sunholm? --KarlaJoanne 14:57, 5 July 2006 (UTC)[reply]

Do you take us to be complete idiots! Ditch this sock, come back as your regular account and explain yourself properly. Using a sockpuppet account to back up protestations of innocence w.r.t. creating vandalising socks is just stupid. Theresa Knott | Taste the Korn 15:00, 5 July 2006 (UTC)[reply]
"KarlaJoanne" ain't going to do much more chatting here, I've blocked "her" indefinitely as a transparent sockpuppet. Just look at the history of contribs, including to Sunfazr's RFA. Sunfazr was the old account name of Sunholm, by the way. --Cyde↔Weys 15:37, 5 July 2006 (UTC)[reply]
I thnk we need to block all the other accounts associated with this user, including sunfazer, sunholm and two others i can't remember off the top of my head as being WoW socks. I'll do it in a little while unless anyone objects Theresa Knott | Taste the Korn 15:49, 5 July 2006 (UTC)[reply]
I'd agree. Morven has been involved in multiple blocks of IPs also used by Sunholm which are always coincidentally used by vandals also. There have also been numerous assurances made that the vandalism will stop. (e.g. User:82.42.237.114). It is also interesting to note that it was Sunholm who Cyde blocked as a bot when removing WoW from the list of permenantly banned users... --pgk(talk) 18:45, 5 July 2006 (UTC)[reply]

I've blocked them all Theresa Knott | Taste the Korn 20:47, 5 July 2006 (UTC)[reply]

Thanks guys, I apprecaite everyone keeping on top of this while I was asleep. (By the way, I answered Theresa's question on my talk page, if anyone was waiting for an answer to that.) There is an open checkuser request on WOW at RFCU that Mackensen has been dealing with; it just mentioned Blueyonder, the same ISP, so perhaps he may have useful information as well. Something tells me this isn't going to be the end of it. Essjay (TalkConnect) 08:14, 6 July 2006 (UTC)[reply]

 Clerk note: This is an edited version of a discussion that took place on the administrator's noticeboard regarding an IP used by a Willy on Wheels vandal.


WoW again[edit]

If you find IP's different from those listed on WP:WOW, could you please list them in the infobox where it says "Known IPs"? Thanks. This is the first time in a long while that I've seen real high-speed page-move vandalism (WoW usernames appear frequently, but actually moving pages in a widespread manner have been quite rare). -- King of 23:43, 27 June 2006 (UTC)[reply]

Note that Hive of scum and viliany! (talk · contribs · deleted contribs · nuke contribs · logs · filter log · block user · block log) appears to have been created in response to User:Mackensen's block of 195.188.152.16 (talk · contribs · deleted contribs · filter log · WHOIS · RDNS · RBLs · http · block user · block log) ([1]), an IP that has been used by an individual claiming to be Willy on Wheels. — Jun. 28, '06 [00:31] <freak|talk>

information Note: I've reblocked the responsible IP address. Mackensen (talk) 12:21, 2 July 2006 (UTC)[reply]

See talk please... -- King of 01:04, 5 July 2006 (UTC)[reply]


WoW or Marmot? Or someone else?[edit]

Seems like brions patch to cap the number of usernames that can be created from an IP payed off. However I expect range attacks as thats tipical. Are all fo them originating from the same IP? Is this a known dynamic IP range or is it an open proxy? --Cool CatTalk|@ 14:22, 13 January 2006 (UTC)[reply]

Looks like a compromised proxy. Blocked and marked as such. Kelly Martin (talk) 03:55, 17 January 2006 (UTC)[reply]
The above discussion is preserved as an archive of the Request for checkuser. Please do not modify it.
Subsequent requests related to this user should be made
above, in a new section.