Steward requests/Global

From Meta, a Wikimedia project coordination wiki
< Steward requests(Redirected from SRG)
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)[reply]

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

Global block for 2A0B:F4C1:2:0:0:0:0:247

Status:    In progress

Tor exit node. --CptViraj (talk) 09:58, 11 March 2022 (UTC)[reply]

Comment: I think this should be handled by TorBlock itself. —MarcoAurelio (talk) 18:17, 6 June 2022 (UTC)[reply]

Global block for 2A02:898:218:0:0:0:0:1

Status:    In progress

Tor exit node. --CptViraj (talk) 10:01, 11 March 2022 (UTC)[reply]

Global block for 2001:BC8:1200:D:208:A2FF:FE0C:8F72

Status:    In progress

Tor exit node. --CptViraj (talk) 10:09, 11 March 2022 (UTC)[reply]

Since we have TorBlock as an extension, I thought we just grab the TorProject data (ie. ExoneraTor claims it has been Tor Exit Node for more than 48 hours prior to this report) to dynamically block exit node? If it did not block, it sounds more like a possible bug report. — regards, Revi 20:14, 14 March 2022 (UTC)[reply]
It wasn't blocked at the time of my request, don't know about now. Is range block helpful as it has been done in my previous Tor IP block requests? -- CptViraj (talk) 09:03, 20 March 2022 (UTC)[reply]
I think I remember there being some issue with IPv6, though I can't find anything on Phabricator. ~~~~
User:1234qwer1234qwer4 (talk)
11:09, 20 March 2022 (UTC)[reply]
Indeed, there's been a few IPv6 Tor exits which have not been blocked by TorBlock and required manual blocks. MarioGom (talk) 17:22, 21 April 2022 (UTC)[reply]
|revi, I thought that at as well, but JavaHurricane corrected me, linking me to a relevant recent thread that explained the TorBlock extension has issues with IPv6 addresses. Dmehus (talk) 03:33, 25 April 2022 (UTC)[reply]

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)[reply]

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)[reply]
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)[reply]
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)[reply]
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)[reply]
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)[reply]
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)[reply]
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)[reply]

Global block for likely IP socks of 121.214.230.66

Status:    In progress

This is a mess. These IPs' contribs on Wikidata are very similar to that of 121.214.230.66, which AmandaNP blocked some time ago for "long-term abuse". There are also some other IPs and ranges without recent edits which were almost certainly also used by the same user:

Extended content

On IPv6, 2001:8000::/29:

On IPv4:

The two IPs I've requested blocks for are the ones with recent edits. Any other help finding more IPs or cleaning up after them would be appreciated. Tol (talk | contribs) @ 17:13, 22 April 2022 (UTC)[reply]

Global block for 2600:1700:3720:3770::/64

Status:    In progress

Long-term abuse. Cross-wiki abuse. --Titore (talk) 22:13, 5 May 2022 (UTC)[reply]

@Titore Can you be more specific? AntiCompositeNumber (talk) 03:26, 4 June 2022 (UTC)[reply]
@AntiCompositeNumber Hoaxes, disruptive editing. Already blocked on multiple projects. Titore (talk) 13:03, 4 June 2022 (UTC)[reply]

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)[reply]

Global block for LTA Xayahrainie43

Status:    In progress

Long term abuse: Xayahrainie43 / zh:LTA:x43. Most of edits were reverted.--SCP-2000 02:41, 14 May 2022 (UTC)[reply]

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)[reply]

Global block for Special:Contributions/1.43.0.0/16 and Special:Contributions/1.42.0.0/16

Status:    In progress

crosswiki abuse, long term abuse [6][7] --Johannnes89 (talk) 13:06, 17 May 2022 (UTC)[reply]

Global block for 120.188.0.0/17, 114.4.0.0/16 and 114.10.0.0/19

Status:    In progress

Persistent long-term abuse, cross-wiki abuse, block evasion and IP hopping. AdhiNG (talk) 20:11, 20 May 2022 (UTC)[reply]

Global block for 38.7.0.0/16

Status:    In progress

Crosswiki spam. Open proxies. See also c:COM:ANB#Spammer using multiple accounts. -- Jeff G. ツ (please ping or talk to me) 16:45, 23 May 2022 (UTC)[reply]

