Steward requests/Global

From Meta, a Wikimedia project coordination wiki
Jump to navigation Jump to search
← Requests and proposals Steward requests (Global) latest archive→
Shortcut:
SRG

This page hosts requests for global (un)blocks, (un)locks and hidings.

If you are here because you have been affected by a global block, please see Global blocks/FAQ for more information about global block and routes to appeal.

Note: (un)blocks apply to IP addresses; and (un)locks apply to global accounts.


Cross-wiki requests
Meta-Wiki requests

Requests for global (un)block

Symbol comment vote.svg Please be sure to follow the instructions below:
Your request might be rejected if you don't follow the instructions.
Please also review Global blocking . Only IP addresses can be globally blocked at this moment. Please see #Requests for global (un)lock and (un)hiding if your request involves an account.
Global blocks don't affect Meta-Wiki, so if your IP address is blocked, you can still appeal here. IP addresses that cause disruption on Meta should be reported at Meta:Requests for help from a sysop or bureaucrat instead of here so that they can be blocked locally.
Please describe the kind of cross wiki abusive activity you see from the IP. Saying an IP is a long term abuser is not helpful, but saying "IP vandalizes at ban.wikipedia, no.wikipedia and vi.wikipedia" is. This is especially important for range blocks. If you do not provide enough details, your request might be declined.
Instructions for making a request

Before requesting, make sure that:

  1. You know the IP address(es) you wish to have globally blocked or unblocked.
  2. For blocks, the global blocking criteria are met.
  3. For unblocks, your request addresses the original reason for blocking the IP, if any.

To make a request for the address(es) to be blocked or unblocked

Copy the template below to the bottom of this section and explain why the address(es) should be blocked/unblocked.
=== Global block/unblock for [[Special:Contributions/Some IP address|Some IP address]] ===
{{Status}} <!-- Do not remove this template -->
* {{Luxotool|IP address}}
Description, evidence, diffs, etc. --~~~~
When requesting that your IP be unblocked, note that stewards need to know your IP address to even consider a request.
To find your IP, please visit https://www.whatismyip.com/
You are not required to disclose your IP in public - you may make requests privately to any steward on IRC or by email at: stewards@wikimedia.org

Global unblock for 185.89.36.0/22

Status:    On hold

This was blocked in 2021 as an OP, but in the meantime the range is used by the German internet provider InternetNord ([1]). One of their customers complained to the German VRTS. I have already made an exempt for the range block on dewiki, but I would also request a total unlock globally. Thanks, XenonX3 (talk) 12:18, 23 February 2022 (UTC)

@Martin Urbanec: --Alaa :)..! 14:03, 25 May 2022 (UTC)

Global unblock for 2001:470::/32

Status:    In progress

The block reason incorrectly identifies this range as an open proxy. It's neither proxy nor open. I learned that some admins believe the Hurricane Electric's service makes it “like” an open proxy, but note that none of the reasons usually given as the rationale for the no open proxies policy apply to it. There is no anonymity nor particularly high potential of abuse. There is no reason why blocking individual /64 or /48 networks wouldn't be effective in case of abuse.--MwGamera (talk) 22:35, 29 March 2022 (UTC)

