meta.m.wikimedia.org
Steward requests/Global
< Steward requests
Due to persistent vandalism and disruption on this page, this page is currently semi-protected indefinitely. Globally blocked or locked users should appeal to stewards
wikimediaorg or UTRS.
If your account was locked with a reason "Compromised account", please contact ca
wikimediaorg.
← Requests and proposalsSteward 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
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
wikimediaorg
Global unblock for 185.89.36.0/22
Status:   On hold
185.89.36.0/22 xwiki-contribs • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • ipchecker
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 block for 2A0B:F4C1:2:0:0:0:0:247
Status:   In progress
2A0B:F4C1:2:0:0:0:0:247 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • ipchecker
Tor exit node. --CptViraj (talk) 09:58, 11 March 2022 (UTC)
Comment: I think this should be handled by TorBlock itself. —MarcoAurelio (talk) 18:17, 6 June 2022 (UTC)
Global block for 2A02:898:218:0:0:0:0:1
Status:   In progress
2A02:898:218:0:0:0:0:1 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • ipchecker
Tor exit node. --CptViraj (talk) 10:01, 11 March 2022 (UTC)
Global block for 2001:BC8:1200:D:208:A2FF:FE0C:8F72
Status:   In progress
2001:BC8:1200:D:208:A2FF:FE0C:8F72 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • ipchecker
Tor exit node. --CptViraj (talk) 10:09, 11 March 2022 (UTC)
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)
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)
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)
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)
|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)
Global unblock for 2001:470::/32
Status:   In progress
2001:470::/32 xwiki-contribs • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • ipchecker
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 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 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 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 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)
Global block for 2600:1700:3720:3770::/64
Status:   In progress
2600:1700:3720:3770::/64 xwiki-contribs • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • ipchecker
Long-term abuse. Cross-wiki abuse. --Titore (talk) 22:13, 5 May 2022 (UTC)
@Titore Can you be more specific? AntiCompositeNumber (talk) 03:26, 4 June 2022 (UTC)
@​AntiCompositeNumber Hoaxes, disruptive editing. Already blocked on multiple projects. Titore (talk) 13:03, 4 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 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)
+ 110.29.114.0/24. --SCP-2000 14:18, 17 May 2022 (UTC)
Global unblock for 147.161.237.87
Status:   In progress
147.161.237.87 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • ipchecker
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)
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)
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)
Global block for 38.7.0.0/16
Status:   In progress
38.7.0.0/16 xwiki-contribs • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • ipchecker
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)
@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)
@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)
Global block for 46.177.0.0/16
Status:   In progress
IP address xwiki-contribs • xwiki-date (address alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • address ipchecker
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)
Global block for 49.228.0.0/18
Status:   In progress
49.228.0.0/18 xwiki-contribs • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • ipchecker
Spammy range, see [8]. ----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
37.128.219.241 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • ipchecker
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)
Associated IPs: 83.92.89.109 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • ipchecker and 192.38.132.230 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • ipchecker. Tbhotch (talk) 17:45, 8 June 2022 (UTC)
Global block for 80.246.28.0/24
80.246.28.0/24 xwiki-contribs • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • ipchecker
Crosswiki abuse and VPN/Open Proxy. --Codc (talk) 23:56, 2 June 2022 (UTC)
Global block for 120.188.92.0/24
Status:   In progress
120.188.92.0/24 xwiki-contribs • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • ipchecker
Long-term abuse. Cross-wiki abuse. Open proxy. --reNVoy (user talk) 13:46, 3 June 2022 (UTC)
Global block for 103.153.2.0/24
Status:   In progress
103.153.2.0/24 xwiki-contribs • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • ipchecker
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 180.243.0.0/20
Status:   In progress
180.243.0.0/20 xwiki-contribs • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • ipchecker
Cross-wiki abuse. The vast majority of recent edits are vandalism. --​NguoiDungKhongDinhDanh 15:33, 13 June 2022 (UTC)
Global block for 2401:4900:560B:D7F1:384A:74A6:1954:4E58
Status:   In progress
2401:4900:560B:D7F1:384A:74A6:1954:4E58​xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • ipchecker
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)
Global block for 195.35.231.192/26
Status:   In progress
195.35.231.192/26 xwiki-contribs • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • ipchecker
LTA resumes activities after 3 month global block expired. See file here. --- Hoyanova (talk) 06:51, 15 June 2022 (UTC)
Global block for 2402:800:621F:C661:1DEC:31DF:32C:27EC/48
Status:   In progress
2402:800:621F:C661:1DEC:31DF:32C:27EC/48 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • ipchecker
Long-term abuse. Cross-wiki abuse. Sister cities vandal. --​NguoiDungKhongDinhDanh 12:19, 16 June 2022 (UTC)
Global block for 178.33.0.0/16
Status:   In progress
178.33.0.0/16 xwiki-contribs • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • ipchecker
Webhost, including spambot abuse. See https://meta.toolforge.org/stalktoy/178.33.0.0/16​. --~~~~
User:1234qwer1234qwer4 (talk) 01:00, 19 June 2022 (UTC)
Global block for LTA
Status:   In progress
Long-term abuse. --Mtarch11 (talk) 11:46, 23 June 2022 (UTC)
Global block for 203.78.230.253
Status:   In progress
203.78.230.0/24 xwiki-contribs • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • ipchecker
Cross-wiki abuse. Spam / spambot. --春春眠眠
Syunsyunminmin
🗨️Talk 06:29, 24 June 2022 (UTC)
Global block for 120.188.66.241
Status:   In progress
120.188.66.241 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • ipchecker
Long-term abuse. --reNVoy (user talk) 08:09, 25 June 2022 (UTC)
@Renvoy I couldn't find any recent edits or filter hits. Am I missing something?--BRP ever 11:58, 27 June 2022 (UTC)
@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)
@Renvoy How about blocking the range on both of those wikis? Considering the affected wikis, and the origin of ip, that might be much better preventive measure in this case.--BRP ever 07:33, 28 June 2022 (UTC)
maybe @CyberTroopers and Ricky250: could help with this reNVoy (user talk) 08:55, 28 June 2022 (UTC)
@Renvoy: Thanks for the ping. I've done blocking this user on mswiki. Has been spamming using varies open IP to create this "Marsuki" page. CyberTroopers (talk) 10:25, 28 June 2022 (UTC)
@CyberTroopers hmm, I do not see the block. Can you perform block of this range 120.188.92.0/24? reNVoy (user talk) 11:09, 28 June 2022 (UTC)
@Renvoy: Done. CyberTroopers (talk) 04:59, 29 June 2022 (UTC)
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)
Global block for 106.102.0.140/24
Status:   In progress
106.102.0.140/24 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • ipchecker
Cross-wiki abuse. See also Stalktoy. --SCP-2000 09:37, 27 June 2022 (UTC)
Global block for 62.11.3.128
Status:   In progress
62.11.3.128 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • ipchecker
Long-term abuse. --𝐖𝐢𝐤𝐢𝐁𝐚𝐲𝐞𝐫 👤💬 17:19, 28 June 2022 (UTC)
Global block for 109.195.51.233
Status:   In progress
109.195.51.233 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • ipchecker
Cross-wiki abuse. Spam / spambot. See plwikibooks and eswikiversity. --~~~~
User:1234qwer1234qwer4 (talk) 20:27, 28 June 2022 (UTC)
Global block for 119.152.123.35
Status:   In progress
119.152.123.35 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • ipchecker
Spam / spambot. --EstrellaSuecia (talk) 21:26, 28 June 2022 (UTC)
Global block for 2604:3D08:6286:7500:6D9B:24EC:9D29:F83B/64
Status:   In progress
2604:3D08:6286:7500:6D9B:24EC:9D29:F83B/64 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • ipchecker
Cross-wiki abuse. --​NguoiDungKhongDinhDanh 22:51, 28 June 2022 (UTC)
Requests for global (un)lock and (un)hiding
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-stewards​connect or email your request to the stewards VRT queue at stewards
    wikimediaorg (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
    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-stewards​connect​, 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 unlock for Eaglestorm
Status:   In progress
Eaglestorm (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser)
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)
Also pinging Tegel as the one who made the lock --Ferien (talk) 15:30, 2 April 2022 (UTC)
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)
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)
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)
+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)
Global lock for socks
Status:   In progress
Валко socking again. SummerKrut (talk) 21:35, 3 May 2022 (UTC)
Global lock for Bilalahmed2022
Status:   In progress
Bilalahmed2022 (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser)
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)
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)
Global lock for Yellow Diamonds
Status:   In progress
Shared/compromised account. See this discussion on viwiki. --​NguoiDungKhongDinhDanh 12:57, 5 May 2022 (UTC)
+ 1. NguoiDungKhongDinhDanh 18:38, 7 May 2022 (UTC)
Cf. viwiki RfCU. NguoiDungKhongDinhDanh 12:57, 26 May 2022 (UTC)
Global lock for どうせ
Status:   In progress
どうせ (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser)
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)
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)
@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)
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)
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 FaridK12
Status:   In progress
FaridK12 (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser)
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)
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)
Global lock for Texas10152
Status:   Done
Texas10152 (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser)
Cross-wiki abuse. Probable sockpuppetry and lock evasion by Tevez55. ---- Jeff G. ツ (please ping or talk to me) 11:01, 24 May 2022 (UTC)
Done. [24Cr][talk] 18:37, 28 June 2022 (UTC)
@24Cr: Thanks! -- Jeff G. ツ (please ping or talk to me) 03:34, 29 June 2022 (UTC)
Global lock for T308397
Status:   In progress
T308397 (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser)
Long-term abuse. user:Cyberpunk2077JohnnySilverhand per edits on Chinese Wikipedia. --PAVLOV 19:20, 25 May 2022 (UTC)
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)
Per en:Wikipedia:Sockpuppet_investigations/Nipponese_Dog_Calvero/Archive#27_May_2022​. PAVLOV 15:10, 28 May 2022 (UTC)
Global lock for Lherhofer
Status:   Done
Lherhofer (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser)
Cross-wiki abuse. Promotion. Hoaxing. Sockpuppetry. ---- Jeff G. ツ (please ping or talk to me) 10:36, 31 May 2022 (UTC)
Done. [24Cr][talk] 18:43, 28 June 2022 (UTC)
@24Cr: Thanks! -- Jeff G. ツ (please ping or talk to me) 03:35, 29 June 2022 (UTC)
Global lock for Ydvraushan
Status:   In progress
Ydvraushan (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser)
Cross-wiki abuse. ---- Jeff G. ツ (please ping or talk to me) 18:25, 4 June 2022 (UTC)
Global lock for 包子暴君 送菜刀
Status:   In progress
包子暴君 送菜刀 (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser)
Abusive username. Lock evasion of user:包子吃屎 送菜刀. --PAVLOV 19:13, 9 June 2022 (UTC)
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)
@Mys 721tx courtesy ping blocking sysop. PAVLOV 03:35, 15 June 2022 (UTC)
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)
Moving to global locks section. ~~~~
User:1234qwer1234qwer4 (talk) 14:23, 15 June 2022 (UTC)
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)
Global lock for Isechika socks
Status:   In progress
Long-term abuse. Abusive username. --Aeschylus (talk) 04:36, 19 June 2022 (UTC)
Global lock for Isechika wave 3
Status:   In progress
Long-term abuse. --Aeschylus (talk) 04:51, 19 June 2022 (UTC)
Global lock
Status:   In progress
name hidden (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser)
Abusive username. --​NguoiDungKhongDinhDanh 12:39, 19 June 2022 (UTC)
Global lock for İşüçöğı
Status:   In progress
İşüçöğı (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser)
Cross-wiki abuse. Sock of User:İsmail Kendir. --Kadı Message 12:58, 19 June 2022 (UTC)
Global lock for 1919901
Status:   In progress
1919901 (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser)
Account compromised by a LTA. --Mys_721tx (talk) 01:50, 22 June 2022 (UTC)
Global lock for Panma50
Status:   In progress
Panma50 (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser)
Sockpuppet of User:Phạm Văn Rạng who is also globally locked. Sir Sputnik (talk) 02:34, 22 June 2022 (UTC)
Global lock for User:Quintinense​'s puppets
Status:   In progress
Puppets confirmed. Edmond Dantès d'un message? 05:45, 22 June 2022 (UTC)
Confirmed where? — regards, Revi 17:24, 26 June 2022 (UTC)
Global lock for 我目送 他们行色匆匆
Status:   In progress
我目送 他们行色匆匆 (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser)
Long-term abuse. 黄冰楠. -- Willy1018 (talk) 01:29, 23 June 2022 (UTC)
Global lock for 渡名喜文仁
Status:   In progress
渡名喜文仁 (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser)
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)
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)
@KhanhCN Defender1st Minh Why should they be globally locked? BRP ever 10:53, 27 June 2022 (UTC)
@BRPever: Sockpuppet KhanhCN Defender1st Minh (talk) 13:21, 27 June 2022 (UTC)
of whom? ~~~~
User:1234qwer1234qwer4 (talk) 13:52, 27 June 2022 (UTC)
@1234qwer1234qwer4 It's Ẩn danh. Both are trash accounts KhanhCN Defender1st Minh (talk) 15:33, 28 June 2022 (UTC)
Global lock for LTA
Status:   In progress
Long-term abuse. Abusive username. Avoided. --~~~~
User:1234qwer1234qwer4 (talk) 11:49, 27 June 2022 (UTC)
Global lock for Pcgeekyy
Status:   In progress
Pcgeekyy (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser)
A couple of SPAM edits/ransomware on minor Wikisource projects. I fear that it continues elsewhere. Thanks --Ruthven (msg) 13:38, 27 June 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) 15:03, 27 June 2022 (UTC)
Added 1 sock.--Lanwi1(talk) 12:10, 28 June 2022 (UTC)
Global lock for Sidowpknbkhihj socks
Status:   In progress
Long-term abuse. Locked user's sockpuppets: User:Sidowpknbkhihj (​w:ja:LTA:HEATHROW​) . --しみはる君 (talk) 15:25, 27 June 2022 (UTC)
Global lock for Nbnk68
Status:   In progress
Nbnk68 (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser)
Long-term abuse. See also Locked user's sockpuppet: User:Nbckfkh (w:ja:LTA:KFKH) . --しみはる君 (talk) 15:25, 27 June 2022 (UTC)
Global lock for KYMM226515
Status:   In progress
KYMM226515 (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser)
Long-term abuse. Locked user's sockpuppet: User:Syun respect for music (w:ja:LTA:SYUN) . --しみはる君 (talk) 15:25, 27 June 2022 (UTC)
Global lock for 科学式魔眼
Status:   In progress
科学式魔眼 (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser)
Password disclosed account. --しみはる君 (talk) 15:25, 27 June 2022 (UTC)
Global lock for Trittian
Status:   In progress
Trittian (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser)
Long-term abuse. ---- LuK3 (Talk) 21:36, 27 June 2022 (UTC)
Global lock for Torun520
Status:   In progress
Torun520 (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser)
Long-term abuse. LTA: 顓如. -- Willy1018 (talk) 00:23, 28 June 2022 (UTC)
Global lock for ↘yuen↙
Status:   In progress
↘yuen↙ (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser)
compromised. -- Willy1018 (talk) 04:51, 28 June 2022 (UTC)
Global lock for Dedemy.tech
Self-advertising — KhanhCN Defender1st Minh (talk) 05:30, 28 June 2022 (UTC)
Global lock for DAEZERO
Status:   In progress
DAEZERO (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser)
Spam / spambot. --Lymantria (talk) 05:29, 28 June 2022 (UTC)
Global lock for Spambot
Status:   In progress
Lock all:
Spambot — KhanhCN Defender1st Minh (talk) 08:11, 28 June 2022 (UTC)
@KhanhCN Defender1st Minh I looked into this. Based on what I see, I think the best idea here would be to consult viwiki CU and tell them to have a look. There are several socks that I came across but all of those I found only edited viwiki. Please try reporting it to them first.--BRP ever 08:35, 28 June 2022 (UTC)
Global lock for Jou.1207
Status:   In progress
Jou.1207 (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser)
Cross-wiki abuse. Vandalism-only account. --SCP-2000 09:20, 28 June 2022 (UTC)
Global lock for حسام علي علي جاد الكريم‎
Status:   In progress
حسام علي علي جاد الكريم‎ (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser)
Cross-wiki abuse. --​NguoiDungKhongDinhDanh 09:56, 28 June 2022 (UTC)
Global lock for حسام علي جاد ويكيبديا‎
Status:   In progress
حسام علي جاد ويكيبديا‎ (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser)
Cross-wiki abuse. --​NguoiDungKhongDinhDanh 10:02, 28 June 2022 (UTC)
Global lock for Bogudoby2
Status:   In progress
Bogudoby2 (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser)
Long-term abuse. Sockpuppet of Bogudoby, per the duck test. ----NGC 54 (talk｜contribs) 10:31, 28 June 2022 (UTC)
Global lock for IPhone 13 Poo Max
Status:   In progress
IPhone 13 Poo Max (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser)
Long-term abuse. --SHB2000 (talk | contribs) 11:45, 28 June 2022 (UTC)
Global lock for 王則文教授
Status:   In progress
王則文教授 (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser)
Long term abuse: Nipponese Dog Calvero. Was blocked on zhwiki. --SCP-2000 12:02, 28 June 2022 (UTC)
Global lock for Charli 250 sock(s)
Status:   In progress
Sport56663 (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser)
Sockpuppet(s) found in enwiki sockpuppet investigation, see w:en:Wikipedia:Sockpuppet investigations/Charli 250. Bbb23 (talk) 13:23, 28 June 2022 (UTC)
Global lock for Vasile2023
Status:   In progress
Vasile2023 (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser)
Long-term abuse. Cross-wiki abuse. Sockpuppet of Bogudoby, per the duck test. ----NGC 54 (talk｜contribs) 15:57, 28 June 2022 (UTC)
Global lock for Vasile2022
Status:   In progress
Vasile2022 (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser)
Long-term abuse. Cross-wiki abuse. Sockpuppet of Bogudoby, per the duck test. ----NGC 54 (talk｜contribs) 16:00, 28 June 2022 (UTC)
Global lock for RecomposeMyLife
Status:   In progress
Long-term abuse. LTA AgustinSepulveda2004. --LuchoCR (talk) 17:52, 28 June 2022 (UTC)
Global lock for Bestof2022 sock(s)
Status:   In progress
Samba Olek (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser)
Sockpuppet(s) found in enwiki sockpuppet investigation, see w:en:Wikipedia:Sockpuppet investigations/Friedjof​. Spicy (talk) 18:09, 28 June 2022 (UTC)
Global lock for ውክፔዲያ
Status:   In progress
ውክፔዲያ (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser)
Username means "Wikipedia" in Amharic + spam. --reNVoy (user talk) 18:56, 28 June 2022 (UTC)
Global lock for Gauravgo693
Status:   In progress
Gauravgo693 (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser)
Spam / spambot. --Johannnes89 (talk) 19:25, 28 June 2022 (UTC)
Global lock for BrigettePleasant
Status:   In progress
BrigettePleasant (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser)
Spam / spambot. --reNVoy (user talk) 19:29, 28 June 2022 (UTC)
Global lock for Heirserra
Status:   In progress
Heirserra (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser)
Long-term abuse. Gvozdet/Servansky. --Mykolatalk 20:11, 28 June 2022 (UTC)
Global lock for Fnaf sister location fox splits location circus fox comic horror
Status:   In progress
Fnaf sister location fox splits location circus fox comic horror (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser) - reincarnation of LTA Igoryu1993.--Ping08 (talk) 20:17, 28 June 2022 (UTC)
Scott game sister location freddy fazbear (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser). ~~~~
User:1234qwer1234qwer4 (talk) 20:42, 28 June 2022 (UTC)
Global lock for Vinafotograf
Status:   In progress
Vinafotograf (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser)
Long-term abuse. Lock evasion: Marsuki s.kom. --reNVoy (user talk) 20:24, 28 June 2022 (UTC)
Global lock for Transporte-77
Status:   In progress
Transporte-77 (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser)
Cross-wiki abuse. Spam / spambot. --​NguoiDungKhongDinhDanh 21:27, 28 June 2022 (UTC)
Global lock for Iamrealmohsin sock(s)
Status:   In progress
Zubaidakhan786 (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser)
Sockpuppet(s) found in enwiki sockpuppet investigation, see w:en:Wikipedia:Sockpuppet investigations/Iamrealmohsin​. GeneralNotability (talk) 23:58, 28 June 2022 (UTC)
Global lock for Thánh Chửi Wiki (Trieu Thuan Son's sockpuppet) and Trieu Thuan Son's sockpuppet(s)
Status:   In progress
Thánh Chửi Wiki (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser)
User list
Lock all:
Nguyen Van Lat (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser)
offensive/abusive username + viwiki raider KhanhCN Defender1st Minh (talk) 03:32, 29 June 2022 (UTC)
See also
Archives
2022: w1, w2, w3, w4, w5, w6, w7, w8, w9, w10, w11, w12, w13, w14, w15, w16, w17, w18, w19, w20, w21, w22, w23, w24, w25, w26
General requests for:help from a Meta sysop or bureaucrat ·deletion (speedy deletions: local · multilingual) ·URL blacklisting · new languages · interwiki map
Personal requests for:username changes ·permissions (global) · bot status ·adminship on Meta ·CheckUser information (local) ·local administrator help
Cooperation requests for:comments (local) (global) · translation
Last edited on 29 June 2022, at 06:25
Content is available under CC BY-SA 3.0 unless otherwise noted.
Privacy policy
Terms of Use
Desktop
HomeRandomLog in Settings DonateAbout MetaDisclaimers
LanguageWatchEdit