@Jeff G. Why do you think that the entire range is open proxy? I am not comfortable making a large range-block like this otherwise.--BRP ever 00:51, 13 June 2022 (UTC)[reply]
@BRPever: In addition to c:Commons:Administrators' noticeboard/Blocks and protections/Archive 32#Spammer using multiple accounts, please see all of the proxy blocks at https://meta.toolforge.org/stalktoy/38.7.0.0/16 in no less than 10 /24s and consider adding \bmensa(?:marketing|tech)\.com\.au\b to the global spam blacklist. -- Jeff G. ツ (please ping or talk to me) 10:45, 14 June 2022 (UTC)[reply]

Global block for 46.177.0.0/16

Status:    In progress

Xwiki disruption; see stalktoy. Blocked on cawikiquote, elwikinews, enwiki, and elwikitionary. IP from this range is currently disrupting enwiki. --Firestar464 (talk) 10:59, 26 May 2022 (UTC)[reply]

Global block for 49.228.0.0/18

Status:    In progress

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

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

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.[9][10][11] The user is already blocked up to 2028 at en.wiki[12], 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)[reply]

Global block for 80.246.28.0/24

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

Global block for 120.188.92.0/24

Status:    In progress

Long-term abuse. Cross-wiki abuse. Open proxy. --reNVoy (user talk) 13:46, 3 June 2022 (UTC)[reply]

Global block for 103.153.2.0/24

Status:    In progress

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

@Renvoy What makes you say this entire range is an open proxy? AntiCompositeNumber (talk) 01:54, 5 June 2022 (UTC)[reply]
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)[reply]

Global block for 180.243.0.0/20

Status:    In progress

Cross-wiki abuse. The vast majority of recent edits are vandalism. --NguoiDungKhongDinhDanh 15:33, 13 June 2022 (UTC)[reply]

Global block for 2401:4900:560B:D7F1:384A:74A6:1954:4E58

Status:    In progress

Long-term abuse. Cross-wiki abuse. w:en:Wikipedia:Sockpuppet_investigations/Wefffrrr/Archive#26_July_2021 Please block the suitable range. As they are active on mrwiki, wikidata, enwiki, hiwiki, commonswiki. From similar geo-locations and IP ranges. thanks. --QueerEcofeminist [they/them/their] 02:42, 15 June 2022 (UTC)[reply]

Global block for 195.35.231.192/26

Status:    In progress

LTA resumes activities after 3 month global block expired. See file here. --- Hoyanova (talk) 06:51, 15 June 2022 (UTC)[reply]

Global block for 2402:800:621F:C661:1DEC:31DF:32C:27EC/48

Status:    In progress

Long-term abuse. Cross-wiki abuse. Sister cities vandal. --NguoiDungKhongDinhDanh 12:19, 16 June 2022 (UTC)[reply]

Global block for 178.238.125.38

Status:    In progress

Cross-wiki abuse. Spam / spambot. See abuse log. --~~~~
User:1234qwer1234qwer4 (talk)
00:53, 19 June 2022 (UTC)[reply]

+5. ~~~~
User:1234qwer1234qwer4 (talk)
01:21, 19 June 2022 (UTC)[reply]

Global block for 178.33.0.0/16

Status:    In progress

Webhost, including spambot abuse. See https://meta.toolforge.org/stalktoy/178.33.0.0/16. --~~~~
User:1234qwer1234qwer4 (talk)
01:00, 19 June 2022 (UTC)[reply]

Global block for 37.143.131.210/24

Status:    In progress

Colocation host, including spambot abuse. See https://meta.toolforge.org/stalktoy/37.143.131.210/24. --~~~~
User:1234qwer1234qwer4 (talk)
01:07, 19 June 2022 (UTC)[reply]

Global block for 36.90.63.248

Status:    In progress

Open proxy/zombie

. --EstrellaSuecia (talk) 08:59, 19 June 2022 (UTC)[reply]

Global Lock Request Araxes TheThief and IPs associated

Status:    In progress

I posted in the lower section too as there are both IPs and usernames to be blocked.

I apologize for the length of the list, but this person/group has been an LTA for quite a while and evading their block on enWiki (as seen here) and on simple of which they are making the exact same changes as seen here in our group synopsis that got them banned on enWiki. This entire thing began in 2001 and has continued through to today. The changes are made almost every one minute and spans a variety of articles (also in our discussion on simple). We, as editors, would appreciate immediate action on this farm so that we can get the articles back in shape to the standards they should be in per MOS. Thank you for your attention to this. PDLTalk to me!OMG, What have I done? 23:14, 19 June 2022 (UTC)[reply]

Global block for 2603:8081:8108:6A00::/64

Status:    In progress

Long-term abuse. Cross-wiki abuse. Long-term subtle abuse. --Ilovemydoodle (talk) 23:50, 20 June 2022 (UTC)[reply]

