Wikipedia:Sockpuppet investigations/UnderArmourKid/Archive/1

15 December 2015

 * Suspected sockpuppets


 * User compare report Auto-generated every hour.
 * Editor interaction utility

They all quack, but I'm missing the master and sleepers. Ks0stm (T•C•G•E) 23:48, 15 December 2015 (UTC)
 * Also, a check for a rangeblock would be helpful; that's a lot of accounts in a short time. Ks0stm  (T•C•G•E) 23:51, 15 December 2015 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Clerk, CheckUser, and/or patrolling admin comments

 * - Lot of accounts here. A sleepers check needed.  Vanjagenije  (talk)  00:09, 16 December 2015 (UTC)
 * Master is, otherwise ✅, . -- Amanda  (aka DQ) 09:52, 16 December 2015 (UTC)
 * Tagged all and closing.  Vanjagenije  (talk)  11:09, 16 December 2015 (UTC)

15 February 2016

 * Suspected sockpuppets


 * User compare report Auto-generated every hour.
 * Editor interaction utility

Making similar nonsense edits to cyclone articles as blocked puppeteer: RE, LC RolandR (talk) 01:40, 15 February 2016 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Clerk, CheckUser, and/or patrolling admin comments

 * Blocked. Closing.  Vanjagenije  (talk)  13:54, 15 February 2016 (UTC)

17 February 2016

 * Suspected sockpuppets


 * User compare report Auto-generated every hour.
 * Editor interaction utility

Many users vandalizing Cyclone Laurence and other pages. GZWDer (talk) 15:25, 17 February 2016 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''
 * Note: Libertadores = Rust EZE X950, Megachannel2 = WormHole25. This may need to be moved. GABHello! 01:59, 18 February 2016 (UTC)
 * Sorry, I was on my phone. By Libertadores, I was referring to the sock already listed, and by moved, I meant that this might have to be merged to another case if there's another master. Megachannel2 and WormHole25 are already on the list.GABHello! 13:37, 18 February 2016 (UTC)
 * We also have Sockpuppet investigations/Edison Lobos, which should also be merged.--GZWDer (talk) 15:45, 18 February 2016 (UTC)

Clerk, CheckUser, and/or patrolling admin comments

 * I've moved three of the four accounts mentioned by to the list. The fourth (Libertadores) doesn't exist. I also don't understand the "moved" comment. I'm checking the socks against each other. The master is .--Bbb23 (talk) 13:32, 18 February 2016 (UTC)
 * Confusing. See Sockpuppet investigations/Rust EZE X950, which will have to be merged into this one after I'm done (not right now, please).--Bbb23 (talk) 13:44, 18 February 2016 (UTC)
 * The following accounts are ✅ to each other:
 * I'll block the unblocked accounts without tags after I save this. There are two possibiilities as to what to do with this case in terms of the master. Either UnderArmourKid can remain the master based on behavioral evidence, or this case and the Rust EZE X950 case need to be folded into a new SPI with one of the above confirmed accounts as the master (there are older accounts than Rust EZE X950). I'll leave that decision to a clerk.--Bbb23 (talk) 14:48, 18 February 2016 (UTC)
 * Thanks for the link to the other SPI.--Bbb23 (talk) 16:31, 18 February 2016 (UTC)
 * I thing that UnderArmourKid should remain the master here, as there is interesting number of pages commonly vandalized. Other two SPIs will be merged into this one soon. Closing.  Vanjagenije  (talk)  23:59, 18 February 2016 (UTC)
 * I'll block the unblocked accounts without tags after I save this. There are two possibiilities as to what to do with this case in terms of the master. Either UnderArmourKid can remain the master based on behavioral evidence, or this case and the Rust EZE X950 case need to be folded into a new SPI with one of the above confirmed accounts as the master (there are older accounts than Rust EZE X950). I'll leave that decision to a clerk.--Bbb23 (talk) 14:48, 18 February 2016 (UTC)
 * Thanks for the link to the other SPI.--Bbb23 (talk) 16:31, 18 February 2016 (UTC)
 * I thing that UnderArmourKid should remain the master here, as there is interesting number of pages commonly vandalized. Other two SPIs will be merged into this one soon. Closing.  Vanjagenije  (talk)  23:59, 18 February 2016 (UTC)
 * I'll block the unblocked accounts without tags after I save this. There are two possibiilities as to what to do with this case in terms of the master. Either UnderArmourKid can remain the master based on behavioral evidence, or this case and the Rust EZE X950 case need to be folded into a new SPI with one of the above confirmed accounts as the master (there are older accounts than Rust EZE X950). I'll leave that decision to a clerk.--Bbb23 (talk) 14:48, 18 February 2016 (UTC)
 * Thanks for the link to the other SPI.--Bbb23 (talk) 16:31, 18 February 2016 (UTC)
 * I thing that UnderArmourKid should remain the master here, as there is interesting number of pages commonly vandalized. Other two SPIs will be merged into this one soon. Closing.  Vanjagenije  (talk)  23:59, 18 February 2016 (UTC)
 * I'll block the unblocked accounts without tags after I save this. There are two possibiilities as to what to do with this case in terms of the master. Either UnderArmourKid can remain the master based on behavioral evidence, or this case and the Rust EZE X950 case need to be folded into a new SPI with one of the above confirmed accounts as the master (there are older accounts than Rust EZE X950). I'll leave that decision to a clerk.--Bbb23 (talk) 14:48, 18 February 2016 (UTC)
 * Thanks for the link to the other SPI.--Bbb23 (talk) 16:31, 18 February 2016 (UTC)
 * I thing that UnderArmourKid should remain the master here, as there is interesting number of pages commonly vandalized. Other two SPIs will be merged into this one soon. Closing.  Vanjagenije  (talk)  23:59, 18 February 2016 (UTC)
 * I'll block the unblocked accounts without tags after I save this. There are two possibiilities as to what to do with this case in terms of the master. Either UnderArmourKid can remain the master based on behavioral evidence, or this case and the Rust EZE X950 case need to be folded into a new SPI with one of the above confirmed accounts as the master (there are older accounts than Rust EZE X950). I'll leave that decision to a clerk.--Bbb23 (talk) 14:48, 18 February 2016 (UTC)
 * Thanks for the link to the other SPI.--Bbb23 (talk) 16:31, 18 February 2016 (UTC)
 * I thing that UnderArmourKid should remain the master here, as there is interesting number of pages commonly vandalized. Other two SPIs will be merged into this one soon. Closing.  Vanjagenije  (talk)  23:59, 18 February 2016 (UTC)
 * I'll block the unblocked accounts without tags after I save this. There are two possibiilities as to what to do with this case in terms of the master. Either UnderArmourKid can remain the master based on behavioral evidence, or this case and the Rust EZE X950 case need to be folded into a new SPI with one of the above confirmed accounts as the master (there are older accounts than Rust EZE X950). I'll leave that decision to a clerk.--Bbb23 (talk) 14:48, 18 February 2016 (UTC)
 * Thanks for the link to the other SPI.--Bbb23 (talk) 16:31, 18 February 2016 (UTC)
 * I thing that UnderArmourKid should remain the master here, as there is interesting number of pages commonly vandalized. Other two SPIs will be merged into this one soon. Closing.  Vanjagenije  (talk)  23:59, 18 February 2016 (UTC)
 * I'll block the unblocked accounts without tags after I save this. There are two possibiilities as to what to do with this case in terms of the master. Either UnderArmourKid can remain the master based on behavioral evidence, or this case and the Rust EZE X950 case need to be folded into a new SPI with one of the above confirmed accounts as the master (there are older accounts than Rust EZE X950). I'll leave that decision to a clerk.--Bbb23 (talk) 14:48, 18 February 2016 (UTC)
 * Thanks for the link to the other SPI.--Bbb23 (talk) 16:31, 18 February 2016 (UTC)
 * I thing that UnderArmourKid should remain the master here, as there is interesting number of pages commonly vandalized. Other two SPIs will be merged into this one soon. Closing.  Vanjagenije  (talk)  23:59, 18 February 2016 (UTC)
 * I'll block the unblocked accounts without tags after I save this. There are two possibiilities as to what to do with this case in terms of the master. Either UnderArmourKid can remain the master based on behavioral evidence, or this case and the Rust EZE X950 case need to be folded into a new SPI with one of the above confirmed accounts as the master (there are older accounts than Rust EZE X950). I'll leave that decision to a clerk.--Bbb23 (talk) 14:48, 18 February 2016 (UTC)
 * Thanks for the link to the other SPI.--Bbb23 (talk) 16:31, 18 February 2016 (UTC)
 * I thing that UnderArmourKid should remain the master here, as there is interesting number of pages commonly vandalized. Other two SPIs will be merged into this one soon. Closing.  Vanjagenije  (talk)  23:59, 18 February 2016 (UTC)
 * I'll block the unblocked accounts without tags after I save this. There are two possibiilities as to what to do with this case in terms of the master. Either UnderArmourKid can remain the master based on behavioral evidence, or this case and the Rust EZE X950 case need to be folded into a new SPI with one of the above confirmed accounts as the master (there are older accounts than Rust EZE X950). I'll leave that decision to a clerk.--Bbb23 (talk) 14:48, 18 February 2016 (UTC)
 * Thanks for the link to the other SPI.--Bbb23 (talk) 16:31, 18 February 2016 (UTC)
 * I thing that UnderArmourKid should remain the master here, as there is interesting number of pages commonly vandalized. Other two SPIs will be merged into this one soon. Closing.  Vanjagenije  (talk)  23:59, 18 February 2016 (UTC)
 * I'll block the unblocked accounts without tags after I save this. There are two possibiilities as to what to do with this case in terms of the master. Either UnderArmourKid can remain the master based on behavioral evidence, or this case and the Rust EZE X950 case need to be folded into a new SPI with one of the above confirmed accounts as the master (there are older accounts than Rust EZE X950). I'll leave that decision to a clerk.--Bbb23 (talk) 14:48, 18 February 2016 (UTC)
 * Thanks for the link to the other SPI.--Bbb23 (talk) 16:31, 18 February 2016 (UTC)
 * I thing that UnderArmourKid should remain the master here, as there is interesting number of pages commonly vandalized. Other two SPIs will be merged into this one soon. Closing.  Vanjagenije  (talk)  23:59, 18 February 2016 (UTC)
 * Thanks for the link to the other SPI.--Bbb23 (talk) 16:31, 18 February 2016 (UTC)
 * I thing that UnderArmourKid should remain the master here, as there is interesting number of pages commonly vandalized. Other two SPIs will be merged into this one soon. Closing.  Vanjagenije  (talk)  23:59, 18 February 2016 (UTC)

