Wikipedia:Sockpuppet investigations/Sidowpknbkhihj/Archive

Suspected sockpuppets



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

After 153.214.208.62 claimed that this user is the sockpuppet of a globally locked user, i have decided to check this user's talk page on jawiki. Then I checked the Sidow's edits and here is the evidence I can find: Since Sidowpknbkhihj and 台風14号 did not have the same interests I'm requesting a CheckUser investigation.  SMB9 9thx   my edits  04:41, 25 August 2020 (UTC)
 * Both Sidow and 台風14号 ignored warnings numerous times on enwiki, though 台風14号 at least finally responded after I sent a final warning to their talk page.
 * Rejects any edits that are against what they want (which led me into warning them against article ownership back two weeks ago).
 * Since 153.214.208.62 claimed that 台風14号 is the Sidowpknbkhihj led me to opening this sockpuppet investigation casepage, i have notified the IP to this casepage.  SMB9 9thx   my edits  04:55, 25 August 2020 (UTC)
 * I always requested CheckUser in every SPI I was involved in, but i want to take a step back this time around.  SMB9 9thx   my edits  07:27, 25 August 2020 (UTC)

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

In the Japanese Wikipedia, admitted being the sockpuppet of.

With this diff in the Japanese Wikipedia, 台風14号 stated that he/she is the same person as
 * , and
 * , and
 * , and
 * , and
 * , and
 * , and
 * , and

In the English Wikipedia,
 * , and
 * have been indefinitely blocked as the sockpuppets of Sidowpknbkhihj. With this diff in the Japanese Wikipedia, 台風14号 included these four accounts in his/her sockpuppet list.
 * , and
 * have been indefinitely blocked as the sockpuppets of Sidowpknbkhihj. With this diff in the Japanese Wikipedia, 台風14号 included these four accounts in his/her sockpuppet list.

Since Sidowpknbkhihj evades his/her block by using the 台風14号 account, I think 台風14号 also needs to be indefinitely blocked from editing the English Wikipedia, too. 153.214.208.62 (talk) 05:38, 25 August 2020 (UTC)
 * Yes, I was using sock puppets. sorry. But now, I deeply regret deeply and vow not to use the sock puppets any more. This "台風14号" account is my main account. Therefore, I pledge that I will never use any account other than this account in the future.--台風14号 (talk) 07:48, 25 August 2020 (UTC)

On 's contribs log, other users such as have continued to revert this user's contribs because they violated one policy or another, especially WP:BRD. ~ Destroyeraa 🌀 13:47, 25 August 2020 (UTC)

Clerk, CheckUser, and/or patrolling admin comments

 * There's no activity on enwiki for action. There's plenty there for global locks as ja-CU confirmed and self-admitted socks of LTA Sidowpknbkhihj. Cabayi (talk) 15:24, 25 August 2020 (UTC)
 * Blocked 台風14号 & filed global lock request for all the unlocked accounts. Cabayi (talk) 15:33, 25 August 2020 (UTC)

Suspected sockpuppets



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

Looking from CU evidence, Typhoon Meranti is blocked as a block evasion of ソングダー, which is a globally locked sock of Sidowpknbkhihj. Using diffs itself, Typhoon Meranti is a with these edits:
 * Removing redirects: new sock (previous sock)
 * "I split from" new sock (previous sock)

Since Typhoon Meranti was a subject of global lock request, i think there is no need for action against the sock. However, it is connected with other socks 迂回マン and 458 Pilgrim, which means actions against the sock is necessary. 迂回マン edited the talk page of the user NORECH which was a target of earlier Sidowpknbkhihj socks: new sock (notifying NORECH about creation of the article Pilgrim Airlines Flight 458 which was created by Typhoon Meranti), previous sock 1, previous sock 2. Typhoon Meranti's creation Pilgrim Airlines Flight 458 are direct copies of the 458 Pilgrim's sandbox and draft (and blanked by Typhoon Meranti, despite it was not submitted yet), which suggest connection between the two.