As far as I can see, edits on projects other than enwikiquote date back to last year (simplewiki). Possibly should just be handled locally. ~~~~
User:1234qwer1234qwer4 (talk)
12:59, 27 June 2022 (UTC)[reply]

Global block for LTA

Status:    In progress
Long-term abuse. --Mtarch11 (talk) 11:46, 23 June 2022 (UTC)[reply]

Global block for 203.78.230.253

Status:    In progress

Cross-wiki abuse. Spam / spambot. --春春眠眠Syunsyunminmin 🗨️Talk 06:29, 24 June 2022 (UTC)[reply]

Global block for LTA Decker

Status:    In progress

Long-term abuse. Cross-wiki abuse. Proxy. IP-range used for vandalism at amiwiki and stwiki (see also the nuked edits over there from 194.68.44.89). --Daniuu (talk) 11:58, 24 June 2022 (UTC)[reply]

Global block for 120.188.66.241

Status:    In progress

Long-term abuse. --reNVoy (user talk) 08:09, 25 June 2022 (UTC)[reply]

@Renvoy I couldn't find any recent edits or filter hits. Am I missing something?--BRP ever 11:58, 27 June 2022 (UTC)[reply]
@BRPever ms:Khas:Log/120.188.66.241 there was spam activity on mswiki from this IP + range blocked on idwiki for the same reason. However good that you reminded me of this because almost month ago I already requested block of range of this IP #Global block for 120.188.92.0/24 which is still pending. If mentioned request is done, this particular one would be irrelevant. Thanks. reNVoy (user talk) 12:35, 27 June 2022 (UTC)[reply]

Global block for 2601:300:4201:2310:xxx

Status:    In progress

Cross-wiki abuse (EN, EO, SV, ...). Taylor 49 (talk) 11:57, 26 June 2022 (UTC)[reply]

Global block for 79.22.104.231

Status:    Done

Cross-wiki abuse. ---- Jeff G. ツ (please ping or talk to me) 11:19, 26 June 2022 (UTC)[reply]

Yes check.svg Done BRP ever 11:45, 27 June 2022 (UTC)[reply]
@BRPever: Thanks! -- Jeff G. ツ (please ping or talk to me) 15:44, 27 June 2022 (UTC)[reply]

Global block for 106.102.0.140/24

Status:    In progress

Cross-wiki abuse. See also Stalktoy. --SCP-2000 09:37, 27 June 2022 (UTC)[reply]

Global block for 1.46.140.30

Status:    In progress

Cross-wiki abuse. ---- Jeff G. ツ (please ping or talk to me) 11:46, 27 June 2022 (UTC)[reply]

Global block for 37.238.229.9

Status:    In progress

Cross-wiki abuse. ---- Jeff G. ツ (please ping or talk to me) 15:29, 27 June 2022 (UTC)[reply]

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 Pcgeekyy

Status:    In progress

A couple of SPAM edits/randsomware on minor Wikisource projects. I fear that it continues elsewhere. Thanks --Ruthven (msg) 13:38, 27 June 2022 (UTC)[reply]

Global unlock for Eaglestorm

Status:    In progress

There were incivility problems on both enwiki and enwikiquote, but these weren't cross-wiki vandalism, spam or sockpuppetry issues and therefore I don't think they are eligible for a global lock. --Ferien (talk) 15:29, 2 April 2022 (UTC)[reply]

Also pinging Tegel as the one who made the lock --Ferien (talk) 15:30, 2 April 2022 (UTC)[reply]
Only edits are on two wikis. I don't see how this couldn't have been handled locally if needed. ~~~~
User:1234qwer1234qwer4 (talk)
15:40, 1 June 2022 (UTC)[reply]
Is there a consensus that you want to have the user back at en.wikiquote? If there is then I would consider a re-evaluation of the global lock. -- Tegel (Talk) 21:39, 7 June 2022 (UTC)[reply]
Tegel, the user was only blocked on Wikiquote for two weeks and that block has now expired, so I would say yes. --Ferien (talk) 05:47, 8 June 2022 (UTC)[reply]
+1. IMO it's the global lock that effectively just extended the enwq block to be indefinite (and nothing else) without consensus. ~~~~
User:1234qwer1234qwer4 (talk)
14:27, 8 June 2022 (UTC)[reply]

Global lock for Gopisingh60

Status:    In progress

Cross-wiki abuse, promotion on English Wikipedia and Simple English Wikipedia. --Deppty (talk) 15:14, 3 May 2022 (UTC)[reply]

Global lock for socks

Status:    In progress