Oppose Oppose You say that there is no particularly high potential of abuse, but that doesn't match our logs. It's full of spambots. AntiCompositeNumber (talk) 03:16, 31 March 2022 (UTC)
The Internet is full of spambots and it would be surprising for a range this huge to carry only benign traffic. I don't have any visibility into Wikimedia logs so can't comment on the actual numbers. Is there any reason why they couldn't be blocked individually like in all the other ranges? In any case, the block reason given doesn't match reality (it's not even weasel worded like the one on EN wiki) and I considered it prudent to try to fix the situation before requesting an exemption from a block that from my POV goes against the guidelines.--MwGamera (talk) 18:02, 4 April 2022 (UTC)
Support Support This block hurts me and other people. HE 6to4 tunnel is necessary for my work, ISPs in my area do not give native IPv6. --Kawtaj (talk) 07:07, 7 May 2022 (UTC)
Support Support This block hurts me, and I expect other people. My ISP doesn’t give good IPv6 access, and HE tunnelserver.org tunnels are my only good option. Lionel Elie Mamane (talk) 01:43, 23 May 2022 (UTC)
This is an open proxy/web host/colocation provided, used by one or more VPN services, if I'm not mistaken. If users with cross-wiki constructive contributions are affected, you can request a global IP block exemption. I can definitely attest to the Hurricane Electric LLC IP ranges being used for abuse and spambots on Miraheze as well. Dmehus (talk) 02:08, 23 May 2022 (UTC)
It is not an open proxy nor a web host. Every user has a separate, identifiable, and individually bannable prefix routed to them (although possibly more than one). There might be, and there likely are, some open proxies, web hosts, VPNs, etc, as well as spambots and other sources of abusive traffic in it, but that doesn't explain why should the whole range be blocked instead of just the networks with those. Or why should it be claimed to be an open proxy if the actual reason for blocking is some actual (ongoing?) cross-network abuse.--MwGamera (talk) 21:02, 27 May 2022 (UTC)
I can only second this request. This range hasn't been blocked until some point in 2020. At least unblock people from editing when logged in. But in general don't impose a general block because most users will be legitimate, like every normal network. Just block /64 or /48 after abuse has been noticed. --Treysis (talk) 09:18, 1 June 2022 (UTC)

Global block for proxy ranges

Status:    In progress

Proxies used in cross-wiki abuse: [2], [3], [4], [5]. ----*Fehufangą ♮ ✉ Talk page ♮ 05:14, 10 May 2022 (UTC)

Global unblock for 147.161.237.87

Status:    In progress

When trying to edit a page, I received the block error "The IP address or range 147.161.237.87 has been globally blocked (disabled) by Jon Kolbert for the following reason(s): Open proxy/Webhost. This block will expire on 15:19, 31 October 2024."

This assessment is incorrect; the IP listed is part of a larger range operated by ZScaler (AS62044, 147.161.236.0/23 as well as many others). The IP range is used for Internet egress for corporate customers, who use ZScaler products for MFA-secured access to internal networks. My employer mandates use of ZScaler and it cannot be disabled on the machine. ZScaler do not operate any open public proxies, nor do they offer "privacy" VPN products, it's purely business use for SMEs & corporates. --Chris W. (talk | WP profile) 13:12, 16 May 2022 (UTC)

Support Support The block reason incorrectly identifies this range as an open proxy. It's neither proxy nor open. I learned in an earlier request that some admins believe the Hurricane Electric's service makes it “like” an open proxy, but note that none of the reasons usually given as the rationale for the no open proxies policy apply to it. There is no anonymity nor particularly high potential of abuse. This should allow to run a sleeper check, if there is indeed sleepers in this range. XJ999 (talk) 21:28, 4 August 2022 (UTC)

Global block for 49.228.0.0/18

Status:    In progress

Spammy range, see [6]. ----Minorax«¦talk¦» 15:23, 30 May 2022 (UTC)

Ping @Teles, considering you acted on #Global block for 49.228.17.157. ~~~~
User:1234qwer1234qwer4 (talk) 09:42, 5 June 2022 (UTC)

Global block/unblock for 37.128.219.241

Status:    In progress

The IP is static. The user adds the Danish cast of several TV series to non-Danish pages.[7][8][9] The user is already blocked up to 2028 at en.wiki[10], so I would highly recommend a long-term block because I just reverted this person on multiple wikis that seem to lack recent patrollers. --Tbhotch (talk) 20:35, 30 May 2022 (UTC)

Global block for 80.246.28.0/24

Crosswiki abuse and VPN/Open Proxy. --Codc (talk) 23:56, 2 June 2022 (UTC)

Global block for 103.153.2.0/24

Status:    In progress

Open proxy. --reNVoy (user talk) 14:10, 3 June 2022 (UTC)

@Renvoy What makes you say this entire range is an open proxy? AntiCompositeNumber (talk) 01:54, 5 June 2022 (UTC)
QBA-bot blocked handful of IPs from that range. Generally there is weird activity that involves LTA Marsuki s.kom + several IPs from that range were indicated as Tor Connection. reNVoy (user talk) 11:28, 5 June 2022 (UTC)

Global block for 8.21.110.0/24

Status:    In progress

Cloudflare / Firefox VPN. --reNVoy (user talk) 10:52, 29 June 2022 (UTC)

Global lock IP rangeblock requested (85.140.14.80/16)

Status:    In progress

Per my talk, a trusted user from en.wp has requested the following:

Hi. Since the "Steward requests/Global" is semi-protected, I was wondering whether it's possible for you to ask for the 85.140.14.80/16 IP range to be globally blocked? They have already been blocked on various projects, including: ru.wp, fr.wp, es.wp, wikidata, nl.wp, de.wp, etc. Many thanks.

Please review for the suitability of blocking these IPs. Thanks. —Justin (koavf)❤T☮C☺M☯ 17:19, 29 June 2022 (UTC)

Moved to appropriate section. ~~~~
User:1234qwer1234qwer4 (talk) 17:40, 29 June 2022 (UTC)

Global block for 102.182.0.0/16

Status:    In progress

Open proxy. --NguoiDungKhongDinhDanh 13:02, 5 July 2022 (UTC)

Global block for 86.120.190.41

Status:    In progress

Long-term abuse. Cross-wiki abuse. see ro:Wikipedia:Afișierul administratorilor/Arhiva/2021#Vandal logo-uri (adrese IP dinamice). --Johannnes89 (talk) 14:36, 6 July 2022 (UTC)

Global block for 103.60.128.0/18

Status:    In progress

Cross-wiki and long-term abuse. Already blocked in several wikis and already globally blocked from last 12 February to 12 May. Active again soon after the global block expired. --GC85 (talk) 17:50, 12 July 2022 (UTC)

Global block for 109.107.171.0/24

Status:    In progress

Cross-wiki abuse. VPN. --reNVoy (user talk) 20:24, 12 July 2022 (UTC)

Global block for 2604:3D08:6286:7500::/64

Status:    In progress

Cross-wiki abuse. On city related pages. New York City is NOT New York. --Ilovemydoodle (talk) 05:11, 14 July 2022 (UTC)

Whislife (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser) looks like their sock to me, considering w:Special:Diff/1100194493 vs edits like w:Special:Diff/1098717197 from the IP range, as well as the template creations on Wikisource on both accounts. ~~~~
User:1234qwer1234qwer4 (talk) 17:41, 1 August 2022 (UTC)

Global block for LTA

Status:    In progress

Global Lock evasion and cross-wiki abuse by the LTA MRY. These IPs are also Open Proxies or VPNs. Please Globally Block for at least a year, and run a sleeper check. — The preceding unsigned comment was added by LightandDark2000 (talk) 17:10, 14 July 2022 (UTC)

At least the second one looks like Wikinger to me, though he might certainly be imitated. Can you provide evidence for the requested block duration? ~~~~
User:1234qwer1234qwer4 (talk) 17:18, 1 August 2022 (UTC)

Global block for 200.14.81.208

Status:    In progress

Cross-wiki abuse. and likely open proxies, but at least confirmed Xwiki abuse.

I can't think of another reason that a chilean IP-adress would suddenly start ban evading and editwarring in svwiki of all places other than if it's a Mikrotik Zombie. The whole /24 range also has a whole bunch of abuse reports on this website: abuse IPDB.
The range belongs to a VPS/webhost "infofractal.io" in Chile. --EstrellaSuecia (talk) 02:00, 15 July 2022 (UTC)

Global block/unblock for 2404:C0:7000:0:0:0:0:0/38

Status:    In progress

Cross-wiki abuse. Casmo spam. – Symphonium264 (talk) 11:09, 15 July 2022 (UTC)

Global block for 61.221.125.204

Status:    In progress

 It looks like a duck to meUser:Xayahrainie43.Confirmed according to edit in zhwp and enwp. --滑稽金苹果 (talk) 11:06, 16 July 2022 (UTC)

Global block for 8.29.105.0/24

Status:    In progress

Cloudflare VPN -- Ahmad Kanik 💬 11:33, 16 July 2022 (UTC)

Next global block for 2601:300:4201:2310:xxx

Status:    In progress

LTA RUMPTF is back. Cross-wiki abuse continues on wikis where there is no longer local block (3 months on sv.wikt and fi.wikt) Taylor 49 (talk) 20:33, 17 July 2022 (UTC)

Global block for long-term abuse

Status:    In progress

Extreme case of long-term abuse. Almost immediately after any of these long-term blocks expire, this individual targets any and all editors who may have reverted their vandalism in the past and edit-wars with them, with summaries that dox them, with examples including Ponyo, Ymblanter, Mtarch11 - and especially Gadfium. With how aggressive they have behaved toward Gadfium, I honestly would recommend that he contact his local New Zealand authorities. They also target it.Wikipedia & mi.Wikipedia. Ohnoitsjamie has done an exemplary job of addressing this individual on the English Wikipedia, but their conduct on multiple projects needs to be addressed. Just today, they took the opportunity to abuse some more. I request a global block of one-plus year. Botto (talk) 00:01, 18 July 2022 (UTC)

For clarification, this request is not stale. The vandal primarily targets the English Wikipedia and sequentially waits for one of the three blocks to be lifted, before almost immediately going to that part of Auckland and attacking their usual targets -- the next one is 122.56.192.0/20, which expires next Friday. In the meantime, they ocassionally target certain editors on other wikis, as Meta-Wiki contributors Mtarch11 and Daniuu may attest. Botto (talk) 17:38, 1 August 2022 (UTC)
Unfortunately, I can confirm the statement made by colleague Botto. Daniuu (talk) 18:19, 1 August 2022 (UTC)
Yeah I doubt this person will ever want to contribute to Wikipedia or any sister projects in a productive way.StarTrekker (talk) 21:30, 2 August 2022 (UTC)

Global block for 2405:201:6822:58C0:1F5:E2C6:5F81:B04

Status:    In progress

Cross-wiki abuse. Spam / spambot. --–FlyingAce✈hello 07:01, 20 July 2022 (UTC)

Noting that the full range is 2405:201:6822:5000::/52. –FlyingAce✈hello 16:35, 20 July 2022 (UTC)
Aforementioned range is still spamming. –FlyingAce✈hello 21:45, 5 August 2022 (UTC)

Global unblock for 197.210.53.3

Status:    In progress

I am requesting for an IP address unblock for 197.210.53.38. The reason stated for the block was "open proxy" — The preceding unsigned comment was added by Prithee P (talk) 20:22, 24 July 2022 (UTC)

Global block for 83.26.0.0/16

Status:    In progress

Long-term abuse. Wikinger; cf. Stalktoy. 83.26.155.102 currently already gblocked by Tegel. --~~~~
User:1234qwer1234qwer4 (talk) 15:32, 28 July 2022 (UTC)

Global block for 68.78.104.87

Status:    In progress

Cross-wiki vandalism. This IP changes URLs subtely to redirect to a mock website for whatever reasons. See here or here for examples. --Gyrostat (talk) 19:38, 29 July 2022 (UTC)

Global block for 176.59.32.0/19

Status:    In progress

Cross-wiki abuse on 10+ projects. --reNVoy (user talk) 11:17, 30 July 2022 (UTC)

Global block for 36.73.32.0/22

Status:    In progress

Cross-wiki abuse. Long-term abuser Casmo. – Symphonium264 (talk) 11:17, 31 July 2022 (UTC)

Global block for 149.126.236.73

Status:    In progress

Cross-wiki abuse. Spam / spambot. Triggering a lot of global abuse filters on various projects, see the relevant abuse logs (filter 162). --Daniuu (talk) 12:36, 4 August 2022 (UTC)

See also stalktoy, particularly of 149.126.232.0/21 xwiki-contribs • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye. ~~~~
User:1234qwer1234qwer4 (talk) 14:08, 6 August 2022 (UTC)

Global block/unblock for spammers

Status:    In progress

Suspected open proxy's, used for spamming purposes on eswikisource or mxwikimedia. --Daniuu (talk) 15:43, 4 August 2022 (UTC)

Global block for spambots

Status:    In progress

Spambots see here. Hoyanova (talk) 05:42, 8 August 2022 (UTC)

Global block for 103.249.77.0/24

Status:    In progress

Cross-wiki spam. –FlyingAce✈hello 07:26, 8 August 2022 (UTC)

Global block for 102.23.96.0/22

Status:    In progress

Cross-wiki abuse. Proxies used for vandalism. Rangeblocked on 4 wikis. ---- Jeff G. ツ (please ping or talk to me) 11:09, 8 August 2022 (UTC)

Global block for 2404:160:8115:7789::/64

Status:    In progress

Cross-wiki abuse. Proxy. ---- Jeff G. ツ (please ping or talk to me) 19:21, 10 August 2022 (UTC)

Requests for global (un)lock and (un)hiding

Symbol comment vote.svg Note that global blocking currently only applies to IPs, due to a technical limitation. If you wish to request a named account for global [un]locking, please request a global [un]lock here instead. Be sure to follow the instructions below:
  • Your request might be rejected if your request doesn't include the necessary information.
  • Warning! This page is publicly viewable. If the account name is grossly insulting or contains personal information please contact a steward privately in #wikimedia-stewardsconnect or email your request to the stewards VRT queue at stewards@wikimedia.org (direct wiki interface) but do not post it here. Thanks.
  • Warning! This is not the place to ask for locks based on your opinion that someone is disruptive. Global locks are used exclusively against vandalism and spam, not because of content disputes, not because you think that someone deserves to be globally blocked. In such cases, you should ask for local blocks at appropriate places.
  • If you are globally locked, you should appeal your lock to stewards(_AT_)wikimedia.org.

Please describe abusive activity of an account before reporting them here. Since stewards are often not active at projects the reported accounts are, things that seem obvious to you may not be equally obvious to the reviewing steward.

Instructions for making a request

Before requesting that a global account be (un)locked, please be sure that:

  1. You have evidence of cross-wiki disruption from the account(s).
  2. You can show that it is not feasible to use local-only blocks or other measures like page protection to combat the disruption.
  3. You have considered making the request in #wikimedia-stewardsconnect, especially for account names which will be hidden, or for urgent requests.
To make a request for an account to be locked or unlocked
Copy one of the codes below to the bottom of this section and explain why the account(s) should be locked/unlocked.
=== Global lock/unlock for Foo ===
{{status}} <!-- do not remove this template -->
* {{LockHide|username}}
* {{LockHide|username|hidename=1}} <!-- if you do not want the name to be visible on this page -->
*...
Reasons, etc. --~~~~

For many accounts: 

=== Global lock for spambots/vandals ===
{{status}} <!-- do not remove this template -->
{{MultiLock|username|username2|username3}}
{{MultiLock|username|username2|username3|hidename=1}} <!-- if you do not want the names to be visible on this page -->
*...
Reasons, etc, --~~~~

Global lock for Arrisontan and socks

Status:    In progress

Lock all:

See CU, these accounts make promotional edits to one subject at zhwiki, enwiki, wikidata, kowiki, and more. --0xDeadbeef (talk) 04:35, 27 July 2022 (UTC)

Global lock for User:Velimir Ivanovic' suckpuppets' farm

Status:    In progress

Lock all:

Lock all:

On & off wiki stalking, harassment, banned from the Wikimedia Serbia wiki live meetings due to violating the Safe Space Policy. --Vs6507 08:32, 30 July 2022 (UTC)

Support lock of the one remaining abusive username, but please see Steward requests/Global/2022-w01#Global lock for Kolega2357. ~~~~
User:1234qwer1234qwer4 (talk) 11:12, 30 July 2022 (UTC)
1234qwer1234qwer4. Yes. I have created a RfC Requests for comment/Global ban of a disruptive user too. Vs6507 11:41, 30 July 2022 (UTC)

Global lock for cross-wiki abuse and LTA sock

Status:    In progress

Same user of Special:CentralAuth/R1t5,also,please check sleepers and block IP/IP range(s) when account not stale. --MCC214#ex umbra in solem 10:06, 1 August 2022 (UTC)

Global lock for Jeantetteee

Status:    In progress

Long-term abuse. Block evasion of Samuelle Santiago (CA · xwiki · COIBot report). --–FlyingAce✈hello 06:15, 2 August 2022 (UTC)

Global lock for Fysrhkbffhjcfgh

Status:    In progress

Cross-wiki abuse. --Victor Trevor (talk) 08:26, 2 August 2022 (UTC)

Global lock for Freezetime

Status:    In progress

Cross-wiki spam. --Mtarch11 (talk) 12:14, 2 August 2022 (UTC)

+1 --Mtarch11 (talk) 06:25, 4 August 2022 (UTC)

Global lock for SheryOfficial

Status:    In progress

Long-term abuse. Cross-wiki abuse. Requesting a lock for the master due to the nature of cross-wiki abuse, and for a few socks as an added bonus here. --DarkMatterMan4500 (talk) (contribs) 17:53, 2 August 2022 (UTC)

Global block for חנריב

Status:    In progress

Clear vandalism across various wikis. -- Prokurator11 (talk) 21:11, 2 August 2022 (UTC)

Global lock for Мадина Омарова sock(s)

Status:    In progress

Sockpuppet(s) found in enwiki sockpuppet investigation, see w:en:Wikipedia:Sockpuppet investigations/Мадина Омарова. Jack Frost (talk) 21:27, 2 August 2022 (UTC)

CU-confirmed on Commons: Lock all:
Мадина Умарова (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser) ~~~~
User:1234qwer1234qwer4 (talk) 03:16, 4 August 2022 (UTC)

Global lock for Joe Banfield-6.0

Status:    In progress

Long-term abuse. Cross-wiki abuse. Sockpuppet of Mike Matthews17. --Johannnes89 (talk) 10:47, 3 August 2022 (UTC)

Global lock for Arunbal puthiyottil

Status:    In progress

Spam-only account. --EstrellaSuecia (talk) 14:13, 3 August 2022 (UTC)

Global lock for ThehelperP

Status:    In progress

Global lock for ShadyPanther07

Status:    In progress

crosswiki nonsense, NOTHERE. --Johannnes89 (talk) 07:29, 4 August 2022 (UTC)

Global lock for Jennsily

Status:    In progress

Cross-wiki vandalism/abuse + copyright violation KhanhCN Defender1st Minh (talk) 10:35, 4 August 2022 (UTC)

Global lock for Jennierbelli

Status:    In progress

Jennsily's sockpuppet KhanhCN Defender1st Minh (talk) 10:43, 4 August 2022 (UTC)

@AmandaNP: can you check this account? KhanhCN Defender1st Minh (talk) 10:43, 4 August 2022 (UTC)
We can't do checkusers on viwiki or commons as they have local checkusers. -- Amanda (she/her) 10:51, 4 August 2022 (UTC)

Global lock for Physo172 sock(s)

Status:    In progress

Sockpuppet(s) found in enwiki sockpuppet investigation, see w:en:Wikipedia:Sockpuppet investigations/Physo172. Dp210 is indeffed on enwiki and trwiki; Dt.022 was CU confirmed at enwiki SPI. The master has a history of cross-wiki hoaxing. See enwiki ANI threads: [11] and [12]. Spicy (talk) 07:07, 5 August 2022 (UTC)

Global lock for socks of Shah Mohi

Status:    In progress

Long-term abuse. Global lock evasion by Shah Mohi. License laundering. ---- Jeff G. ツ (please ping or talk to me) 13:02, 6 August 2022 (UTC)

Global lock for Lai Wen-hsiung

Status:    In progress

Cross-wiki long-term abuse: w:WP:LTA/NDC. blocked on enwiki, and has edit history on wikidata. --郊外生活Kogaiseikatsu (talk,contribs) 02:33, 7 August 2022 (UTC)

Global lock for Amicus0Plato

Status:    In progress

LTA: 1Goldberg2 (WMF-banned user). SummerKrut (talk) 15:53, 7 August 2022 (UTC)

Global lock for Md Mushfiqur Alif

Status:    In progress

Lock evasion: Mushfiqur Alif. --Njd-de (talk) 20:33, 8 August 2022 (UTC)

Global lock for TheresNooTime(ＷMF)

Status:    In progress

Long-term abuse. ja:LTA:SLIME. As you can see, some of the accounts involve impersonation. --Dragoniez (talk) 06:32, 9 August 2022 (UTC)

Global lock for Nagnath Munde

Status:    In progress

Long-term abuse. Cross-wiki abuse. Multiple account xwiki spamming/self promotion. --Tiven2240 (talk) 07:07, 9 August 2022 (UTC)

Global lock for Wizkizayo sock(s)

Status:    In progress

Sockpuppet(s) found in enwiki sockpuppet investigation, see w:en:Wikipedia:Sockpuppet investigations/Wizkizayo. Girth Summit (blether) 07:29, 9 August 2022 (UTC)

Global lock for potential Cynthis Chukie socks

Status:    In progress

Lock all:

Please also see en:Wikipedia:Sockpuppet investigations/Cynthis Chukie and en:Wikipedia:Sockpuppet investigations/Z4590 gever

en:Wikipedia:Sockpuppet investigations/Z4590 gever confirmed that J and Z are related. I believe that en:User:Cynthis Chukie is also related to J and Z because C created en:Draft:Amaka The Igbo Princess, got enwiki-blocked indefinitely (for unrelated reasons) on 1 March, and globally locked for spam on 6 March. The Z4590 gever account was created on 7 March, and promptly started editing the draft page. Please consider locking the Z4590 gever account, and the J account, since it is a confirmed sockpuppet. Thanks. --NotReallySoroka (talk) 10:17, 9 August 2022 (UTC)

Global lock for ArrestLand 77

Status:    In progress

Long-term abuse. Lock evasion: Cricket Fan 7, via this confession. --DarkMatterMan4500 (talk) (contribs) 12:29, 9 August 2022 (UTC)

Global lock for LucyAyoubFan sock(s)

Status:    In progress

Sockpuppet(s) found in enwiki sockpuppet investigation, see w:en:Wikipedia:Sockpuppet investigations/LucyAyoubFan. Bbb23 (talk) 14:44, 9 August 2022 (UTC)

Global lock for Curious boy km sock(s)

Status:    In progress

Sockpuppet(s) found in enwiki sockpuppet investigation, see w:en:Wikipedia:Sockpuppet investigations/Curious boy km. TheSandDoctor Talk 05:23, 10 August 2022 (UTC)

Global lock for the remaining few of the Wwikix socks of the batches locked earlier

Status:    In progress

Lock all:

The few still unlocked socks of the third batch of Wwikix. This list was compiled based on the file on nlwiki and the lists of socks on afwiki and enwiki. Hoyanova (talk) 07:55, 10 August 2022 (UTC)

Global lock for Taji003

Status:    In progress

crosswiki spam. --Johannnes89 (talk) 08:11, 10 August 2022 (UTC)

Global lock for 陪伴是最深情的告白

Status:    In progress

Long-term abuse. Cross-wiki abuse. --MCC214#ex umbra in solem 10:11, 10 August 2022 (UTC)

Global lock for Jack Grey1403

Status:    In progress

Cross-wiki abuse. Sockpuppet of Mike Matthews17. see [13][14]. --Johannnes89 (talk) 10:17, 10 August 2022 (UTC)

Added another sockpuppet --Johannnes89 (talk) 11:01, 10 August 2022 (UTC)
@Johannnes89: I added in one more. --DarkMatterMan4500 (talk) (contribs) 11:50, 10 August 2022 (UTC)

Global lock for MrSuave2022

Status:    In progress

Cross-wiki abuse. Confirmed socks on enwiki, currently active crosswiki with promo-spam. --EstrellaSuecia (talk) 11:30, 10 August 2022 (UTC)

Global lock for Dxoc1494

Status:    In progress

Two more socks of the MissAsean2022 sockfarm. See also above here and on enwiki. Hoyanova (talk) 12:59, 10 August 2022 (UTC)

Global lock for 影武者(Nipponese Dog Calvero)

Status:    In progress

Cross-wiki LTA, also please check sleepers.  It looks like a duck to me--Lanwi1(talk) 12:55, 10 August 2022 (UTC)

Global lock for LTA:SUMOSONG

Status:    In progress

Long-term abuse. w:ja:LTA:SUMOSONG or copycat. --しみはる君 (talk) 17:46, 10 August 2022 (UTC)

Global lock for Xoduce

Status:    In progress

Long-term abuse. Locked user's sockpuppet: User:Sidowpknbkhihj (w:ja:LTA:HEATHROW) . --しみはる君 (talk) 17:46, 10 August 2022 (UTC)

Global lock for Bnmsas

Status:    In progress

Long-term abuse. Locked user's sockpuppet: User:Nbckfkh (w:ja:LTA:KFKH) . --しみはる君 (talk) 17:46, 10 August 2022 (UTC)

Global lock for Masato Koizumi socks

Status:    In progress

Long-term abuse. Locked user's sockpuppets: User:Masato Koizumi (w:ja:LTA:KOIZUMI) . --しみはる君 (talk) 17:46, 10 August 2022 (UTC)

Global lock for YMWJMTD88

Status:    In progress

Long-term abuse. Locked user's sockpuppet: User:Syun respect for music (w:ja:LTA:SYUN) . --しみはる君 (talk) 17:46, 10 August 2022 (UTC)

Global lock for TYMIDMNMUSNG

Status:    In progress

Long-term abuse. Locked user's sockpuppet: User:名取の納豆 (w:ja:LTA:NATO) . --しみはる君 (talk) 17:46, 10 August 2022 (UTC)

Global lock for LMGsharu socks

Status:    In progress

Lock evation: User:LMGsharu. CU-confirmed on jawiki. --しみはる君 (talk) 17:46, 10 August 2022 (UTC)

Global lock for JSKCWJSKCW

Status:    Done

Long-term abuse. Cross-wiki abuse. Cyberpunk2077JohnnySilverhand. --Billytanghh (talk) 22:53, 10 August 2022 (UTC)

Robot clerk note: Yes check.svg Done by Hasley. MajavahBot (talk) 02:25, 11 August 2022 (UTC)

Global lock for Kurihya(⒲ⅯF)

Status:    In progress

Long-term abuse. Impersonating WMF staff. --Daraku K. (talk) 08:47, 11 August 2022 (UTC)

See also

Cooperation requests for: comments (local) (global) · translation

Retrieved from "https://meta.wikimedia.org/w/index.php?title=Steward_requests/Global&oldid=23655553"