Requesting CU for technical evidence.  SMB9 9thx   my edits  10:03, 31 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

 * These ones are ✅:
 * , requesting locks. ST47 (talk) 23:20, 31 August 2020 (UTC)
 * , requesting locks. ST47 (talk) 23:20, 31 August 2020 (UTC)
 * , requesting locks. ST47 (talk) 23:20, 31 August 2020 (UTC)
 * , requesting locks. ST47 (talk) 23:20, 31 August 2020 (UTC)
 * , requesting locks. ST47 (talk) 23:20, 31 August 2020 (UTC)
 * , requesting locks. ST47 (talk) 23:20, 31 August 2020 (UTC)
 * , requesting locks. ST47 (talk) 23:20, 31 August 2020 (UTC)
 * , requesting locks. ST47 (talk) 23:20, 31 August 2020 (UTC)
 * , requesting locks. ST47 (talk) 23:20, 31 August 2020 (UTC)
 * , requesting locks. ST47 (talk) 23:20, 31 August 2020 (UTC)
 * , requesting locks. ST47 (talk) 23:20, 31 August 2020 (UTC)
 * , requesting locks. ST47 (talk) 23:20, 31 August 2020 (UTC)
 * , requesting locks. ST47 (talk) 23:20, 31 August 2020 (UTC)
 * , requesting locks. ST47 (talk) 23:20, 31 August 2020 (UTC)

Suspected sockpuppets



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

I translate/copied/split from (oldid=) edit summaries (Vandjn, Typhoon Meranti, 台風14号) -. Requesting CU for technical evidence and sleepers.  SMB9 9thx   my edits  05:06, 2 September 2020 (UTC)


 * Update: Globally locked alongside new sock ラスじゃ on the same day. I'm still requesting CU if more sleepers show up.  SMB9 9thx   my edits  12:03, 2 September 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

 * ✅ plus the following accounts:
 * . Global locks requested. Closing. Mz7 (talk) 06:37, 3 September 2020 (UTC)
 * . Global locks requested. Closing. Mz7 (talk) 06:37, 3 September 2020 (UTC)
 * . Global locks requested. Closing. Mz7 (talk) 06:37, 3 September 2020 (UTC)

Suspected sockpuppets



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

Posiko because of the obvious edit summaries (use of 'oldid='): new sock (previous sock). Nillew came from ja:Wikipedia‐ノート:投稿ブロック依頼/Sidowpknbkhihj. Remaining three other possible socks are found from ja:Wikipedia:管理者伝言板/投稿ブロック/ソックパペット. Requesting CU if they are linked and if there is more sleepers.  SMB9 9thx   my edits  10:06, 7 September 2020 (UTC)
 * Please note that account doesn't exist on en.wiki, as such i removed the account from the list to prevent messing up the CU request. However, in any event that account is registered on enwiki I will add them to the list again, as that account exists on ja:Wikipedia:管理者伝言板/投稿ブロック/ソックパペット.  SMB9  9thx   my edits  12:27, 7 September 2020 (UTC)
 * Note: There is one more account, which was identified as a 'reference' sock in ja:Wikipedia‐ノート:投稿ブロック依頼/スカイ13 (スカイ13 is an old sock of Sidowpknbkhihj). This suspected sock just recently got added on ja:Wikipedia:管理者伝言板/投稿ブロック/ソックパペット, and I already put this possible sock on the global request in suspicion of being the same person as the Sidowpknbkhihj - and i found out about this possible sock just recently. However i'm not sure if that account is a sock or not, and this account has not been active since 29 August 2019, so I will not add this to the list.  SMB9  9thx   my edits  02:12, 8 September 2020 (UTC)

Update: Most of the socks mentioned here are now globally locked, with the exception of Denbau and マリスリス (not on enwiki). Not dropping my CU request for possible link with Denbau and sleepers. Also adding a sock, found on the ja:Wikipedia:管理者伝言板/投稿ブロック/ソックパペット.  SMB9 9thx   my edits  04:02, 12 September 2020 (UTC)

All of these socks are now globally locked. There's nothing to do here. Can SPI clerks close this? I also filed a global ban request for comment on Meta, as suggested below.  SMB9 9thx   my edits  07:31, 18 September 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

 * Everyone's globally locked. Closing. GeneralNotability (talk) 17:39, 18 September 2020 (UTC)

Suspected sockpuppets

 * ( original case name)


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

Several similar edits on tropical storm pages, see this edit history for example, and user was created shortly after the sockpuppeteer was blocked.  Onel 5969  TT me 11:43, 16 September 2020 (UTC)

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

Requesting CU. By the way, this account was created around the time when older socks of Sidowpknbkhihj got blocked, not after Typhoon No.14 got blocked.  SMB9 9thx   my edits  23:44, 16 September 2020 (UTC)