Валко socking again. SummerKrut (talk) 21:35, 3 May 2022 (UTC)[reply]

Global lock for Bilalahmed2022

Status:    In progress

Lock evasion. Similar behaviour as Thamesinfotech socks on English Wikipedia. Creating articles about Sheikh Asif on Kashmiri Wikipedia. --Hulged (talk) 15:48, 4 May 2022 (UTC)[reply]

Global lock for Papa2004's socks

Status:    In progress

Long-term abuse: Papa2004 / Mama1938. See w:ru:Википедия:Проверка участников/Ukraina12. SummerKrut (talk) 18:53, 4 May 2022 (UTC)[reply]

Global lock for Yellow Diamonds

Status:    In progress

Shared/compromised account. See this discussion on viwiki. --NguoiDungKhongDinhDanh 12:57, 5 May 2022 (UTC)[reply]

+ 1. NguoiDungKhongDinhDanh 18:38, 7 May 2022 (UTC)[reply]
Cf. viwiki RfCU. NguoiDungKhongDinhDanh 12:57, 26 May 2022 (UTC)[reply]

Global lock for どうせ

Status:    In progress

Cross-wiki long-term abuse: w:ja:LTA:SLIME. Vandalism-only account. Continuing vandalism on jawiki. --郊外生活Kogaiseikatsu (talk,contribs) 08:39, 8 May 2022 (UTC)[reply]

My CU results at login-wiki don't particularly indicate this to be SLIME. How sure are we this is SLIME? -- Amanda (she/her) 14:12, 8 May 2022 (UTC)[reply]
@AmandaNP: That is because this account did vandal edits at Tokyo-related articles on jawiki. I guess the editing trend matches what SLIME usually do, and a jawiki sysop added this account into SLIME sock list; w:ja:Special:Diff/89427416. But considering your CU report, this account may be copycat of SLIME by other LTA, or this account has been logged in by taking measure to CU such as using different IP or ISP. Even if this account is not SLIME, but this account has done vandal edits on jawikivoyage such as creating vandalism-only page that ridicules a jawiki sysop voy:ja:Special:Redirect/logid/13654, so this account can be thought to cross-wiki abuse account. --郊外生活Kogaiseikatsu (talk,contribs) 20:23, 8 May 2022 (UTC)[reply]

Global lock for zh:LTA:JIONG sock 10052022

Status:    In progress

globally banned user; zh:LTA:JIONG or copycat. This account has posted harassment message at w:ja:User talk:No1lovesu. That user talk page has been vandalised by this LTA and has semi-protection history. If possible, please also check other socks including sleepers. I have a doubt that Special:CentralAuth/Oppo-tei and Special:CentralAuth/Chirosithone are also socks. Please see the page history of w:ja:User talk:五月念珠. --郊外生活Kogaiseikatsu (talk,contribs) 17:52, 10 May 2022 (UTC)[reply]

:@郊外生活 , could you withdraw this? Checkuser information showed that these users are not LTA:JIONG. PAVLOV 14:37, 25 May 2022 (UTC)[reply]

Support Support Also abusing multiple accounts on Chinese Wikipedia.--PAVLOV 00:48, 26 May 2022 (UTC)[reply]

Global lock for Krishnamurthy GovindaReddy

Status:    In progress

Cross-wiki abuse. Clearly not constructive. This user has been indeffed on 2 wikis and temporarily blocked on 2 more. They were also blocked on ta.wikipedia for 3 days. --Prahlad balaji.test (talk) 02:51, 13 May 2022 (UTC)[reply]

Global lock for

Status:    In progress

Cross-wiki abuse. crosswiki hoax

. --𝐖𝐢𝐤𝐢𝐁𝐚𝐲𝐞𝐫 👤💬 12:51, 13 May 2022 (UTC)[reply]

Global lock for EggplantGuy

Status:    In progress

Lock evasion: Kent2121 (i.e. LevelUser51). Both tried to edit User:Tigerzeng userpage [13]. Were blocked in zhwiki. --SCP-2000 05:35, 14 May 2022 (UTC)[reply]

+ KUser14. Was blocked in zhwiki. Please block their using IP address/range and check sleepers if possible. --SCP-2000 08:24, 15 May 2022 (UTC)[reply]

Global lock for Martorellpedro

Status:    In progress

Cross-wiki abuse. Machine translation. --𝐖𝐢𝐤𝐢𝐁𝐚𝐲𝐞𝐫 👤💬 18:33, 15 May 2022 (UTC)[reply]