18 February 2016

 * Suspected sockpuppets


 * User compare report Auto-generated every hour.
 * Editor interaction utility

Another possible sock who vandalize Cyclone Larry. GZWDer (talk) 15:42, 18 February 2016 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''
 * This is also probably related to these users (stale but IP may be useful).--GZWDer (talk) 15:49, 18 February 2016 (UTC)

Clerk, CheckUser, and/or patrolling admin comments

 * The following accounts are ✅:
 * I'll block the unblocked accounts without tags in a moment.--Bbb23 (talk) 16:59, 18 February 2016 (UTC)
 * Closing the case.  Vanjagenije  (talk)  00:17, 19 February 2016 (UTC)
 * I'll block the unblocked accounts without tags in a moment.--Bbb23 (talk) 16:59, 18 February 2016 (UTC)
 * Closing the case.  Vanjagenije  (talk)  00:17, 19 February 2016 (UTC)
 * I'll block the unblocked accounts without tags in a moment.--Bbb23 (talk) 16:59, 18 February 2016 (UTC)
 * Closing the case.  Vanjagenije  (talk)  00:17, 19 February 2016 (UTC)
 * I'll block the unblocked accounts without tags in a moment.--Bbb23 (talk) 16:59, 18 February 2016 (UTC)
 * Closing the case.  Vanjagenije  (talk)  00:17, 19 February 2016 (UTC)
 * I'll block the unblocked accounts without tags in a moment.--Bbb23 (talk) 16:59, 18 February 2016 (UTC)
 * Closing the case.  Vanjagenije  (talk)  00:17, 19 February 2016 (UTC)
 * I'll block the unblocked accounts without tags in a moment.--Bbb23 (talk) 16:59, 18 February 2016 (UTC)
 * Closing the case.  Vanjagenije  (talk)  00:17, 19 February 2016 (UTC)
 * I'll block the unblocked accounts without tags in a moment.--Bbb23 (talk) 16:59, 18 February 2016 (UTC)
 * Closing the case.  Vanjagenije  (talk)  00:17, 19 February 2016 (UTC)
 * I'll block the unblocked accounts without tags in a moment.--Bbb23 (talk) 16:59, 18 February 2016 (UTC)
 * Closing the case.  Vanjagenije  (talk)  00:17, 19 February 2016 (UTC)
 * I'll block the unblocked accounts without tags in a moment.--Bbb23 (talk) 16:59, 18 February 2016 (UTC)
 * Closing the case.  Vanjagenije  (talk)  00:17, 19 February 2016 (UTC)

18 February 2016

 * Suspected sockpuppets

And also: (low confidence)


 * User compare report Auto-generated every hour.
 * Editor interaction utility

Other possible socks. GZWDer (talk) 19:12, 18 February 2016 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Clerk, CheckUser, and/or patrolling admin comments

 * The following accounts are :
 * Create&DESTROY99
 * CODbacon2003
 * Group 1 – the following accounts are ✅ to the previous accounts:
 * Group 2 – the following accounts are ✅ to each other and ❌ to Group 1:
 * Group 3 – the following accounts are ✅ to each other and ❌ to Groups 1 and 2:
 * Group 4 – the following accounts are ❌ to each other and to Groups 1, 2 and 3:
 * Group 3 is school kid vandalism.
 * I will block any unblocked accounts in Groups 1, 2, and 3 shortly. No tags.--Bbb23 (talk) 23:11, 18 February 2016 (UTC)
 * Groups 2 and 3 are obvoius vandals, no need to tag them. I'm closing this.  Vanjagenije  (talk)  23:40, 20 February 2016 (UTC)
 * Group 3 – the following accounts are ✅ to each other and ❌ to Groups 1 and 2:
 * Group 4 – the following accounts are ❌ to each other and to Groups 1, 2 and 3:
 * Group 3 is school kid vandalism.
 * I will block any unblocked accounts in Groups 1, 2, and 3 shortly. No tags.--Bbb23 (talk) 23:11, 18 February 2016 (UTC)
 * Groups 2 and 3 are obvoius vandals, no need to tag them. I'm closing this.  Vanjagenije  (talk)  23:40, 20 February 2016 (UTC)
 * Group 4 – the following accounts are ❌ to each other and to Groups 1, 2 and 3:
 * Group 3 is school kid vandalism.
 * I will block any unblocked accounts in Groups 1, 2, and 3 shortly. No tags.--Bbb23 (talk) 23:11, 18 February 2016 (UTC)
 * Groups 2 and 3 are obvoius vandals, no need to tag them. I'm closing this.  Vanjagenije  (talk)  23:40, 20 February 2016 (UTC)
 * Group 4 – the following accounts are ❌ to each other and to Groups 1, 2 and 3:
 * Group 3 is school kid vandalism.
 * I will block any unblocked accounts in Groups 1, 2, and 3 shortly. No tags.--Bbb23 (talk) 23:11, 18 February 2016 (UTC)
 * Groups 2 and 3 are obvoius vandals, no need to tag them. I'm closing this.  Vanjagenije  (talk)  23:40, 20 February 2016 (UTC)
 * Group 4 – the following accounts are ❌ to each other and to Groups 1, 2 and 3:
 * Group 3 is school kid vandalism.
 * I will block any unblocked accounts in Groups 1, 2, and 3 shortly. No tags.--Bbb23 (talk) 23:11, 18 February 2016 (UTC)
 * Groups 2 and 3 are obvoius vandals, no need to tag them. I'm closing this.  Vanjagenije  (talk)  23:40, 20 February 2016 (UTC)
 * Group 3 is school kid vandalism.
 * I will block any unblocked accounts in Groups 1, 2, and 3 shortly. No tags.--Bbb23 (talk) 23:11, 18 February 2016 (UTC)
 * Groups 2 and 3 are obvoius vandals, no need to tag them. I'm closing this.  Vanjagenije  (talk)  23:40, 20 February 2016 (UTC)
 * Group 3 is school kid vandalism.
 * I will block any unblocked accounts in Groups 1, 2, and 3 shortly. No tags.--Bbb23 (talk) 23:11, 18 February 2016 (UTC)
 * Groups 2 and 3 are obvoius vandals, no need to tag them. I'm closing this.  Vanjagenije  (talk)  23:40, 20 February 2016 (UTC)
 * Groups 2 and 3 are obvoius vandals, no need to tag them. I'm closing this.  Vanjagenije  (talk)  23:40, 20 February 2016 (UTC)

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

Lately I've noticed a lot of vandalism only/throwaway accounts on Cyclone articles. I believe these users are all UnderArmourKid (example: confirmed sock to this user). The only unblocked account is Smoke1780, who I also believe to be connected (made this edit to Cyclone Larry and also there's this, which can be compared to this and this and this. However, here HeadrushGD claims to be a sockpuppet of a different master, iPhonehurricane95. Maybe UnderArmourKid is actually a iPhonehurricane95 sock? Sro23 (talk) 20:39, 19 July 2016 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Clerk, CheckUser, and/or patrolling admin comments

 * The accounts are ✅ to each other. The technical data of the past accounts is, so I can't make any connections. Mike V • Talk 17:34, 20 July 2016 (UTC)

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

~ Junior5a   (Talk)   Cont  00:58, 7 August 2016 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Clerk, CheckUser, and/or patrolling admin comments

 * Already blocked. CLosing.  Vanjagenije  (talk)  21:52, 7 August 2016 (UTC)

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

Probably WP:DUCK quacking. Already blocked, just want to list in here. NgYShung huh? 14:16, 6 September 2016 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

For the creation of the exact same page, Refutation of Apollo 11 on the basis of the fuel balance for the start and flight trajectory (see deleted contribs), as well as similar edits to other pages.  ~Oshwah~  (talk) (contribs)   13:35, 6 September 2016 (UTC)
 * I've added 5 additional usernames, evidence is a similarity of names and similarity of vandalism on, some of which use CU / SOCK templates (indicating someone who is quite familiar with this type of abuse).  Murph 9000  (talk) 14:14, 6 September 2016 (UTC)
 * Thank you, Murph9000! :-)  ~Oshwah~  (talk) (contribs)   14:15, 6 September 2016 (UTC)
 * No problem. :-) 190.47.181.41 added, due to same editing pattern.   Murph 9000  (talk) 14:34, 6 September 2016 (UTC)
 * 2 more names added. Connected through .  Already blocked, just adding for documentation and investigation purposes.   Murph 9000  (talk) 14:48, 6 September 2016 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Clerk, CheckUser, and/or patrolling admin comments
Everyone is blocked. Closing. Please see if this should be merged into Sockpuppet investigations/UnderArmourKid.--Bbb23 (talk) 15:20, 6 September 2016 (UTC)
 * ✅, merged.  Vanjagenije  (talk)  00:25, 8 September 2016 (UTC)

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