Definitely a sockpuppet. See this: and. Sidowpknbkhihj should be locked on all meta accounts and be banned from creating new accounts, along with his IP address and all his socks should be locked and prevented from account creation!~ Destroyeraa 🌀 00:01, 18 September 2020 (UTC)
 * , which means it's a global ban. I'm thinking about starting an RfC on it.  SMB9 9thx   my edits  02:11, 18 September 2020 (UTC)

All of these socks are now globally locked. There's nothing to do here. Can SPI clerks close this? I also filed a global ban request for comment on Meta, as suggested here.  SMB9 9thx   my edits  07:31, 18 September 2020 (UTC)

Clerk, CheckUser, and/or patrolling admin comments

 * moved to Sidowpknbkhihj. Dreamy Jazz talk to me &#124; my contributions 12:46, 16 September 2020 (UTC)


 * - the suspected accounts are all locked (and I presume they were locked as socks of this master), but can we get a sleeper check please? GeneralNotability (talk) 20:16, 18 September 2020 (UTC)
 * No unlocked sleepers immediately visible. Closing. Kevin ( aka L235 · t · c) 17:23, 20 September 2020 (UTC)

Suspected sockpuppets


This is the newly reported account on ja:Wikipedia:進行中の荒らし行為/長期/ヒースロー.There are many similarities, such as creating articles related to earthquakes. In addition, when an edit by another sock puppet is returned, the edit is canceled by these account. These account also creates articles that originate only from Kotobank, which is one of Sidowpknbkhihj's characteristics. For these reasons, we request a sock puppet survey by CU.2400:2410:C1C0:9800:C105:7DD5:96D9:7257 (talk) 07:22, 22 September 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

 * None of these 3 socks have edited enwiki. They've all edited on jawiki where there's a case running. Two have edited on data. Nothing to do here. Cabayi (talk) 08:06, 22 September 2020 (UTC)
 * Copy filed on data - d:Special:Permalink/1280552238. Cabayi (talk) 08:17, 22 September 2020 (UTC)
 * ...and declined on data. The jawiki investigation is the only viable investigation. Cabayi (talk) 08:53, 22 September 2020 (UTC)

Suspected sockpuppets


A new account has emerged to edit hurricane-related articles. This account creating articles based on Kotobank. This is a feature of Heathrow LTA.2400:2410:C1C0:9800:24B9:9912:65F8:18EE (talk) 11:57, 5 October 2020 (UTC)

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

Kept on adding "Other" section preferred by socks. Which is why I cleaned up the article in the first place.  SMB9 9thx   my edits  08:10, 6 October 2020 (UTC)

Clerk, CheckUser, and/or patrolling admin comments

 * This is ✅. This account and a number of others have already been globally locked so I haven't blocked or tagged them. Closing. Callanecc (talk • contribs • logs) 06:32, 7 October 2020 (UTC)

Suspected sockpuppets
It looks like is one of the socks of, also known as the vandal ja:LTA:HEATHROW in the Japanese Wikipedia. was active in the English Wikipedia from 30 September to 22 October 2022, and is now globally-locked as Sidowpknbkhihj's sock. Compasu and Mafing have often edited storm/typhoon-related pages, making the redirects and/or moving the articles; compare Compasu's edit on 31 October 2022 and Mafing's edit on 10 October 2022. Requesting checkuser because I am afraid that there are other sleepers.

For what it's worth, below, I would like to add some of the IP ranges that seem to be used by Sidowpknbkhihj in the English Wikipedia. A bunch of IP ranges got blocked, most of them for 1 year, as Sidowpknbkhihj's IP socks in the Japanese Wikipedia. Sidowpknbkhihj's IP ranges are listed at ja:LTA:HEATHROW/USER.



I think Sidowpknbkhihj's IP ranges need to be blocked in the English Wikipedia, as in the Japanese Wikipedia. For example, restored 's edit at Typhoon Vicki; compare 台風20177's edit in 2020 and 126.255.227.108's edit in 2022. Furthermore, Compasu appeared 6 minutes after 126.255.227.108's edit at the same article. 2400:4050:C222:B700:AD5C:4636:C9F5:5E7D (talk) 23:38, 31 October 2022 (UTC)