Please don't block me, Because I like to work articles about cartoons. --Martorellpedro (talk) 19:07, 15 May 2022 (UTC)[reply]
@WikiBayer i don't know about other wikis, but their contributions on ckb wikipedia are good and understandable, therefore as a Sysop on ckb wiki; i don't see any reason to be blocked on ckb. 🌸 Sakura emad 💖 (talk) 19:20, 15 May 2022 (UTC)[reply]
@Sakura emad This user is an LTA that I have noticed for months. The user creates masses of machine translations with IPs and with these (possibly other) accounts. 𝐖𝐢𝐤𝐢𝐁𝐚𝐲𝐞𝐫 👤💬 19:24, 15 May 2022 (UTC)[reply]
@WikiBayer: as i said i don't know about their activity on other wikis, but as i am patrolling ckb; i can understand their contributions very well. 🌸 Sakura emad 💖 (talk) 19:28, 15 May 2022 (UTC)[reply]
Support. I came here to propose the same thing. It's highly unlikely that one user creates articles in languages as diverse as Ewe, Zulu, and Kurdish, all of which happen to be supported by Google Translate, and that these articles would actually be good.
It would also be nice to clean up the machine-translated articles they created in many languages. Is there a convenient, efficient way to run something like "nuke" in multiple wikis? Amir E. Aharoni (talk) 07:33, 16 May 2022 (UTC)[reply]
I reported a similar case before and the result was "turn to global ban". But this one is confirmed of cross-wiki abuse, so I will support to global lock this one. PAVLOV 09:31, 16 May 2022 (UTC)[reply]
Just like ผู้ใช้:บุญพฤทธิ์ ทวนทัย He is make wikipedia too, But Most of them he create pages about Thai morlam/lukthung singer, Foreign Monarchist and Leader president (in Thwiki, enwiki, and other wikipedia language) etc.--Martorellpedro (talk) 10:17, 16 May 2022 (UTC)[reply]
@WikiBayer Also see this page วิกิพีเดีย:สภากาแฟ/อภิปราย/อภิปรายเรื่องผู้ใช้:Martorellpedro (thwiki) Martorellpedro (talk) 14:33, 21 May 2022 (UTC)[reply]
Added another sock now. Very similar behavior: lots of languages, articles about animation and toilet topics. --Amir E. Aharoni (talk) 18:36, 29 May 2022 (UTC)[reply]
I removed the account now because this account is used by someone else. --Martorellpedro (talk) 04:06, 24 June 2022 (UTC)[reply]
Better remember that I'm not Henry408's sock. --Martorellpedro (talk) 11:10, 25 June 2022 (UTC)[reply]

Global lock for LTA Lyrixio and socks

Status:    In progress

LTA - cross wiki vandalism (copyvio uploads on commons, unwanted edits, removing traces of wrong doing by blanking talk pages) - see file here. -- Hoyanova (talk) 07:37, 19 May 2022 (UTC)[reply]

Global lock for Cedreon/Ekrex's socks

Status:    In progress
User list

Cross-wiki abuse. Spam / spambot. Confirmed socks of Ekrex/Cedreon.

Global lock for User:BitaKarate1

Status:    In progress

Cross-wiki abuse, is copy/pasting machine-translated bullshit in article about topics such as medicine or islam without understanding what he's doing. Trying to discuss this with him on German Wikipedia were futile. He is already blocked in bn:wp, I just blocked him on de:wp and requested from our French collegues to do so because he's doing the same shit there as well, cf. VM at de:wp, at fr:wp. --Gardini (talk) 13:20, 21 May 2022 (UTC)[reply]

Global lock for FaridK12

Status:    In progress

Copyright violations at multiple wikis, see also en:Wikipedia:Administrators'_noticeboard/Incidents#FaridK12_and_copyright. They have already been blocked at enwiki, and 16 of their articles at azwiki have also been deleted. At Commons, 2 uploads have already been deleted. --LaundryPizza03 (talk) 01:32, 22 May 2022 (UTC)[reply]

Comment Comment Additionally, all remaining contributions at azwiki should be inspected for copyright violations, and revdel'd or deleted as appropriate. All copyvios at enwiki have been removed, and all files uploaded at Commons have been deleted or are nominated for deletion. LaundryPizza03 (talk) 02:32, 22 May 2022 (UTC)[reply]

Global lock for ZVRussianVZ

Status:    In progress