Murph 9000 (talk) 13:46, 9 September 2016 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Clerk, CheckUser, and/or patrolling admin comments

 * Accounts are already blocked. Case closed.  Vanjagenije  (talk)  14:49, 9 September 2016 (UTC)

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

First obvious sock, already blocked. Second undid revert of first's vandalism. Third created by second. Murph 9000 (talk) 13:29, 15 September 2016 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Clerk, CheckUser, and/or patrolling admin comments

 * Three ducks, all now blocked. Closing. BethNaught (talk) 17:45, 15 September 2016 (UTC)

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

Mostly likely "Armour" is matched. ~ Junior5a   (Talk)   Cont  22:15, 18 September 2016 (UTC)
 * for both.  Murph 9000  (talk) 22:39, 18 September 2016 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Clerk, CheckUser, and/or patrolling admin comments

 * Everyone is blocked. Closing. Bbb23 (talk) 22:54, 18 September 2016 (UTC)

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

Murph 9000 (talk) 21:43, 21 September 2016 (UTC)
 * All blocked now, leaving report for the record and any analysis you may want to do.  Murph 9000  (talk) 21:53, 21 September 2016 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Clerk, CheckUser, and/or patrolling admin comments

 * All blocked. Closing. Favonian (talk) 17:44, 22 September 2016 (UTC)

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

Murph 9000 (talk) 13:24, 4 October 2016 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Clerk, CheckUser, and/or patrolling admin comments

 * IP blocked by ; named account by myself. Closing. Favonian (talk) 13:32, 4 October 2016 (UTC)

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

N-C16 (talk) 23:01, 4 October 2016 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''


 * Blocked the IP, but it would be nice to get a CU to look at this (combined with past accounts in the archive) to see if a rangeblock is feasable. Ks0stm  (T•C•G•E) 23:16, 4 October 2016 (UTC)

Clerk, CheckUser, and/or patrolling admin comments

 * Also requesting CU to check for a range block. Ks0stm  (T•C•G•E) 23:14, 4 October 2016 (UTC)
 * - A rangeblock would be nice. GABgab 21:32, 6 October 2016 (UTC)
 * . A block has been applied. Mike V • Talk 17:52, 8 October 2016 (UTC)
 * . A block has been applied. Mike V • Talk 17:52, 8 October 2016 (UTC)
 * . A block has been applied. Mike V • Talk 17:52, 8 October 2016 (UTC)
 * . A block has been applied. <b style="color:#151B54">Mike V</b> • <b style="color:#C16C16">Talk</b> 17:52, 8 October 2016 (UTC)
 * . A block has been applied. <b style="color:#151B54">Mike V</b> • <b style="color:#C16C16">Talk</b> 17:52, 8 October 2016 (UTC)

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

Quack. They've been known to have sleepers, so sleeper check? Ks0stm (T•C•G•E) 05:02, 19 November 2016 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Clerk, CheckUser, and/or patrolling admin comments

 * Found --  Amanda  (aka DQ) 05:23, 19 November 2016 (UTC)

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

Seems pretty quacky. Vandalizing tropical cyclone articles like past socks. Ks0stm (T•C•G•E) 22:39, 21 November 2016 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Clerk, CheckUser, and/or patrolling admin comments

 * - Katietalk 22:40, 21 November 2016 (UTC)
 * ✅ – I don't see any active sleepers. Blocked without tags per DENY, closing. Katietalk 22:48, 21 November 2016 (UTC)

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

Self-admitted. Let's do the usual check for sleepers, please. Ks0stm (T•C•G•E) 20:15, 23 November 2016 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Clerk, CheckUser, and/or patrolling admin comments

 * No sleepers. -- Amanda  (aka DQ) 20:37, 23 November 2016 (UTC)

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

. Just reporting for the record. Ks0stm (T•C•G•E) 23:50, 24 November 2016 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Clerk, CheckUser, and/or patrolling admin comments

 * Blocked, closing. GABgab 00:25, 25 November 2016 (UTC)

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

A clear self identified sock as can be seen in this edit on Cyclone Nargis and also the same edit was done by User:BlassCFB  due to which they have already been blocked. Hence, requesting checkuser for any other possible sleeper accounts. TheGeneralUser (talk) 17:47, 27 December 2016 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Clerk, CheckUser, and/or patrolling admin comments

 * Account blocked. No reason to do a CU. Closing. Bbb23 (talk) 01:14, 28 December 2016 (UTC)

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