Comments by other users

 * Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Thanks. All locked. マードン and Tenteng on enwiki are same person :) --Sotiale (talk) 11:48, 1 November 2022 (UTC)
 * Thanks, Blablubbs. Same person and locked. --Sotiale (talk) 12:09, 1 November 2022 (UTC)

Clerk, CheckUser, and/or patrolling admin comments

 * -  Girth Summit  (blether)  10:58, 1 November 2022 (UTC)
 * is fairly to . Given the very similar editing, I'm going to block and request lock - pinging  who seems to be familiar with this LTA.   Girth Summit  (blether)  11:11, 1 November 2022 (UTC)
 * No comments on the IPs; leaving this open in case a clerk wants to consider range blocks.  Girth Summit  (blether)  11:14, 1 November 2022 (UTC)
 * There's also . Behavioural match and technically somewhere in the neighbourhood of . Ping in case you want to lock this one as well.  --Blablubbs (talk) 11:57, 1 November 2022 (UTC)
 * Those IP ranges aren't lighting up - closing this, we can look again if the disruption starts up again.  Girth Summit  (blether)  19:04, 2 November 2022 (UTC)

Suspected sockpuppets
FYI Special:CentralAuth/伊勢湾台風, request for checking sleepers. Lemonaka (talk) 18:31, 24 November 2022 (UTC)
 * @Bbb23 and @Salvio giuliano, created a pile of mess by randomly moving articles to other places. A lot of sweeping needed to be done after checking and block. Lemonaka (talk) 02:26, 25 November 2022 (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, tagged, glock requested, leaving CU request. Bbb23 (talk) 18:51, 24 November 2022 (UTC)
 * Adding:
 * Salvio 22:07, 24 November 2022 (UTC)
 * - please indef the three accounts above as proven socks, they are obviously linked to the master based on the interest in hurricanes (see also ). Thanks, Spicy (talk) 02:34, 26 November 2022 (UTC)
 * Blocked and tagged per request; also requested global locks. Bbb23 (talk) 02:43, 26 November 2022 (UTC)
 * - please indef the three accounts above as proven socks, they are obviously linked to the master based on the interest in hurricanes (see also ). Thanks, Spicy (talk) 02:34, 26 November 2022 (UTC)
 * Blocked and tagged per request; also requested global locks. Bbb23 (talk) 02:43, 26 November 2022 (UTC)

Suspected sockpuppets
Like the recent socks, , and , Negmegirin and the 126 IPs appeared on typhoon-related articles, creating/moving multiple pages and opening multiple move requests. For example, they created a draft page as an IP user and moved it to the main space as an account user; compare Special:Log/伊勢湾台風 and Special:Log/Negmegirin. See also Compasu's move request and 126.253.172.31's move request. For what it's worth, the vandal ja:LTA:HEATHROW's IP ranges are listed at ja:LTA:HEATHROW/USER. 2400:4050:C222:B700:39B8:B6D3:577F:6887 (talk) 06:49, 2 December 2022 (UTC)


 * Pretty blatant sockpuppetry via IP hopping. The editor is restoring edits by their blocked accounts which were previously reverted. Yue 🌙 07:27, 2 December 2022 (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

 * CU data isn't as helpful here as it is in some other cases, but Negmegirin looks like them. Blocked the account, . --Blablubbs (talk) 19:18, 4 December 2022 (UTC)
 * Tagged Negmegirin and requested a lock. The IPs have not been active recently and a rangeblock is not going to be possible. Closing. Thanks, Spicy (talk) 05:10, 7 December 2022 (UTC)

Suspected sockpuppets
This IP has just opened up a requested move discussion. This on its own is not suspicious, however, it reminds me a lot of the logic of the moves preformed by Special:Contributions/Compasu. There have been other IPs during the meantime proposing Requested moves as well, see for a few examples. 12.207.51.104 (talk) 16:29, 29 December 2022 (UTC) 12.207.51.104 (talk) 16:29, 29 December 2022 (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 IP has not edited recently, closing. This user has access to several wide ranges and individual IP blocks are not going to accomplish much. Requesting semi-protection on frequently targeted pages would be a better approach. Spicy (talk) 15:14, 3 January 2023 (UTC)

Suspected sockpuppets
Per CA, not so obvious socking. Check or not depend on Clerks. -Lemonaka‎ 09:11, 28 February 2023 (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 globally locked, no other accounts on the IP they used here, no action required here, closing.  Girth Summit  (blether)  16:26, 28 February 2023 (UTC)