Abusive username. --𝐖𝐢𝐤𝐢𝐁𝐚𝐲𝐞𝐫 👤💬 06:36, 22 May 2022 (UTC)[reply]

  • i think it is not abusive. it is just supporting russia? it is just doing propaganda. do we ban "slava ukraine" nicknames? if we do, then this should be banned too. Modern primat (talk) 11:06, 26 May 2022 (UTC)[reply]
  • Support Support. This is not supporting, but direct propaganda of terrorism. At this rate swastika accounts will register, and call it support. --Mykola talk 11:13, 26 May 2022 (UTC)[reply]
    @Modern primat These symbols are not compatible with the Terms of Use or our Policies. 𝐖𝐢𝐤𝐢𝐁𝐚𝐲𝐞𝐫 👤💬 12:59, 26 May 2022 (UTC)[reply]

Global lock for WKP (Music)

Status:    In progress

Cross-wiki abuse. Also lock evasion of several accounts listed at c:Category:Sockpuppets of Alex9777. --~~~~
User:1234qwer1234qwer4 (talk)
15:34, 22 May 2022 (UTC)[reply]

Global lock for Texas10152

Status:    In progress

Cross-wiki abuse. Probable sockpuppetry and lock evasion by Tevez55. ---- Jeff G. ツ (please ping or talk to me) 11:01, 24 May 2022 (UTC)[reply]

Global lock for T308397

Status:    In progress

Long-term abuse. user:Cyberpunk2077JohnnySilverhand per edits on Chinese Wikipedia. --PAVLOV 19:20, 25 May 2022 (UTC)[reply]

Global lock for Shifu 8964

Status:    In progress

Global lock evasion. Edit summaries are exactly the same as that of globally-locked user Shih Ming-teh. The dog2 (talk) 16:40, 27 May 2022 (UTC)[reply]

Per en:Wikipedia:Sockpuppet_investigations/Nipponese_Dog_Calvero/Archive#27_May_2022. PAVLOV 15:10, 28 May 2022 (UTC)[reply]

Global lock for Lherhofer

Status:    In progress

Cross-wiki abuse. Promotion. Hoaxing. Sockpuppetry. ---- Jeff G. ツ (please ping or talk to me) 10:36, 31 May 2022 (UTC)[reply]

Global lock for User:Rajesh56om and sockpuppets

Status:    In progress

Lock all:

These accounts are actively spamming promotional articles and drafts of "Rajesh Kumar Ram" a non-notable Indian musician with the stagename of "Devilraj" across multiple Wikis. These have included the English Wikipedia, Simple English Wikipedia, French Wikipedia, Korean Wikipedia, and Hindi Wikipedia. The accounts have also added likely copyvios to Wikimedia Commons.

Checkuser results are available in a EnWiki sockpuppet investigation.

--Mhawk10 (talk) 20:12, 31 May 2022 (UTC)[reply]

It's been three weeks since I first made the request, and many of these accounts are blocked on multiple Wikis. This is a clear case of long-term cross-wiki sockpuppetry. Mhawk10 (talk) 02:16, 23 June 2022 (UTC)[reply]

Global lock for Ydvraushan

Status:    In progress

Cross-wiki abuse. ---- Jeff G. ツ (please ping or talk to me) 18:25, 4 June 2022 (UTC)[reply]

Global lock for 包子暴君 送菜刀

Status:    In progress

Abusive username. Lock evasion of user:包子吃屎 送菜刀. --PAVLOV 19:13, 9 June 2022 (UTC)[reply]

Global lock for KatiMedi

Status:    Not done

LTA - copyvio uploads and cross wiki computer translation placements. See checkuser on en-wiki --- Hoyanova (talk) 17:14, 10 June 2022 (UTC)[reply]

Declining as there has been no enwiki SPI case indicating that they are identified as socks; and there has been no locks on any of the accounts listed.
If you want to lock these, get these 3 accounts vetted at SPI, and come back with list of cross-wikiness and all socks past and present. — regards, Revi 17:29, 26 June 2022 (UTC)[reply]

Global lock for 陳亞倫's socks group

Status:    In progress

Cross-wiki abuse. Cross-wiki abuse, main account indef on two projects for vandalism. Threatening to use a cluster of puppets to attack . --PAVLOV 03:24, 15 June 2022 (UTC)[reply]

@Mys 721tx courtesy ping blocking sysop. PAVLOV 03:35, 15 June 2022 (UTC)[reply]

Global block for KOALİSYONİZM

Status:    In progress

KOALİSYONİZM (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser)

Fatma ceylan sockpuppet. Long-term abuse. LisafBia6531 (talk) 13:35, 15 June 2022 (UTC)[reply]

Moving to global locks section. ~~~~
User:1234qwer1234qwer4 (talk)
14:23, 15 June 2022 (UTC)
[reply]