same types of edits, abusing page about sockpuppets of UnderArmourKid -glove-(alt, public) (talk) (main account's talk) 19:43, 12 January 2017 (UTC)

same types of vandalism, editing page about their sockpuppets -glove-(alt, public) (talk) (main account's talk) 19:45, 12 January 2017 (UTC)

same types of edits, editing sockpuppet category page for puppeteer -glove-(alt, public) (talk) (main account's talk) 19:46, 12 January 2017 (UTC)

similar editing patterns and articles to other socks WNYY98 (talk) 22:25, 12 January 2017 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''
 * Seeing also, , and a few more in the histories of Jimmie Johnson, Kevin Harvick, and Bass Pro Shops. All are blocked. -- ferret (talk) 22:30, 12 January 2017 (UTC)
 * OceanicFish!! talk page abuse in progress WNYY98 (talk) 22:53, 12 January 2017 (UTC)
 * ✅ (verify: ) by --JustBerry (talk) 23:03, 12 January 2017 (UTC)

Clerk, CheckUser, and/or patrolling admin comments

 * Only ones unlisted, but already blocked:
 * -- Amanda  (aka DQ) 15:33, 13 January 2017 (UTC)
 * -- Amanda  (aka DQ) 15:33, 13 January 2017 (UTC)
 * -- Amanda  (aka DQ) 15:33, 13 January 2017 (UTC)
 * -- Amanda  (aka DQ) 15:33, 13 January 2017 (UTC)


 * No tags, closing. GABgab 16:14, 13 January 2017 (UTC)

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

As per this edit, where they admit to being a sock:

https://en.wikipedia.org/w/index.php?title=Danica_Patrick&diff=prev&oldid=760275490

Also editing the same kind of articles, ie ones that have had some form of aviation involvement:

https://en.wikipedia.org/w/index.php?title=United_Airlines_Flight_175&diff=prev&oldid=615404989

https://en.wikipedia.org/w/index.php?title=World_Trade_Center_(1973%E2%80%932001)&diff=prev&oldid=760275387

Requesting CheckUser to see if there are any others and also because of this threat to create another sock unless unblocked:

https://en.wikipedia.org/w/index.php?title=User_talk:GameCube_Racing&diff=prev&oldid=760275835 5 albert square (talk) 00:46, 16 January 2017 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Clerk, CheckUser, and/or patrolling admin comments
✅ + the following accounts:
 * Blocked the two unblocked accounts without tags per WP:DENY. Closing.--Bbb23 (talk) 13:14, 18 January 2017 (UTC)
 * Blocked the two unblocked accounts without tags per WP:DENY. Closing.--Bbb23 (talk) 13:14, 18 January 2017 (UTC)
 * Blocked the two unblocked accounts without tags per WP:DENY. Closing.--Bbb23 (talk) 13:14, 18 January 2017 (UTC)

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

New accounts vandalizing the same pages sometimes within minutes of each other. I think these are the only unblocked socks? Sro23 (talk) 19:37, 29 January 2017 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Clerk, CheckUser, and/or patrolling admin comments

 * I'm familiar with this sock so I'll check the edits 5 albert square (talk) 19:46, 29 January 2017 (UTC)


 * so I've blocked and I've protected the Aflac page as that one was vandalised by all socks. I've not tagged as I noticed a previous comment from Bbb23 regarding WP:DENY.    or any other passing CheckUser is it worthwhile running CU to see if there are any others? 5 albert square (talk) 20:01, 29 January 2017 (UTC)
 * I'll pass on the CU this time. Closing.--Bbb23 (talk) 20:42, 29 January 2017 (UTC)

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

Fairly obvious duck. Chrissymad ❯❯❯  ¯\_(ツ)_/¯  22:00, 30 January 2017 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Clerk, CheckUser, and/or patrolling admin comments

 * Puff! Closing. Favonian (talk) 22:02, 30 January 2017 (UTC)

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

Quack quack. (See edit to Home Depot, a UAK favorite and the self-proclamation of being UAK...) Chrissymad  ❯❯❯  ¯\_(ツ)_/¯  17:32, 6 February 2017 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Clerk, CheckUser, and/or patrolling admin comments

 * I'm familiar so I'll take a look 5 albert square (talk) 17:45, 6 February 2017 (UTC)
 * In fact already blocked by . I'm not going to tag as per WP:DENY.  No CheckUser requested so going to close now.--5 albert square (talk) 17:52, 6 February 2017 (UTC)

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

Fairly obvious Duck. Chrissymad ❯❯❯  ¯\_(ツ)_/¯  20:44, 6 February 2017 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Clerk, CheckUser, and/or patrolling admin comments

 * Obvious duck. Rangeblock does not look possible here, unfortunately. Ks0stm  (T•C•G•E) 21:22, 6 February 2017 (UTC)

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

Pretty obvious WP:DUCK from edits and username. Have CheckUsers looked into any possible rangeblocks? Jasper Deng (talk) 02:21, 7 February 2017 (UTC)
 * Update: just saw the previous case. Looks like I may want to look into constructing an abuse filter instead.--Jasper Deng (talk) 02:22, 7 February 2017 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Clerk, CheckUser, and/or patrolling admin comments

 * All blocked. The CU request is ; I wavered, but it looks like Ks0stm's already checked recently. Nothing left to do here, closing. Kevin ( aka L235 ·&#32; t ·&#32; c) 14:24, 8 February 2017 (UTC)

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

Obvious duck of UAK. Chrissymad ❯❯❯  ¯\_(ツ)_/¯  18:34, 7 February 2017 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Clerk, CheckUser, and/or patrolling admin comments

 * Already blocked by . Going to close now as no SPI requested for this one. 5 albert square (talk) 20:55, 7 February 2017 (UTC)

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

I mistakenly added this to the wrong SPI. Obvious UAK duck. Chrissymad ❯❯❯  ¯\_(ツ)_/¯  13:58, 8 February 2017 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

User:UnderArmourMan is likely a sockpuppet of UnderArmourKid. --B1 l T l C (C)2016 Brynda1231 Do Not Steal. 14:12, 8 February 2017 (UTC)

Clerk, CheckUser, and/or patrolling admin comments

 * All blocked. Closing. Favonian (talk) 14:14, 8 February 2017 (UTC)

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

Quack quack. Chrissymad ❯❯❯  ¯\_(ツ)_/¯  23:29, 10 February 2017 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Clerk, CheckUser, and/or patrolling admin comments

 * Blocked, closing. GABgab 23:44, 10 February 2017 (UTC)

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

See diff provided; explicitly claims to be UnderArmourKid in vandalistic edit. YITYNR My work • What's wrong? 21:45, 16 March 2017 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Clerk, CheckUser, and/or patrolling admin comments

 * Blocked; closing. Favonian (talk) 21:51, 16 March 2017 (UTC)
 * - I'm actually going to do a sleeper/rangeblock check right quick. Ks0stm  (T•C•G•E) 03:46, 17 March 2017 (UTC)
 * Anyway, now that I'm done being rudely interrupted by a different LTA, I blocked two sleepers and a range, but the primary range was too busy to block. In the future, however, a checkuser of their most recent socks at the time every few weeks wouldn't go amiss just in case they get back on blockable ranges or leave sleepers behind.  Ks0stm  (T•C•G•E) 04:17, 17 March 2017 (UTC)
 * Closing. GABgab 13:58, 17 March 2017 (UTC)

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

See his contributions. RitoWiki likes editing on pages that past socks of UnderArmorKid have been known to vandalize (e.g. Aflac). Editing pattern appears quite similar, particularly these, some sort of nonsense vandalism seen from this sockmaster in the past; also, the "GD" in the vandal edits are very likely a reference to his other socks with the "GD" name (e.g. User:211 GD, User:GironDavidGD). The user also continued to vandalize after their first block expired. Requesting a sleeper check in any case (it never hurts), and if the account is confirmed, requesting block on the IPs used there. LightandDark2000 (talk) 09:44, 18 April 2017 (UTC)
 * By the way, this edit here seems to reference the account's link to UnderArmourKid, which would make it a possible quack. It's very similar to other vandal edits by different UnderArmourKid socks as well, see, . LightandDark2000 (talk) 05:04, 19 April 2017 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Clerk, CheckUser, and/or patrolling admin comments

 * Good eye, ✅ and blocked. Courcelles (talk) 19:12, 21 April 2017 (UTC)

Suspected sockpuppets
*


 * User compare report Auto-generated every hour.
 * Editor interaction utility

Quack, quack, quack. . See the contributions of the vandalism-only accounts listed above (the first 2 have already been confirmed as socks of UnderArmourKid and are blocked; they are included for referencing purposes). These accounts all appear to be unblocked sleeper accounts of UnderArmourKid. They all edit in identical manners, and they vandalize the same articles consistently. All of their editing patterns/behavior is pretty consistent with the kind of vandalism seem from other UnderArmourKid socks in previous cases. Also, most of the accounts were created in quick succession of each other. In addition, all of those accounts edited in a rather short period of time within each other's activity, or within a short amount of time after the blocking of a confirmed UnderArmourKid sock. The names of some of these accounts are also very similar to other blocked sockpuppets of UnderArmourKid; for example, User:Smoke2014 is extremely similar to User:Smoke1780. Requesting that all of the accounts above be blocked indefinitely, as well as a sleeper check on the underlying IP range. I would hate to see any more of these socks remaining unblocked. Even if a Checkuser can't be done on these accounts, I would still request an indef block on all those accounts due to the behavioral evidence. LightandDark2000 (talk) 21:32, 23 April 2017 (UTC)
 * Since there are so many accounts listed, I will only provide a few examples of the vandal edits to tie the accounts together to UnderArmourKid. They have all vandalized tropical cyclone articles and articles pertaining to brands (something that UnderArmourKid is notorious for). A number of the unblocked accounts above made the following edits:, , , , (sock account plunks in "yes," a known vandal edit performed by past UnderArmourKid socks), . Now, compare them with these vandal edits by known (blocked) UnderArmourKid socks: , , , , , , ,  (a "yes" edit), ...
 * Sorry, I accidentally included Salamon650 above. He probably not a sock account. (It's also taking some time for me to gather up some editorial evidence). LightandDark2000 (talk) 22:06, 23 April 2017 (UTC)
 * What about a sleeper check on the underlying IP range? I'm concerned that we may still be missing a couple of undetected sock accounts that may reemerge to wreck havoc in the near future. LightandDark2000 (talk) 22:19, 23 April 2017 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Clerk, CheckUser, and/or patrolling admin comments

 * - The only account here that has edited in the last two years is . Please, provide some evidence regarding this account (see Template:diffsneeded for explanation). You can disregard other stale accounts.  Vanjagenije   (talk)  22:04, 23 April 2017 (UTC)
 * There's no need to block years old throw-away accounts. Case closed.  Vanjagenije  (talk)  22:09, 23 April 2017 (UTC)

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

WP:DUCK. Nearly every account named has vandalized User talk:UA rocks!. In the case of NetherGD and Skrillex Party, identical edits. In the case of ExtremeArmourKid, UnderArmourKid666, By Zobros and UA rocks!, they make pleas/threats to unblock. In the case of the others, similar one-two word gibberish at top of page.

Other than piling on the same talkpage, some have explicitly or implicitly declared themselves to be UnderArmourKid

In addition, several accounts with similar name conventions have vandalized Bass Pro: OceanicFish!! , Robot and Nascar!! , UA Kid!! and ExtremeArmourKid as well.

Many users use a template-style blob in their vandalism, incorporating 9-11 imagery. Examples: from the IP,  from OceanicFish!! and from the most recently active sock are identical.

Many if not nearly all socks have vandalized Jimmie Johnson, including Sonic Wave and BlueArmour

I realize these aren't all current but this needs to be filed for the record. Bri (talk) 02:09, 28 May 2017 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Clerk, CheckUser, and/or patrolling admin comments

 * Will check this sometime later if no other CU gets to it first. With this many accounts there may be sleepers and a rangeblock may be useful. Ks0stm  (T•C•G•E) 02:47, 28 May 2017 (UTC)
 * Specifically to check and  from the archive against the non-stale .  Ks0stm  (T•C•G•E) 02:51, 28 May 2017 (UTC)
 * ✅ via RitoWiki andBausha Vortex:
 * With nearly all of the accounts above being stale, there isn't much to work with, and I only checked the ranges and addresses known to be used this year, so I may have missed some. ​—DoRD (talk)​ 12:07, 28 May 2017 (UTC)
 * All blocked. Case closed.  Vanjagenije  (talk)  13:09, 28 May 2017 (UTC)
 * With nearly all of the accounts above being stale, there isn't much to work with, and I only checked the ranges and addresses known to be used this year, so I may have missed some. ​—DoRD (talk)​ 12:07, 28 May 2017 (UTC)
 * All blocked. Case closed.  Vanjagenije  (talk)  13:09, 28 May 2017 (UTC)
 * With nearly all of the accounts above being stale, there isn't much to work with, and I only checked the ranges and addresses known to be used this year, so I may have missed some. ​—DoRD (talk)​ 12:07, 28 May 2017 (UTC)
 * All blocked. Case closed.  Vanjagenije  (talk)  13:09, 28 May 2017 (UTC)
 * With nearly all of the accounts above being stale, there isn't much to work with, and I only checked the ranges and addresses known to be used this year, so I may have missed some. ​—DoRD (talk)​ 12:07, 28 May 2017 (UTC)
 * All blocked. Case closed.  Vanjagenije  (talk)  13:09, 28 May 2017 (UTC)

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

Quack, quack. Obvious socks. The editing behavior pretty much gives it away; vandalism is nearly identical and there is a direct overlap at Aflac, which UnderArmourKid has been known to vandalize recently. Since the sockmaster has been generating new socks as recently as a week ago, and since the IP Range he's on right now is still unblocked, I strongly recommend a sleeper check on all of his IP ranges, and Rangeblocked wherever possible. A sockmaster of his type isn't just going to quit, and we're going to have to implement stronger measures against him. At this point, I would also recommend filing a WP:LTA report, due to his persistence and the severity of his vandalism. LightandDark2000 (talk) 22:43, 7 June 2017 (UTC)
 * The named accounts are currently blocked; however, I listed them for reference and because their recent activity deems a sleeper check on their underlying IPs, as well as the underlying IP ranges of all known UnderArmourKid socks. LightandDark2000 (talk) 22:43, 7 June 2017 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Clerk, CheckUser, and/or patrolling admin comments

 * Accounts are already blocked, and there's nothing left to do here. Please refrain from reverting CheckUsers or SPI clerks. ​—DoRD (talk)​ 11:49, 8 June 2017 (UTC)

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

Consistent with WP:Long-term abuse/UnderArmourKid, specifically, cyclones and 9/11 imagery. Note that the first diff also introduced text "underarmourkid". ☆ Bri (talk) 00:18, 21 September 2017 (UTC)

StarLightZone1 listed for coherency, may have already been CU blocked. ☆ Bri (talk) 03:30, 21 September 2017 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Clerk, CheckUser, and/or patrolling admin comments
Everyone is already blocked. NinjaRobotPirate (talk) 02:59, 24 September 2017 (UTC)

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

This seems like a very obvious one; see the username itself and the two edits thus far (also VOA). 65 HC  A7  12:45, 24 September 2017 (UTC)

Edit to add another obvious one from recently. 65 HC  A7  12:50, 24 September 2017 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''
 * Also added . –72 (talk) 18:45, 24 September 2017 (UTC)
 * My God, can someone please rangeblock this guy for 6 months to 1 year? I know that a Checkuser or two implemented about 3 separate 3-month rangeblocks for this guy back in March 2017 (see SPI archives); they must have expired by now. He's been mass socking for over 2 weeks now, and without any kind of larger-scale blocking at the IP level, I doubt that we will see any of this socking stop. Even 5-10 small rangeblocks would be better than letting this guy go unchecked with his IP switching. LightandDark2000 (talk) 06:58, 25 September 2017 (UTC)
 * Added the remaining recent socks that I could find. Requesting a sleeper check on the underlying IP ranges, just to make sure we didn't miss anything (especially since the sockmaster appears to be active very recently, and could be making new socks). LightandDark2000 (talk) 07:14, 25 September 2017 (UTC)


 * Also added –72 (talk) 22:34, 25 September 2017 (UTC)

Please help. This is really getting out of control. Worse, this guy is also vandalizing a number of high-viewership articles (e.g. Hurricane Irma, Hurricane Maria, etc.). LightandDark2000 (talk) 22:25, 26 September 2017 (UTC)
 * Note to Checkusers, when considering rangeblocking this sockmaster, it would also be helpful to see the other sock IPs indicated in the SPI archive, and to consult with other CUs who have rangeblocked this guy in the past (such as the admin I've pinged above). LightandDark2000 (talk) 22:33, 26 September 2017 (UTC)
 * This IP (157.157.58.170) has also been used repeatedly during this year.

LightandDark2000 (talk) 22:37, 26 September 2017 (UTC)
 * I would also like to see a sleeper check on all known IP ranges of this sockmaster as well (regardless of whether or not they've been used in the last 2 months), because you never know what might be lurking out there. He also appears to be creating new socks, based on recent activity. LightandDark2000 (talk) 22:44, 26 September 2017 (UTC)
 * As I thought, he's still at it. It also wouldn't hurt for admins to sift through the User Account Creation Logs for fishy accounts, until rangeblocks can be implemented. LightandDark2000 (talk) 03:43, 27 September 2017 (UTC)
 * Yup, this is a bloody mess. I suspect the he is in the process (or soon will be) of creating new sockpuppets. And the accounts/IPs listed above are just for the past 2 months alone, so plenty of other socks (all blocked) from earlier this year are not included. LightandDark2000 (talk) 03:58, 27 September 2017 (UTC)

Thanks for the blocks. By the way, this is probably long overdue, but looking at this guy's behavior, it appears that this sockmaster is an indirect meatpuppet of User:IPhonehurricane95, due to their editing similarities (in 2014 and 2016) and overlapping interests. It seems that whoever is operating the UnderArmourKid sockfarm has taken a liking to IPhonehurricane95's former (hopefully) vandalism, and has based his sockfarm on the old IPh95 account, UnderArmourKid. I'm just stating this for the record, so that any future admins and involved users will know what they are dealing with. While the UnderArmourKid sockmaster appears to operate independently of IPhonehurricane95 (especially given recent evidence that IPh95 has been inactive for 9 months now), UAK's admiration of IPh95 and emulation of the latter's vandalism means that this sockmaster may be just as persistent and disruptive as the older sockmaster, meaning that actions taken against IPhonehurricane95 in the past may also have to be taken for this user as well (such as Global Account locking). Users can reference IPhonehurricane95's SPIs to analyze behavioral similarities between the two sockmasters, and see just how UAK has taken on the mantle of vandalism that IPh95 seems to have abandoned. LightandDark2000 (talk) 20:18, 28 September 2017 (UTC)
 * As of today, the rangeblocks appear to be effective, and there are no new sock accounts that I'm aware of. However, I advise users to be vigilant and continue to check up on the articles most frequently vandalized by this sockmaster, as you never know whether or not he will find some way to circumvent his blocks. That's another reason why I believe that a sleeper check needs to be performed on his IP ranges. LightandDark2000 (talk) 21:16, 29 September 2017 (UTC)
 * Note the use of usernames consistent with WP:Long-term abuse/UnderArmourKid. Email me if you need more specifics. ☆ Bri (talk) 20:19, 30 September 2017 (UTC)
 * I think they're busy right now. Hopefully they will be able to run some checks and finish up this case soon. LightandDark2000 (talk) 22:29, 30 September 2017 (UTC)

Clerk, CheckUser, and/or patrolling admin comments
— Berean Hunter   (talk)  18:44, 25 September 2017 (UTC)
 * to find other accounts and apply appropriate rangeblocks where possible.
 * Yikes. I'll take a look at this tomorrow. Ks0stm  (T•C•G•E) 03:47, 27 September 2017 (UTC)
 * Also, rangeblocks applied. You'd have to be a dullard not to see they're quacking. Ks0stm  (T•C•G•E) 03:59, 27 September 2017 (UTC)

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

Self proclaimed duck  Velella  Velella Talk 19:34, 10 October 2017 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Clerk, CheckUser, and/or patrolling admin comments

 * . Favonian (talk) 19:42, 10 October 2017 (UTC)

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

Ducks. The first one is a dead giveaway, but the second account needs to be CU checked, because someone commented that it might be an User:Incorrigible Troll sock. Requesting a CheckUser to run a sleeper check and block the underlying IP ranges of these accounts, as this guy is still evading his block.  Light and Dark2000  (talk) 05:29, 11 October 2017 (UTC)
 * , please help. This guy has evaded his rangeblocks. And the second account is another potential block evasion, either by UAK or by Incorrigible Troll.  Light and Dark2000  (talk) 05:29, 11 October 2017 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Just noticed these things about UAK and Troll. 1) both habitually drawn to hurricane articles 2) Troll's editing fills in a gap in UAK's timeline 3) both have socks containing "David". ☆ Bri (talk) 05:54, 11 October 2017 (UTC)
 * I personally believe that those are coincidental. Both sockmasters geolocate to completely different locations (Incorrigible Troll appears to be stationed in the eastern US, but UAK is in Chile). It could be an obsession with similar stuff, or possibly with each other. The recent UAK did Hurricane Irma account is a bit interesting, given that its editing patterns didn't conform to most of what we've seen from UAK socks recently. I find what you've noted about both sockmasters very intriguing, nonetheless, if they are the same person, that would be very bad. We need a CU to run checks on all those accounts, especially the ones listed above.  Light and Dark2000  (talk) 06:32, 11 October 2017 (UTC)
 * As far as I know, Incorrigible Troll didn't start vandalizing hurricane articles until last month (with the creation of Category5AtlanticHurricaneBoy101). I could be wrong, but his recent targeting of hurricane articles appears to have started less than a month ago.  Light and Dark2000  (talk) 06:33, 11 October 2017 (UTC)

Clerk, CheckUser, and/or patrolling admin comments

 * Both accounts ✅ as the user known as Incorrigible Troll. Also blocked as the same. Range(s) not blocked at this time, but don't hesitate to pursue range blocks in the future. I'll leave it to the clerks where to place this report. -- zzuuzz (talk) 19:24, 11 October 2017 (UTC)

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

Obvious ducks. Requesting a Sleeper Check and a re-blocking of all IP Ranges involved, given the persistence and severity of this vandal's disruption.
 * Can you please re-block the IP Ranges that UAK used within the last 6 months? He returned to vandalize almost immediately after his last 2 rangeblocks expired, and it's clear that he isn't just going to stop. The ranges 191.119.0.0/16, 191.116.0.0/16 should probably be re-blocked as well.  Light and Dark2000  (talk) 03:20, 8 December 2017 (UTC)
 * I also found an obvious sock account that he used to evade his rangeblocks a couple of weeks ago. The IP range for that account (now listed) needs to be blocked as well.  Light and Dark2000  (talk) 03:25, 8 December 2017 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Clerk, CheckUser, and/or patrolling admin comments

 * The named account was blocked weeks ago. I see no basis for a sleeper check. Closing. Bbb23 (talk) 15:56, 8 December 2017 (UTC)
 * The named account was blocked weeks ago. I see no basis for a sleeper check. Closing. Bbb23 (talk) 15:56, 8 December 2017 (UTC)

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

Obvious ducks. The articles targeted and the behavior is pretty much identical. Requesting a Sleeper Check and a re-blocking of all IP Ranges involved, given the persistence and severity of this vandal's disruption. Given his pattern of mass sock creation, it's possible that there are still some sleeper accounts lying around.  Light and Dark2000  (talk) 09:37, 11 December 2017 (UTC)
 * Can you please re-block the IP Ranges that UAK used within the last 6 months? 191.119.0.0/16, 191.116.0.0/16 are some of his most recent ranges, and the recent SPI cases in the archives should help as well. This vandal has been vandalizing ever since his rangeblocks wore off, and continued to sock recently almost immediately after his most recent IP block wore off. His persistent mass socking/vandalism spree is especially problematic, given his use of 9/11 imagery and targeting of high-viewership articles (e.g. Hurricane Harvey).  Light and Dark2000  (talk) 09:42, 11 December 2017 (UTC)
 * By the way, it would be very useful to create an edit/account creation filter to help nab new sock accounts before they can do any damage. An edit filter for the usernames related to "UnderArmour" or "ArmourKid" (or other common naming patterns used by this sockmaster) would prove quite useful.  Light and Dark2000  (talk) 09:44, 11 December 2017 (UTC)
 * Can someone seriously please reblock his IP Ranges, and run some Sleeper Checks??  Light and Dark2000  (talk) 13:07, 14 December 2017 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Clerk, CheckUser, and/or patrolling admin comments

 * I've made a separate block and run sleeper checks. The disruption from these ranges is not currently at a level which warrants range blocks. However feel free to update with any further vandalsockery. -- zzuuzz (talk) 15:08, 14 December 2017 (UTC)

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

Obvious ducks. The editing behavior and types of articles vandalizes matches the known pattern of this sockmaster. Requesting another Sleeper Check, given this vandal's penchant for serial socking. (The most recent range appears to be 201.219.236.0/22.) Can we please get rangeblocks on this guy? Given his past and recent behavior, he's only going to continue serial socking and vandalizing across multiple articles unless his ability to create more accounts and IP sock are cut off.  Light and Dark2000  (talk) 20:07, 28 December 2017 (UTC)
 * BTW, it seems that UAK is currently socking from his smartphone, so a rangeblock should probably be implemented here.  Light and Dark2000  (talk) 20:28, 28 December 2017 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Clerk, CheckUser, and/or patrolling admin comments

 * ✅ accounts + . to the archive (but behavior overrides that obviously). Rangeblock not possible right now. The current range being used only has these three accounts on it, and I can't justify blocking the range at this time until there is more activity. --  Amanda  (aka DQ) 00:48, 29 December 2017 (UTC)
 * Closing. Sro23 (talk) 00:58, 29 December 2017 (UTC)
 * Global locks requested. --<span style="font-family:'Trebuchet MS',Geneva,sans-serif"> QEDK ( 桜  ❄  伴 ) 19:53, 1 January 2018 (UTC)

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

Obvious ducks. The vandalism and the articles targeted by the sock is consistent with the pattern of this sockmaster. Requesting a Sleeper Check to be run, given this vandal's penchant for mass-socking, and also requesing IP blocks, if possible.  Light and Dark2000  (talk) 11:30, 24 January 2018 (UTC)
 * By the way, after viewing this sock's latest vandalism attacks, I believe that there should be an edit filter created for the addition of graphic 9/11 images in articles of topics unrelated to the event.  Light and Dark2000  (talk) 11:33, 24 January 2018 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

There's also another likely sock I've found: Rematch GD. He's just vandalized this very page and has put "underarmourkid" on one page. Person who formerly started with &#34;216&#34; (talk) 13:19, 24 January 2018 (UTC)


 * I've put in a request at MediaWiki talk:Bad image list for the series of images shown here (two of these were used above) to be blacklisted. Home Lander (talk) 16:38, 25 January 2018 (UTC)


 * I had request an global lock at SRG, stewards also can run a sleeper check as well. <b style="color:red">S</b><b style="color:orange">A</b><b style="color:gold"> 1</b><b style="color:green">3</b><b style="color:blue"> B</b><b style="color:indigo">r</b><b style="color:violet">o</b> (talk) 19:20, 25 January 2018 (UTC)
 * Yes, that account's definitely him. The username ("GD") is a direct giveaway. By the way, a rangeblock would really help here, given the serial socking exposed.  Light and Dark2000  (talk) 22:39, 25 January 2018 (UTC)
 * I found another sock, UA Rocks 2.0!.  Light and Dark2000  (talk) 22:41, 25 January 2018 (UTC)

Clerk, CheckUser, and/or patrolling admin comments
-- zzuuzz (talk) 19:29, 25 January 2018 (UTC)
 * Confirmed, no current sleepers, recent unlocked accounts are:
 * Tagging and closing. Sir Sputnik (talk) 20:20, 25 January 2018 (UTC)

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

see WP:Long-term abuse/UnderArmourKid - username and behavior match. also self-identified ☆ Bri (talk) 03:34, 16 February 2018 (UTC)
 * I agree, obvious ducks. The IPv6 IP sock could possibly be an IPhonehurricane95 sock (given the IP's geolocation and the service provider). However, given the fact that IPhonehurricane95 hasn't vandalized for 1 or 2 years, it could be UAK, using a proxy.  Light and Dark2000  (talk) 10:32, 16 February 2018 (UTC)
 * Can CUs please run Sleeper Checks on the IPs and the named account? And please rangeblock the IP ranges, the vandal has already demonstrated that he will stop at nothing to vandalize Wikipedia. He returned to vandalize the day after his recent rangeblock expired.  Light and Dark2000  (talk) 10:32, 16 February 2018 (UTC)
 * FYI, for any Checkusers reading this: if the named account was created by an IP based in the US, it's probably IPhonehurricane95. Their vandalism is similar enough that only their geolocations (IPhonehurricane95 operates from the US and China, on occassions) would give them away. If the named account is linked to Chile, or has no relation to the IPv6 address, then the IPv6 sock is most likely IPhonehurricane95, which would be very problematic (long story short, his vandalism's much worse than anything UAK is capable of). Does UAK even have IPs to use in the US?  Light and Dark2000  (talk) 10:38, 16 February 2018 (UTC)
 * By the way, this is the IP Range: 2600:1:f440::/44. In addition, the rangeblock for 201.219.232.0/21 should probably be reset and extended to 6 months, due to UAK's persistent vandalism. The IPv4 range was UAK's most recent IP Range used, and it should be reblocked, given his statement here.  Light and Dark2000  (talk) 10:45, 16 February 2018 (UTC)

He's still socking. Can someone please block/re-block his IP Ranges for at least a few months?  Light and Dark2000  (talk) 13:13, 16 February 2018 (UTC)
 * Okay, the ranges have been blocked, but we still need a Sleeper Check, since UAK was busy IP hopping and creating new socks just an hour ago.  Light and Dark2000  (talk) 13:55, 16 February 2018 (UTC)

By the way, is the IP sock 2600:1:F447:D811:60D5:F1E4:6A84:F3E3 related to any of the accounts? If not, it looks like User:IPhonehurricane95 returned, and it this would require a new SPI page to be opened under his casepage. The IP's geolocation is in the United States, and the network provider is Sprint PCS (the same network provider as that of IPhonehurricane95's main IP Range), and these differences align much more closely with IPhonehurricane95's IP socks than those of the UnderArmourKid vandal / User:Lightning Sabre.  Light and Dark2000  (talk) 03:16, 20 February 2018 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

The IPv6 address looks like it could actually be an IPhonehurricane95 sock (IPh95 was the one that started the 9/11 imagery sh*t, along with the first "UnderArmourKid" accounts). However, if the IP is a VPN or a proxy, it's probably the operator of the UnderArmourKid sock family; that being said, if the IP in question is a VPN or proxy, the entire IP range needs to be rangeblocked for a year, per Wikipedia policy.  Light and Dark2000  (talk) 10:32, 16 February 2018 (UTC)

Clerk, CheckUser, and/or patrolling admin comments
— Berean Hunter   (talk)  06:25, 20 February 2018 (UTC)
 * - For a sleeper check. Thanks, GABgab 02:38, 20 February 2018 (UTC)
 * See below.
 * No more tags for this LTA, as per WP:DENY. Closing. GABgab 21:57, 20 February 2018 (UTC)

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

<span style="font-family: Gill Sans MT, Arial, Helvetica; font-weight:140;"> General Ization <i style="color: #000666;">Talk </i> 01:01, 18 February 2018 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

I found another sock. Given the behavior of this sockmaster, a rangeblock would be really helpful here. (The current IP range is 191.116.0.0/16.)  Light and Dark2000  (talk) 01:20, 18 February 2018 (UTC) — Berean Hunter   (talk)  07:01, 20 February 2018 (UTC)
 * I agree that we need a Sleeper Check.  Light and Dark2000  (talk) 01:25, 18 February 2018 (UTC)
 * You might want to revoke that sock's talk page access. Like User:IPhonehurricane95, UAK/Lightning Sabre has a history of using his talk page to dump vandalism and attack other users, even while blocked. The vandalism in question tends to be 9/11 imagery, and if he logs in to that account, vandalism is almost certainly guaranteed.  Light and Dark2000  (talk) 06:50, 20 February 2018 (UTC)

Clerk, CheckUser, and/or patrolling admin comments
Blocked. May need a CU check for sleepers, though. —C.Fred (talk) 01:02, 18 February 2018 (UTC) — Berean Hunter   (talk)  06:25, 20 February 2018 (UTC)
 * as per above. Thanks, GABgab 02:39, 20 February 2018 (UTC)
 * Only one account that wasn't already indeffed:

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

Quack. The account name matches a known naming pattern used by some UAK socks (look at some accounts in the SPI archive), and the vandalism from this account is identical to some of the vandalism observed from past UnderArmourKid socks. Please also run a Sleeper Check, since this vandal is known for leaving behind Sleepers. If this account is UAK, a 3-6 month rangeblock should be implemented on the underlying IP range in order to prevent further socking.  Light and Dark2000  (talk) 11:45, 1 March 2018 (UTC)
 * If this is him, he is probably using the IP range 191.119.0.0/16 to sock, since that range is currently his only unblocked IP range (in recent history). And if he is currently socking with this range, the IP range should be rangeblocked for 6 months to prevent further abuse.  Light and Dark2000  (talk) 12:15, 1 March 2018 (UTC)

Okay. Well, if it is another sockmaster, then are the socks Cacgv and Cacgv1 (which I've just added above) also socks of User:Brendar 1214? Those 2 sock accounts vandalized the same article before a few days before the SpacePenguin25 account. The possible impersonation is interesting, but if true, it would also indicate a troubling trend.  Light and Dark2000  (talk) 20:02, 2 March 2018 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''
 * Amanda, I've followed the UAK LTA for a while, and this didn't smell like him to me. CU results seem about right on this one. ☆ Bri (talk) 01:52, 2 March 2018 (UTC)
 * I'm just not seeing enough behavior matchups with the LTA listed at the top of this page. Vandalism to a hurricane isn't enough on it's own to convince me it's him. UAK has quite a few quirks to go on. More than that I'd rather not say; some LTAs monitor their own sockpuppet investigations. ☆ Bri (talk) 21:22, 2 March 2018 (UTC)

Clerk, CheckUser, and/or patrolling admin comments

 * My guess would have been him, but this is coming up as to, and ❌ to UAK. I would like someone else to independently evaluate behavior, but also consider if this is a copycat before moving cases. --  Amanda  (aka DQ) 19:43, 1 March 2018 (UTC)
 * This is indeed unrelated to UAK. Behaviourally, I'm not seeing a connection to Bar 123; it's inconclusive if there's another sockmaster. Closing.. -- zzuuzz (talk) 20:48, 3 April 2018 (UTC)
 * This is indeed unrelated to UAK. Behaviourally, I'm not seeing a connection to Bar 123; it's inconclusive if there's another sockmaster. Closing.. -- zzuuzz (talk) 20:48, 3 April 2018 (UTC)

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

DUCK per blanking on cyclone pages  Eve rgr een Fir  (talk) 18:54, 21 March 2018 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

It is an unusual username for UAK but the cyclone blanking is suspicious. Also the apparent taunt in one edit summary. ☆ Bri (talk) 18:56, 21 March 2018 (UTC)

I'm starting to think from the last couple of reports here (post-CU), there's some kind of copycat ☆ Bri (talk) 19:27, 21 March 2018 (UTC)

Clerk, CheckUser, and/or patrolling admin comments

 * ❌ to UAK, possibly related to Incorrible Troll, but probably unlikely. -- zzuuzz (talk) 19:08, 21 March 2018 (UTC)
 * ✅ to Sockpuppet investigations/Vandyrandy. -- zzuuzz (talk) 20:40, 21 March 2018 (UTC)

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

Obvious sock is obvious (see the user's edit summaries). CheckUser would be to check for sleepers and/or effect rangeblocks. Jasper Deng (talk) 19:46, 21 March 2018 (UTC)
 * How about User:JotCeVauDe? The vandalism is quite similar compared to that of the other recent accounts. Is this also a sock of Vandyrandy, or is it a sock of User:Wikinger?  Light and Dark2000  (talk) 01:44, 23 March 2018 (UTC)
 * In any event, the underlying IP range(s) of Vandyrandy and JotCeVauDe need to be Rangeblocked for at least 1 month, in order to cut off this rapid socking spree, if they haven't been blocked yet.  Light and Dark2000  (talk) 04:04, 23 March 2018 (UTC)
 * Okay, according to this discussion, JotCeVauDe is a sock of Wikinger, while the other impersonator accounts are all socks of Vandyrandy.  Light and Dark2000  (talk) 06:31, 23 March 2018 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Clerk, CheckUser, and/or patrolling admin comments
It's an impersonator. See Sockpuppet investigations/Vandyrandy. -- zzuuzz (talk) 20:34, 21 March 2018 (UTC)

Suspected sockpuppets



 * Tools: Editor interaction utility • Interaction Timeline • User compare report Auto-generated every hour.

Sock. Source Content Self-Maker (talk) 18:19, 17 August 2018 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Obvious sock is obvious. A CheckUser might not even be needed here, since I've already filed a report at m:SRG.  Light and Dark2000  (talk) 19:18, 17 August 2018 (UTC)

Clerk, CheckUser, and/or patrolling admin comments

 * I indef blocked Anyela Sanchez LAB per WP:DUCK before seeing this SPI. I also blocked the IP range  190.107.228.0/22, apparently used by UnderArmourKid, based on a report at AIV.  -- Ed (Edgar181) 18:32, 17 August 2018 (UTC)

Suspected sockpuppets



 * Tools: Editor interaction utility • Interaction Timeline • User compare report Auto-generated every hour.

WP:Duck. IP and TLG on Aflac (both) and TLG on Bass Pro Shops (see here fav target of the master. <em style="font-family:Rubik;color:Lollipop">JC7V <em style="font-family:Ebrima;color:Purple">-constructive zone  14:11, 20 August 2018 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Clerk, CheckUser, and/or patrolling admin comments

 * Both now blocked. Closing. Bbb23 (talk) 15:01, 20 August 2018 (UTC)

Suspected sockpuppets



 * Tools: Editor interaction utility • Interaction Timeline • User compare report Auto-generated every hour.

Obvious ducks. Requesting a CheckUser to run a Sleeper Check, due to this LTA's tendency for mass sock account creations and leaving behind sleeper accounts. Also, please rangeblock the underlying IP range of the first 3 listed accounts for at least 3–6 months (12 months is ideal), because without rangeblocks, this LTA's history has shown that he will soon return to sock and vandalizing articles en masse, likely at a much higher pace than before (September 2017 is a good analog for comparing his vandalism activity). The underlying IP range(s) is likely one of the 3 that I've listed above, but it could be different. 🌀  Light and Dark2000  (talk) 04:23, 22 September 2018 (UTC)
 * Can you please take a look at this report? This LTA needs to be rangeblocked before he can return to resume his mass vandalism. Thanks. 🌀  Light and Dark2000  (talk) 04:23, 22 September 2018 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''


 * Added CriticalFusionGD & The Lab games obvious ducks, apparently in CU time horizon. ☆ Bri (talk) 04:33, 22 September 2018 (UTC)
 * Those accounts are within the CU time horizon, but the underlying IPs of The Lab games has already been blocked (the IP range of CriticalFusionGD is currently unblocked, though). 🌀  Light and Dark2000  (talk) 04:49, 22 September 2018 (UTC)


 * Another two ducks: CrashCarSeries & SecretSummer, both vandalized LTA case page ☆ Bri (talk) 04:53, 22 September 2018 (UTC)
 * Recommend that and the Architect 134 sockfarm be looked at again. Aflac, hurricanes, etc. quacks. ☆ Bri (talk) 05:03, 22 September 2018 (UTC)
 * I don't think that Architect 134 is behind any of the accounts from this month, though Namedmaker and UAK strikes again! appear to be his attempts to imitate IPhonehurricane95, an unrelated sockmaster that UAK/Lightning Sabre is imitating in his copycat vandalism and unblock requests. 🌀  Light and Dark2000  (talk) 07:17, 22 September 2018 (UTC)

Clerk, CheckUser, and/or patrolling admin comments
All accounts are confirmed UAK except Namedmaker, who is Architect 134. I am confident that UAK has been impersonated several times by Architect 134. Any further IP blocks are not appropriate at this time. -- zzuuzz (talk) 07:56, 22 September 2018 (UTC)

Suspected sockpuppets



 * Tools: Editor interaction utility • Interaction Timeline • User compare report Auto-generated every hour.

See this diff from one of the vandal edits: Special:Diff/929528808. Was also on one of the "targeted" pages listed at UnderArmourKid's long-term abuse page. Master of Time  ( talk ) 11:52, 6 December 2019 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Clerk, CheckUser, and/or patrolling admin comments

 * Blocked, closing. GABgab 23:32, 6 December 2019 (UTC)

Suspected sockpuppets



 * Tools: Editor interaction utility • Interaction Timeline • User compare report Auto-generated every hour.

Recent edits to this very page (among others), obviously. No CU needed to know. Master of Time  ( talk ) 12:00, 6 December 2019 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Clerk, CheckUser, and/or patrolling admin comments

 * Also blocked, closing. GABgab 23:33, 6 December 2019 (UTC)

Suspected sockpuppets



 * Tools: Editor interaction utility • Interaction Timeline • User compare report Auto-generated every hour.

This LTA has generated new accounts within the past few months. However, I don't recall a sleeper check being run on any of them (I don't recall a CU being run on any of this LTA's socks in months). The IP range definitely belongs to him, given the behavior, and the pattern of vandalism there leads me to believe that he is currently using the same IP range (if this is the case, a CU on the range should reveal some sock accounts). Please run a sleeper check on both the accounts and the IP range, because this LTA has a long history of serial socking and leaving behind sleepers. And if he has been abusing the range recently, the IP range should receive a multi-month rangeblock, because otherwise, nothing will stop him from continuing to vandalize this site.  Light and Dark2000  🌀 (talk) 19:31, 28 August 2020 (UTC)
 * Can someone please run a sleeper check and apply the IP blocks? Thanks.  Light and Dark2000  🌀 (talk) 19:32, 28 August 2020 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Clerk, CheckUser, and/or patrolling admin comments

 * There are some other accounts on the range, but most are locked already, and there's nothing recent. Closing. ST47 (talk) 04:20, 3 September 2020 (UTC)
 * There are some other accounts on the range, but most are locked already, and there's nothing recent. Closing. ST47 (talk) 04:20, 3 September 2020 (UTC)

Suspected sockpuppets



 * Tools: Editor interaction utility • Interaction Timeline • User compare report Auto-generated every hour.

Similar usernames of master and same pattern of disruption. Creating SPI retro-actively for record-keeping and historical purposes.  ~Oshwah~  (talk) (contribs)   01:38, 17 November 2020 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Clerk, CheckUser, and/or patrolling admin comments



 * Also found and ✅:
 * All have been indef'd and tagged. Created SPI report retro-actively after running into the two accounts in the new user log.  ~Oshwah~  (talk) (contribs)   01:41, 17 November 2020 (UTC)
 * All have been indef'd and tagged. Created SPI report retro-actively after running into the two accounts in the new user log.  ~Oshwah~  (talk) (contribs)   01:41, 17 November 2020 (UTC)
 * All have been indef'd and tagged. Created SPI report retro-actively after running into the two accounts in the new user log.  ~Oshwah~  (talk) (contribs)   01:41, 17 November 2020 (UTC)
 * All have been indef'd and tagged. Created SPI report retro-actively after running into the two accounts in the new user log.  ~Oshwah~  (talk) (contribs)   01:41, 17 November 2020 (UTC)
 * All have been indef'd and tagged. Created SPI report retro-actively after running into the two accounts in the new user log.  ~Oshwah~  (talk) (contribs)   01:41, 17 November 2020 (UTC)
 * All have been indef'd and tagged. Created SPI report retro-actively after running into the two accounts in the new user log.  ~Oshwah~  (talk) (contribs)   01:41, 17 November 2020 (UTC)


 * GeneralNotability (talk) 02:11, 17 November 2020 (UTC)

Suspected sockpuppets



 * Tools: Editor interaction utility • Interaction Timeline • User compare report Auto-generated every hour.

On the Spanish Wikipedia, several Mexico City Metro/Santiago Metro-related pages are protected due to vandalism by a user commonly called "Conejo" (Rabbit).

Apparently the user, whose original account is named "HabíaUnaVezUnConejo" (OnceUponATimeARabbit), now globally locked, has now moved here.

All the new accounts have edited Aflac, and as you can see with Onceuponatime, Sebastián Piñera is a common target as well. (CC) Tb hotch <big style="color: #555555;">™ 15:53, 11 November 2020 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Clerk, CheckUser, and/or patrolling admin comments



 * No comment in respect to their connectivity to the master. Accounts are indef'd and tagged.  ~Oshwah~  (talk) (contribs)   02:03, 12 November 2020 (UTC)
 * No comment in respect to their connectivity to the master. Accounts are indef'd and tagged.  ~Oshwah~  (talk) (contribs)   02:03, 12 November 2020 (UTC)
 * No comment in respect to their connectivity to the master. Accounts are indef'd and tagged.  ~Oshwah~  (talk) (contribs)   02:03, 12 November 2020 (UTC)


 * Sure looks like UAK., closing. GeneralNotability (talk) 01:54, 17 November 2020 (UTC)

Suspected sockpuppets



 * Tools: Editor interaction utility • Interaction Timeline • User compare report Auto-generated every hour.

Same vandalism and same "HCH"; also see below discussion.

Firestar464 (talk) 12:17, 19 November 2020 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

This is pretty clearly UAK or a copycat, as is. I've requested glocks for the three. Best, Blablubbs (talk • contribs) 12:20, 19 November 2020 (UTC)
 * These are definitely socks - the response after being blocked by Chadwick removed any doubt on that one being like the other two. If we could get a sweep for any accounts created after those were blocked that could be helpful - the individual appears to create them sequentially Nosebagbear (talk) 13:16, 19 November 2020 (UTC)
 * , Martin Urbanec performed an LWCU which turned up (now glocked). He also globally blocked an associated IP after the vandalism moved to meta . I'm not sure how much an enwiki sleeper check will give us here – but it might still be worth a try. Best, Blablubbs (talk • contribs) 13:21, 19 November 2020 (UTC)
 * Are these all (possible) socks? If so, a CheckUser may be needed. Firestar464 (talk) 10:35, 20 November 2020 (UTC)
 * , these are socks, yes. Since they're all ducks, and all globally locked (and an associated IP has been globally blocked for a month), the main use of CU I can see here would be to run a sleeper check and see if any other underlying IPs are blockable. I also assume that this case should be merged into the relevant SPI. Blablubbs (talk • contribs) 10:57, 20 November 2020 (UTC)
 * How do we run the sleeper check? Merged. Firestar464 (talk) 11:26, 20 November 2020 (UTC)

Clerk, CheckUser, and/or patrolling admin comments

 * Everyone is blocked or globally locked. No need for tags since this is an LTA. I don't think there's much value in CU here; Martin's already done an LWCU and since these are throwaway accounts I don't think we're likely to find local sleepers. Closing. GeneralNotability (talk) 02:53, 21 November 2020 (UTC)

Suspected sockpuppets



 * Tools: Editor interaction utility • Interaction Timeline • User compare report Auto-generated every hour.

Vandalizing the Jimmie Johnson, Richard Petty, and American Airlines Flight 11 articles, like other socks have done. <b style="background:#006A4D; padding:2px"> NASCARfan0548  ↗ </b> 19:31, 3 December 2020 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Clerk, CheckUser, and/or patrolling admin comments

 * ✅, blocked. -- zzuuzz (talk) 19:49, 3 December 2020 (UTC)


 * Fixing tag. Archive. Dreamy <i style="color:#d00">Jazz</i> talk to me &#124; my contributions 02:29, 4 December 2020 (UTC)

Suspected sockpuppets



 * Tools: Editor interaction utility • Interaction Timeline • User compare report Auto-generated every hour.

I'm pretty sure this is Long-term abuse/UnderArmourKid, vandalism on cyclone Larry with one asking for an unblock of Underarmourkid (see rockman x5 talk page). If it is him then global locks will probably be needed. Pahunkat (talk) 12:33, 31 December 2020 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Clerk, CheckUser, and/or patrolling admin comments

 * ✅. Bagging and tagging. This SPI report can be closed...  ~Oshwah~  (talk) (contribs)   12:50, 31 December 2020 (UTC)

Suspected sockpuppets



 * Tools: Editor interaction utility • Interaction Timeline • User compare report Auto-generated every hour.

First three edits match documented interests of LTA: NASCAR, Aflac, Home Depot/Office Depot.

Note that another sock was at Home Depot a few tens of hours ago, also Richard Petty where they explicitly claim to be the LTA. ☆ Bri (talk) 19:33, 2 January 2021 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Clerk, CheckUser, and/or patrolling admin comments

 * Bagging and tagging confirmed sock.  ~Oshwah~  (talk) (contribs)   21:31, 2 January 2021 (UTC)
 * Bagging and tagging confirmed sock.  ~Oshwah~  (talk) (contribs)   21:31, 2 January 2021 (UTC)
 * Bagging and tagging confirmed sock.  ~Oshwah~  (talk) (contribs)   21:31, 2 January 2021 (UTC)
 * Bagging and tagging confirmed sock.  ~Oshwah~  (talk) (contribs)   21:31, 2 January 2021 (UTC)
 * Bagging and tagging confirmed sock.  ~Oshwah~  (talk) (contribs)   21:31, 2 January 2021 (UTC)


 * Likely account has since been blocked for vandalism and globally locked for long term abuse. Confirmed account is blocked locally and there is a SRG request open for that account. Tagging likely sock as a sock. Close. Dreamy <i style="color:#d00">Jazz</i> talk to me &#124; my contributions 23:05, 2 January 2021 (UTC)

Suspected sockpuppets



 * Tools: Editor interaction utility • Interaction Timeline • User compare report Auto-generated every hour.

Obvious due to edits. Report and CU request made solely for sleeper check, as this LTA is known to have sleepers. Steve M (talk) 17:47, 2 February 2021 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Clerk, CheckUser, and/or patrolling admin comments
Confirmed and -- zzuuzz (talk) 18:09, 2 February 2021 (UTC)

Suspected sockpuppets



 * Tools: Editor interaction utility • Interaction Timeline • User compare report Auto-generated every hour.

As usual, this LTA has sleepers, so a CU will rat out all the sleepers. Steve M (talk) 18:19, 3 February 2021 (UTC)

Comments by other users
Is it possible to check 6 new Uaks? Steve M (talk) 20:25, 3 February 2021 (UTC)

Clerk, CheckUser, and/or patrolling admin comments

 * ✅. .  ~Oshwah~  (talk) (contribs)   19:44, 3 February 2021 (UTC)
 * Steve M - 6 new Uaks is ✅. Bagged and tagged.  ~Oshwah~  (talk) (contribs)   20:43, 3 February 2021 (UTC)

Suspected sockpuppets

 * ( original case name)


 * Tools: Editor interaction utility • Interaction Timeline • User compare report Auto-generated every hour.

You've dealt with this guy before, presumably. L&D2K believes it's him. here ~ Destroyeraa 🌀🇺🇸 20:27, 3 February 2021 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Clerk, CheckUser, and/or patrolling admin comments

 * See above; 6 New Uaks is ✅ and has been blocked. Closing SPI...  ~Oshwah~  (talk) (contribs)   20:47, 3 February 2021 (UTC)

Suspected sockpuppets



 * Tools: Editor interaction utility • Interaction Timeline • User compare report Auto-generated every hour.

CU to catch sleepers. Sock is obvious based on edits. Steve M (talk) 13:15, 9 February 2021 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''
 * GD in the username is also a hallmark of the LTA. ☆ Bri (talk) 14:15, 9 February 2021 (UTC)

Clerk, CheckUser, and/or patrolling admin comments

 * - -- RoySmith (talk) 17:04, 9 February 2021 (UTC)
 * ✅ plus . ., closing. Mz7 (talk) 01:32, 10 February 2021 (UTC)

Suspected sockpuppets



 * Tools: Editor interaction utility • Interaction Timeline • User compare report Auto-generated every hour.

Sleeper check as usual. Edit summary confirms sock. Steve M (talk) 23:02, 10 February 2021 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Clerk, CheckUser, and/or patrolling admin comments

 * ✅. . This SPI can be closed...  ~Oshwah~  (talk) (contribs)   06:11, 12 February 2021 (UTC)