Global block for 杨锦桐

Status:    In progress
  • 由于中文维基百科纯粹破坏。
Spam / spambot. Spam bot on wikiquote. --Se 4142 15:08, 15 June 2022 (UTC)[reply]
@Se 4142 It doesn't seem as though they have edited any wikiquote. Can someone clarify this request?--BRP ever 04:37, 16 June 2022 (UTC)[reply]
No need to lock these accounts: they have no edits at all on Wikiquote, and have been blocked solely on zhwiki. What’s more, the account who filed the request itself has been glocked. U.T. 07:55, 23 June 2022 (UTC)[reply]

Global lock for Fatma ceylan's socks

Status:    Done
User list

Long-term abuse. Cross-wiki abuse. Abusive username. Spam / spambot. https://tr.wikipedia.org/wiki/Kategori:Vikipedi:Fatma_ceylan_kullan%C4%B1c%C4%B1s%C4%B1n%C4%B1n_kuklalar%C4%B1

Harassive usernames created by Fatma ceylan. Targets Arabs, Islam and Ataturk. --Kadı Message 15:41, 15 June 2022 (UTC)[reply]
One locked, rest also hidden. ~~~~
User:1234qwer1234qwer4 (talk)
13:03, 27 June 2022 (UTC)[reply]

Global lock for JavadNazari et al

Status:    In progress

Crosswiki spam. Sockpuppetry. See also c:Category:Sockpuppets of JavadNazari. ---- Jeff G. ツ (please ping or talk to me) 08:33, 16 June 2022 (UTC)[reply]

Global lock for HideoTakashi

Status:    In progress

Cross-wiki abuse. --Eta Carinae (talk) 14:58, 17 June 2022 (UTC)[reply]

Global lock for Awesds

Status:    In progress

Long-term abuse. Heymid. --EstrellaSuecia (talk) 10:22, 18 June 2022 (UTC)[reply]

Global lock for Isechika socks

Status:    In progress

Long-term abuse. Abusive username. --Aeschylus (talk) 04:36, 19 June 2022 (UTC)[reply]

Global lock for Isechika wave 3

Status:    In progress

Long-term abuse. --Aeschylus (talk) 04:51, 19 June 2022 (UTC)[reply]

Global lock for ja:LTA/ISECHIKA socks

Status:    In progress
User list

Long-term abuse. Abusive username. --Aeschylus (talk) 12:28, 19 June 2022 (UTC)[reply]

Global lock

Status:    In progress

Abusive username. --NguoiDungKhongDinhDanh 12:39, 19 June 2022 (UTC)[reply]

Global lock for İşüçöğı

Status:    In progress

Cross-wiki abuse. Sock of User:İsmail Kendir. --Kadı Message 12:58, 19 June 2022 (UTC)[reply]

Global Lock Request Araxes TheThief and IPs associated

Status:    In progress

I apologize for the length of the list, but this person/group has been an LTA for quite a while and evading their block on enWiki (as seen here) and on simple of which they are making the exact same changes as seen here in our group synopsis that got them banned on enWiki. This entire thing began in 2001 and has continued through to today. The changes are made almost every one minute and spans a variety of articles (also in our discussion on simple). We, as editors, would appreciate immediate action on this farm so that we can get the articles back in shape to the standards they should be in per MOS. Thank you for your attention to this. PDLTalk to me!OMG, What have I done? 18:40, 19 June 2022 (UTC)[reply]

@PotsdamLamb I think this one can be handled locally. Please make a cleaner list of the accounts/IPs that have been affecting the wikis and report it to AN. An CU/admin should be able to assist you better there.--BRP ever 11:22, 27 June 2022 (UTC)[reply]
@BRPeverThanks for the information. You can mark this as not done and the one below as well. They do not appear to have edited since I reported them here. Thanks for everything you do. PDLTalk to me!OMG, What have I done? 17:29, 27 June 2022 (UTC)[reply]

Global lock for 1919901

Status:    In progress

Account compromised by a LTA. --Mys_721tx (talk) 01:50, 22 June 2022 (UTC)[reply]

Global lock for Panma50

Status:    In progress

Sockpuppet of User:Phạm Văn Rạng who is also globally locked. Sir Sputnik (talk) 02:34, 22 June 2022 (UTC)[reply]

Global lock for User:Nildo ouriques's puppets

Status:    In progress

LTA; started vandalizing other projects. Edmond Dantès d'un message? 05:16, 22 June 2022 (UTC)[reply]

Global lock for User:Quintinense's puppets

Status:    In progress

Puppets confirmed. Edmond Dantès d'un message? 05:45, 22 June 2022 (UTC)[reply]

Confirmed where? — regards, Revi 17:24, 26 June 2022 (UTC)[reply]

Global lock for 我目送 他们行色匆匆

Status:    In progress

Long-term abuse. 黄冰楠. -- Willy1018 (talk) 01:29, 23 June 2022 (UTC)[reply]

Global lock

Status:    Done

Abusive username. --SHB2000 (talk | contribs) 12:59, 26 June 2022 (UTC)[reply]

Has been hidden. ~~~~
User:1234qwer1234qwer4 (talk)
13:05, 26 June 2022 (UTC)[reply]

Global lock

Status:    Done

Cross-wiki abuse. --NguoiDungKhongDinhDanh 14:33, 26 June 2022 (UTC)[reply]

Robot clerk note: Yes check.svg Done by AntiCompositeNumber. MajavahBot (talk) 16:05, 26 June 2022 (UTC)[reply]

Global lock

Status:    Done

LTA, abusive username, harassment. --Ruy (talk) 15:32, 26 June 2022 (UTC)[reply]

Black check.svg Already done 8 minutes ago. Sgd. —Hasley 15:36, 26 June 2022 (UTC)[reply]

Global lock for 渡名喜文仁

Status:    In progress

Cross-wiki long-term abuse: w:WP:LTA/NDC. appeared on jawiki and wikidata. The username contains 文仁 (w:Fumihito, Crown Prince of Japan); the name of Japanese imperial family member. In wikidata, this account added sitelink to Vietnamese Wikipedia article. --郊外生活Kogaiseikatsu (talk,contribs) 16:53, 26 June 2022 (UTC)[reply]

Global lock for Phạm Minh Huyền

Status:    In progress

Spammer - KhanhCN Defender1st Minh (talk) 10:40, 27 June 2022 (UTC)[reply]

@KhanhCN Defender1st Minh they are already blocked on viwiki which seems to be the only wiki they edited. Is there a need for a global lock?--BRP ever 10:52, 27 June 2022 (UTC)[reply]

Global lock for Ẩn danh 1024 and Ẩn danh 2012

User list

Sockpuppet/trash account. KhanhCN Defender1st Minh (talk) 10:46, 27 June 2022 (UTC)[reply]

@KhanhCN Defender1st Minh Why should they be globally locked? BRP ever 10:53, 27 June 2022 (UTC)[reply]
@BRPever: Sockpuppet KhanhCN Defender1st Minh (talk) 13:21, 27 June 2022 (UTC)[reply]
of whom? ~~~~
User:1234qwer1234qwer4 (talk)
13:52, 27 June 2022 (UTC)[reply]

Global lock for Fnaf sister location fox splits location circus fox

Status:    In progress

Long-term abuse. Igoryu1993. --~~~~
User:1234qwer1234qwer4 (talk)
11:42, 27 June 2022 (UTC)[reply]

Global lock for LTA

Status:    In progress

Long-term abuse. Abusive username. Avoided. --~~~~
User:1234qwer1234qwer4 (talk)
11:49, 27 June 2022 (UTC)[reply]

Global lock for Madoithoinay and Madoithoinay socks

Status:    In progress
User list

Self advertising + offensive username KhanhCN Defender1st Minh (talk) 13:38, 27 June 2022 (UTC)[reply]

I don't see anything offensive nor any signs of sockpuppetry. NguoiDungKhongDinhDanh 13:41, 27 June 2022 (UTC)[reply]

Global lock for Muabannhadatcafeland

Status:    In progress

Cross-wiki abuse. Spam / spambot. --Rubbish computer (Ping me or leave a message on my talk page) 13:45, 27 June 2022 (UTC)[reply]

Global lock for ClayLarios39

Status:    In progress
User list

Spam / spambot. ntsamr. --~~~~
User:1234qwer1234qwer4 (talk)
14:47, 27 June 2022 (UTC)[reply]

Global lock for SafFahim

Status:    In progress

Crosswiki spam. ---- Jeff G. ツ (please ping or talk to me) 15:04, 27 June 2022 (UTC)[reply]

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) 15:03, 27 June 2022 (UTC)[reply]

Global lock for YHHMercedes

Status:    In progress
User list

Baccarat spambot (see spam blacklist log). --~~~~
User:1234qwer1234qwer4 (talk)
15:05, 27 June 2022 (UTC)[reply]

Global lock for Nadeth007

Status:    In progress

Abusing multiple accounts: Phnom Penh Skyline. ----Minorax