Steward requests/Global

From Meta, a Wikimedia project coordination wiki
< Steward requests
This is an archived version of this page, as edited by Ivanvector (talk | contribs) at 15:01, 8 February 2023 (→‎Global lock for DJdjPollard15: new request). It may differ significantly from the current version.

Latest comment: 1 year ago by Ivanvector in topic Requests for global (un)lock and (un)hiding
Skip to top
Skip to bottom
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

Latest comment: 1 year ago81 comments42 people in discussion

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 block for 36.71.80.9

Status:    In progress
IP list

Long Term Abuse. Cross-wiki abuse, Proxy abuse & distributive editing in enwiki, mswiki & idwiki within footage on idwiki Doraemon Movie Article and other article related. -- AF1011 (talk) 01:18, 16 October 2022 (UTC)Reply

Note Note: @AF1011: I have moved your request to Requests for global (un)block!  ☀DefenderTienMinh☽  (discussion) 09:56, 16 October 2022 (UTC)Reply

Global block for 91.197.234.0/23

Status:    In progress

Block per No_open_proxies. F-Secure Freedome VPN IP-range 95.175.96.0/19 is already blocked and this is for filling the missing IP-ranges. --Zache (talk) 08:46, 22 October 2022 (UTC)Reply

I added another Freedome ip-range (168.1.192.0/18) --Zache (talk) 07:44, 27 October 2022 (UTC)Reply
@Jon Kolbert: 95.175.96.144/28 (part of 95.175.96.0/19 blocked by you) is mapped to a software company named w:en:Solita (company). There was a question why they were blocked so that they cannot even create accounts. I answered because IP-range is part of a larger block of Freedome as an open proxy. However, if it is possible to somehow allow them to edit it would be nice. Are there better options than unblocking locally in different wikis? --Zache (talk) 13:31, 16 November 2022 (UTC)Reply

Global unblock for 163.116.135.0/24

Status:    On hold

I was affected by this block (specifically at IP 163.116.135.91) on English Wikipedia, where I am an editor. This is almost certainly related to blocks on various Netskope IPs noted in this discussion. Netskope has a number of IPs beyond just that in the 163.116.128.0/17 range. It remains, just as earlier in 2021, a huge stretch that Netskope services are blocked on the open proxies policy. It is not an open proxy inasmuch as it is a corporate network security company. You literally cannot even subscribe to Netskope without getting a corporate quote. Users cannot choose an exit node. The range of the block also is rather large.

I think all Netskope exit nodes should be changed to soft block, per the response from that steward request from over a year ago. There exist continued requests for users (eg 1, 2, 3) to be unblocked from Netskope services. The default of blocking all service from Netskope seems to me to be wildly overbroad. Ifly6 (talk) 04:15, 9 November 2022 (UTC)Reply

@Martin Urbanec:--Alaa :)..! 15:20, 4 January 2023 (UTC)Reply

Global block for 190.61.0.0/19

Status:    In progress

Webhost; spambot abuse (see ST). --~~~~
User:1234qwer1234qwer4 (talk) 01:16, 12 November 2022 (UTC)Reply

Global block for 2a03:e600:100::/48

Status:    In progress

TOR exit anonymizer. Thanks in advance! ---- Jeff G. ツ (please ping or talk to me) 09:33, 12 November 2022 (UTC)Reply

Global block for 149.34.240.0/20

Status:    In progress

Cross wiki vandalism, conform no open proxy policy - is VPN/Proxyserver CDN77 Datacamp Ltd. -- Hoyanova (talk) 14:47, 15 November 2022 (UTC)Reply

Global block for 94.46.220.0/22

Status:    In progress

Webhost; spambot abuse (see ST). --~~~~
User:1234qwer1234qwer4 (talk) 19:50, 19 November 2022 (UTC)Reply

Global block for 2001:8003:b1b8:bf00::/64

Status:    In progress

Continued crosswiki trolling after the expiration of this global block. Escalation would be to 2001:8003::/32. Thanks in advance! ---- Jeff G. ツ (please ping or talk to me) 10:52, 26 November 2022 (UTC)Reply

GUC shows latest edits to be on 5 November (on a wiki where the range has been blocked); this probably needs some additional evidence (even more so for the suggested "escalation" to a huuuge range). ~~~~
User:1234qwer1234qwer4 (talk) 23:13, 8 December 2022 (UTC)Reply
@1234qwer1234qwer4: They are back today, see these contributions. -- Jeff G. ツ (please ping or talk to me) 12:55, 9 December 2022 (UTC)Reply
And these. -- Jeff G. ツ (please ping or talk to me) 01:37, 14 December 2022 (UTC)Reply
And those. -- Jeff G. ツ (please ping or talk to me) 11:50, 28 December 2022 (UTC)Reply
And more [1]. 11:18, 15 January 2023 (UTC)Reply

Global block for 94.229.208.0/20

Status:    In progress

Long-term cross-wiki vandalism targetting pages related to the Cugowski family (Polish musicians) on plwiki, enwiki and commons. --jdx Re: 22:17, 27 November 2022 (UTC)Reply

Global block for 202.75.0.0/16

Status:    In progress

Cross-wiki abuse. Cross-wiki abuse in zhwiki and enwiki. --LuciferianThomas 08:05, 29 November 2022 (UTC)Reply

Subrange 202.75.86.0/24 is already locally blocked in meta, and /16 range blocked in zh and en wikis. LuciferianThomas 08:17, 29 November 2022 (UTC)Reply
Established abuser: Sorcerex per Steward_requests/Checkuser/2022-11#202.75.83.58@zh.wikipedia. LuciferianThomas 08:21, 29 November 2022 (UTC)Reply

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

Status:    In progress

Continuously long-term abuse, cross-wiki abuse and proxy abuse. They also have vandalism Indonesian Wikipedia, Malay Wikipedia and many of WikiMedia projects by adding unsourced content and targeting Indonesian football clubs, companies and television shows related, the evidence is here and here BisikiNG (talk) 06:30, 1 December 2022 (UTC)Reply

Global block for 147.158.0.0/16

Status:    In progress

Cross-wiki abuse. --BisikiNG (talk) 09:30, 1 December 2022 (UTC)Reply

Global block for 37.221.136.0/21

Status:    In progress

Open proxy. --reNVoy (user talk) 20:04, 27 December 2022 (UTC)Reply

Global block for 2405:4802:1a5:58f0::/64

Status:    In progress

Cross-wiki abuse. Thanks in advance! ---- Jeff G. ツ (please ping or talk to me) 21:44, 27 December 2022 (UTC)Reply

2405:4802::/32 xwiki-contribs • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye also meets the criteria. ---- Jeff G. ツ (please ping or talk to me) 23:09, 27 December 2022 (UTC)Reply

Global block for 111.119.187.0/24

Status:    In progress

Cross-wiki abuse. Highly abused IP range [2]. It was blocked on fawiki, enwiki and simplewiki. --SCP-2000 14:23, 28 December 2022 (UTC)Reply

Global block for 2601:240:CD09:3F61:40F5:5D25:AC65:91E0

Status:    In progress

Long-term abuse. Cross-wiki abuse. -- YIEWI talk 19:16, 29 December 2022 (UTC)Reply

Global block for 37.26.83.160/27

Status:    In progress

While 37.26.83.176/30 is already blocked (cf. request), it looks like the range could be extended to at least 37.26.83.160/27 (e.g. 37.26.83.167 was active today outside the /30 range). --Titore (talk) 20:52, 29 December 2022 (UTC)Reply

Global lock and block for many sockpuppets of single user (IPs)

Status:    In progress
IP list

Request originally filed under this section. The rationale for this request is shown there (I just did the formatting of the request). Kind regards, --Daniuu (talk) 22:58, 1 January 2023 (UTC)Reply

Global block for 185.254.52.0/24

Status:    In progress

Open proxy. --reNVoy (user talk) 23:03, 4 January 2023 (UTC)Reply

Global block for 158.62.66.194

Status:    In progress

Falsifying date-of-birth, date-of-death and age in biography articles. Already blocked in kowiki. Their behaviours are identical to the globally blocked 120.143.189.106 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye, 110.8.46.113 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye, 221.168.26.189 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye, 221.168.23.69 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye, Kaboom4545 (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser). Example:en:Special:Diff/1131853010 by 158.62.66.194; en:Special:Diff/1112608989 by Kaboom4545. --Wotheina (talk) 03:19, 6 January 2023 (UTC)Reply

Global block for 173.93.96.0/19

Status:    In progress

Cross-wiki long-term abuse: Hoggardhigh (see also my previous report about an IP in this range). This range, which is based in the US, has been globally blocked on enwiki. Graham87 (talk) 04:29, 7 January 2023 (UTC)Reply

Global block for 2409:4064:E0A:988B:A5F9:586:7B29:7476

Status:    In progress

Cross-wiki abuse. Spam / spambot. --Syunsyunminmin 🗨️talk 09:58, 8 January 2023 (UTC)Reply

Global block for 37.73.9.245

Status:    In progress

Cross-wiki abuse. --Johannnes89 (talk) 20:27, 8 January 2023 (UTC)Reply

Global block for 218.250.24.0/23

Status:    In progress

Long-term abuse. Cross-wiki abuse. 米記123。. --MCC214#ex umbra in solem 11:03, 9 January 2023 (UTC)Reply

Global block for 2409:4064:228C:48CF:8FC8:568:9847:13CB

Status:    In progress

Cross-wiki abuse. --Tryvix1509 (talk) 03:42, 10 January 2023 (UTC)Reply

Global block for 157.97.120.0/21

Status:    In progress

See here. Conform no open proxy policy - VPN/Proxyserver --- Hoyanova (talk) 16:07, 10 January 2023 (UTC)Reply

Global block for 2600:6C40:5400:1192:64C2:B20D:E2BE:E050

Status:    In progress

Long-term abuse. Cross-wiki abuse. -- YIEWI talk 14:09, 11 January 2023 (UTC)Reply

Global block for 43.241.192.217

Status:    In progress

Open proxy. --Ferien (talk) 18:18, 11 January 2023 (UTC)Reply

Global block for Special:Contributions/2A01:CB19:38E:5D00:4C49:7936:7AA9:9C93

Status:    In progress

Cross-wiki abuse. Socks of Special:CentralAuth/Acacibib. --Jonteemil (talk) 22:41, 12 January 2023 (UTC)Reply

Global block for open proxies abused on svwiki

Status:    In progress

Open proxy, different hosting companies. Abused on svwiki by LTA. --EstrellaSuecia (talk) 00:22, 13 January 2023 (UTC)Reply

Global block for 87.244.190.139

Status:    In progress

Long-term abuse. Proxy. --― Blaze WolfTalkBlaze Wolf#6545 02:34, 14 January 2023 (UTC)Reply

Global block

Status:    In progress
IP list

Kit vandal on ENWIKI and CommonsWiki. Flix11 (talk) 07:42, 14 January 2023 (UTC)Reply

Global block for 41.143.0.0/16

Status:    In progress

Cross-wiki abuse. Blocked on 3 wikis. Thanks in advance! ---- Jeff G. ツ (please ping or talk to me) 10:45, 14 January 2023 (UTC)Reply

Global block for 49.216.233.148

Status:    In progress

Cross-wiki long-term abuse: w:WP:LTA/NDC. This IP has restored edits by past socks at c:File:Peter Huang and Jason Lin 2018-03-25.jpg, which had been semi-protected before. See also c:Commons:Administrators' noticeboard/Blocks and protections#Request for page semi-protection for File:Peter Huang and Jason Lin 2018-03-25.jpg. This IP also been appeared on jawiki. w:ja:李登輝 is Taiwanese politician. --郊外生活Kogaiseikatsu (talk,contribs) 06:38, 15 January 2023 (UTC)Reply

Global block for spambots

Status:    In progress

Spam / spambot. --Superpes15 (talk) 15:25, 15 January 2023 (UTC)Reply

Global block for 2A00:1B88:4::2 and 178.20.55.16

Status:    In progress

Tor exit node. --Huñvreüs (talk) 19:54, 17 January 2023 (UTC)Reply

Global block for 114.125.144.0/20

Status:    In progress

Cross-wiki abuse. Abuse of TPA. Thanks in advance! ---- Jeff G. ツ (please ping or talk to me) 21:57, 17 January 2023 (UTC)Reply

Global block for 140.213.0.0/16

Status:    In progress

Cross-wiki abuse. Thanks in advance! ---- Jeff G. ツ (please ping or talk to me) 03:15, 18 January 2023 (UTC)Reply

Global block for 2001:B042:4005:0:0:0:0:0/48

Status:    In progress

Long-term abuse. Cross-wiki abuse. Xayahrainie43. --MCC214#ex umbra in solem 06:52, 18 January 2023 (UTC)Reply

Global block for OPs, VPNs and/or Spambots

Status:    In progress

Spam/spambots. These IPs are also open proxies/VPNs/webhosts operated by the American VPN provider Norton ([3]).

These events have also been noticed:

  • Mass sockpuppetting (excessive number of accounts and IPs for editing at first, avoiding scrutiny, discussing with other username of self, thanking to other username of self, using summaries to "react" to other username of self, contributing to one page from multiple usernames, contributing to discussions from more than one username in topic, creating an illusion of support, pretending to speak in different languages, less oriented users are being blocked because admins allege they are socks, even if not from any related IP listed above, other IP ranges being hacked, etc...).
  • Abusive Usernames (they are mostly wannabe-funny, sometimes named after kids shows and cars, certain usernames even possibly violate copyright as they are copied from Fandom).
  • Excessive sneaky vandalism (often appearing to be constructive and hard to discover, also trivial vandalisms by constantly repeating the same violations of page format or style although long-term user knowing such rules very well).
  • And a strange ability to hack into other IPs to create unauthorized socks (i.e. the currently-inactive BobTheBuilder982 sock that is alleged to be created under one of the IPs listed above).

Most mentioned issues above occur on the English Wikipedia but some usernames/IPs are similarly active on the Spanish Wikipedia. Block for at least until 31 December 2024 and run a sleeper check. VandalMan247 (talk, contribs) 02:30, 19 January 2023 (UTC)Reply

Global block for 2001:44c8::/32

Status:    In progress

Cross-wiki abuse. Thanks in advance! ---- Jeff G. ツ (please ping or talk to me) 14:36, 19 January 2023 (UTC)Reply

Global block for Special:Contributions/2404:3100:1800::/45

Status:    In progress

Cross-wiki abuse. Spam / spambot. --~StyyxTalk? 20:27, 19 January 2023 (UTC)Reply

Global block for 218.250.188.0/22

Status:    In progress

Long-term abuse. Cross-wiki abuse. 米記123. --MCC214#ex umbra in solem 06:31, 21 January 2023 (UTC)Reply

Global block for 2600:1700:9040:1A90:0:0:0:0/64

Status:    In progress

Disney vandal/Bambifan. Wutsje (talk) 05:16, 22 January 2023 (UTC)Reply

Global block for 176.65.112.0/20

Status:    In progress

Only linkspam cross wiki from Russia. Hoyanova (talk) 11:39, 23 January 2023 (UTC)Reply

Global block for 207.166.32.0/21

Status:    In progress

Schoolserver. Only cross wiki vandalism. Continues everywhere since blocked long time on en-wiki. ---Hoyanova (talk) 08:08, 25 January 2023 (UTC)Reply

Global block for 2a01:8640:12::/48

Status:    In progress

2a01:8640:12::/48 xwiki-contribs • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye

Per No open proxies, hosting/VPN provider (Hostzealot). --Thibaut (talk) 09:15, 25 January 2023 (UTC)Reply

Global block for 2401:4900:3C74:E77B:FE9F:8DB8:233E:AE7F

Status:    In progress

Cross-wiki abuse. Spam / spambot. --Tryvix1509 (talk) 04:33, 29 January 2023 (UTC)Reply


Global block for 194.61.40.0/23

Status:    In progress

Cross wiki vandalism, conform no open proxy policy - is VPN/Proxyserver GSL Networks Pty LTD. -- Hoyanova (talk) 09:07, 29 January 2023 (UTC)Reply

Global block for 2405:201:4018:2E10:6C:C984:BCB9:9932

Status:    In progress

Long-term abuse. Spam / spambot. This IP is creating a page with incorrect words. -- Manish Panwar (talk) |Contribs) 11:05, 29 January 2023 (UTC)Reply

Global block for Bambifan

Status:    In progress

LTA Bambifan. Hoyanova (talk) 07:29, 2 February 2023 (UTC)Reply

Global block for 188.123.231.0/24

Status:    In progress

Cross-wiki abuse. Open proxy. Thanks in advance! ---- Jeff G. ツ (please ping or talk to me) 19:45, 5 February 2023 (UTC)Reply

Global block for 2600:1000::/28

Status:    In progress

Cross-wiki abuse. Open proxy. Blocked on 3 wikis. Thanks in advance! ---- Jeff G. ツ (please ping or talk to me) 06:23, 6 February 2023 (UTC)Reply

Global block for 2600:1700:8F50:31F0:D8C5:B072:8B0F:4C80

Status:    In progress

Cross-wiki abuse. Wikidata and enWP. --Eihel (talk) 23:35, 6 February 2023 (UTC)Reply

Global block for 2603:8000:9B02:D635:A030:F354:28CC:3011

Status:    In progress

Cross-wiki abuse. --Xnet1234 (talk) 00:07, 7 February 2023 (UTC)Reply

Global block for 180.214.232.81

Status:    In progress

Abused open proxy. --IWI (talk) 02:51, 7 February 2023 (UTC)Reply

Global block for 2401:4900:45EB:22BB:FD16:7F45:E281:7CD1

Status:    In progress

Spam / spambot. -- Manish Panwar (talk) |Contribs) 13:34, 7 February 2023 (UTC)Reply

Global block for 187.211.76.157

Status:    In progress

Cross-wiki abuse. MediaWiki and WD. --Eihel (talk) 14:50, 7 February 2023 (UTC)Reply

Global block for 92.189.212.235

Status:    In progress

Cross-wiki abuse. esWP and caWP. --Eihel (talk) 14:57, 7 February 2023 (UTC)Reply

Global block for 194.167.42.37

Status:    In progress

Long-term abuse. Cross-wiki abuse. --Eihel (talk) 15:18, 7 February 2023 (UTC)Reply

Global block for 186.98.243.246

Status:    In progress

Long-term abuse. Andres camilo ruiz. --IWI (talk) 17:22, 7 February 2023 (UTC)Reply

Global block for 36.11.224.0/21

Status:    Done

Cross-wiki abuse. --Johannnes89 (talk) 19:37, 7 February 2023 (UTC)Reply

Robot clerk note: Done by BRPever. MajavahBot (talk) 11:05, 8 February 2023 (UTC)Reply

Global block for 2405:4802:2EB:D430:3834:86A2:466F:D818

Status:    In progress

Trieu Thuan Son's Sock. --Quangkhanhhuynh (talk) 01:45, 8 February 2023 (UTC)Reply

Global block for 91.214.136.0/23

Status:    In progress

Cross-wiki abuse. Open proxy. --reNVoy (user talk) 10:47, 8 February 2023 (UTC)Reply

Global block for 160.176.77.253

Status:    Done

Long-term abuse. Cross-wiki abuse. --Xiplus (talk) 12:31, 8 February 2023 (UTC)Reply

Robot clerk note: Done by Hoo man. MajavahBot (talk) 13:45, 8 February 2023 (UTC)Reply

Global block for 102.214.88.8

Status:    In progress

Open proxy. More global ban evasion action by Ljupco Steriev, GRP (George Reeves Person), Wikinger, or a friend. Thanks in advance! ---- Jeff G. ツ (please ping or talk to me) 13:31, 8 February 2023 (UTC)Reply

Global block for 2001:B07:A2A:3A80::/64 c.a.

Status:    In progress

LTA/CWA, doxing, attacking nl:wiki main page. Wutsje (talk) 14:43, 8 February 2023 (UTC)Reply

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

Latest comment: 1 year ago60 comments38 people in discussion

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 it 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-oversight@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-appeals@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 socks of Eiskrahablo

Status:    In progress

Lock all:

LTA based on id.wikipedia. CU confirmed on Commons. --Paul_012 (talk) 19:07, 11 December 2022 (UTC), 00:03, 13 December 2022 (UTC)Reply

Global lock for Younes.bashiri80, 10brj, Wikibashir, Younes.bashiri2001

Status:    In progress

Lock all:

i assume that these accounts used for sockpuppetry and they're responsible for cross-wiki spam, i even asked for global sysop to take down their spam on several wikis (diff). i request global lock as this diff proves their sockpuppetry and cross wiki spam --🌸 Sakura emad 💖 (talk) 09:22, 12 December 2022 (UTC)Reply

Global lock for w:zh:LTA:MLLM sockpuppets

Status:    In progress

Lock all:

Long-term abuse. Cross-wiki abuse. w:zh:LTA:MLLM sockpuppets. Vandalism in zhwiki and abusing Commons to upload out of scope media. --LuciferianThomas 16:34, 26 December 2022 (UTC)Reply

Global lock and block for many sockpuppets of single user (accounts)

Status:    In progress
List of usernames and IPs (some may be openproxys)
Lock all:

User orginally contributed as Pyprilescu but then started to create many more accounts to the point it certainly passed any level of tolerance.

Moreover:

  • Massive sockpuppetting (excessive number of accounts and IPs for editing at first, avoiding scrutiny, discussing with other username of self, thanking to other username of self, using summaries to "react" to other username of self, contributing to one page from multiple usernames, contributing to discussions from more than one username in topic, creating an illusion of support, pretending to speak in different languages, less oriented users are being juggled because they don't know it is same person etc...).
  • Usernames are mostly wannabe-funny, sometimes reacting to current happennings on wiki, certain usernames even possibly violate copyright as they are in form of authored aphorisms (or slightly obfuscated).
  • Repetitive sneaky vandalisms, often very sophisticated and hard to discover, also trivial vandalisms by constantly repeating the same violations of page format or style although long-term user knowing such rules very well.

Somebody may object that checkuser is needed, but duck test here is very obvious. (Mr. Martin Urbanec will know.)

Most mentioned issues happens on czech wiktionary but some usernames are similarly active on other czech and slovak wikis. Tsechische (talk) 20:00, 31 December 2022 (UTC)Reply

@Tsechische: Thanks for raising this matter and filing the request. I have now formatted the request with the conventional templates (and moved the IPs to the section on global blocks). Daniuu (talk) 23:02, 1 January 2023 (UTC)Reply

Global lock for Boogi wu

Status:    In progress

Cross-wiki abuse. Enough, this user's cross-wiki introducing hoaxes is finally over. --Lemonaka (talk) 02:39, 4 January 2023 (UTC)Reply

cc @AmandaNP who imposed previous block on Chinese Wikipedia, now there are three blocks on all active projects for vandalism-only Lemonaka (talk) 14:19, 4 January 2023 (UTC)Reply
For the record, it's actually 2 blocks for vandalism, and one CU block.
Given the nature of the zhwiki block, I'd prefer a seperate set of eyes consider the lock. -- Amanda (she/her) 14:40, 4 January 2023 (UTC)Reply
FWIW, w:zh:Special:Diff/75367176, further discussion of this block on Chinese Wikipedia. Lemonaka (talk) 22:18, 9 January 2023 (UTC)Reply

Global lock for Ban Mai Miss Peace Vietnam 2022

Status:    In progress

Abusive username. Promotional username. --Tryvix1509 (talk) 13:22, 18 January 2023 (UTC)Reply

MoreInfo Additional information needed Cross-wiki vandalism. ([4] and [5])  ☀DefenderTienMinh☽  (discussion) 10:55, 30 January 2023 (UTC)Reply

Global lock for Hougan Misuchachi

Status:    In progress

Long-term abuse. --𝐖𝐢𝐤𝐢𝐁𝐚𝐲𝐞𝐫 👤💬 19:35, 20 January 2023 (UTC)Reply

@WikiBayer: The user is not blocked anywhere - could you expand? Jon Kolbert (talk) 14:54, 5 February 2023 (UTC)Reply
P@Jon Kolbert: This is Aguchito2023 Aleluya2022 --𝐖𝐢𝐤𝐢𝐁𝐚𝐲𝐞𝐫 👤💬 15:10, 5 February 2023 (UTC)Reply

Global lock for DjMrj384AusidnV7511

Status:    In progress

Long-term abuse. Cross-wiki abuse. R1t5. --Princess Rosalina Q 462558 03:17, 27 January 2023 (UTC)Reply

Global lock for Anil King bhadohi

Status:    In progress

Lock all:

Spam / spambot. sockpuppet. -- Manish Panwar (talk) |Contribs) 12:28, 29 January 2023 (UTC)Reply

Global lock for spambots

Status:    In progress

Lock all:

Active cross-wiki spammers. Actually there is a whole group of users, mostly inactive at the moment. They spam using non-reliable websites from a list of around 300 items (full list of links can be found for example on one of their site - 1). If the result of this request will be positive, I'll provide a complete list of users and ip.--Sigwald (talk) 16:36, 30 January 2023 (UTC)Reply

Global lock for NDC sock 01022023

Status:    In progress

Cross-wiki long-term abuse: w:WP:LTA/NDC. per contributions on c:File:Peter Huang and Jason Lin 2018-03-25.jpg. I guess the username may be slander about Xi Jinping (習近平) in Chinese language. --郊外生活Kogaiseikatsu (talk,contribs) 18:01, 1 February 2023 (UTC)Reply

Global lock for long-term abusers

Status:    In progress

Lock all:

Long-term abuse, and impersonation. The first Tailsultimatefan is impersonating the globally locked Tailsultimatefan3891 (CA), the second PBSR\QCRSDBSR is impersonating the globally locked users PBSR\QCRSDBSR0199 (CA) and PBSR\QCRSDBSR9901 (CA). The third and fourth Miraheze users are alts. --Solaris5296 (talk) 13:09, 3 February 2023 (UTC)Reply

Global unlock for Raymondskie99

Status:    In progress

This user was trying to appeal their enwiki ban but could not participate in the discussion due to being globally locked five or so years ago for crosswiki vandalism, causing the appeal to be closed prematurely. The instructions here seem to imply that I could just make an unlock request on his behalf. If not, please advise me what, if any, information he should include when submitting a request via UTRS. —Compassionate727 (T·C) 16:16, 3 February 2023 (UTC)Reply

I think that the user should address their appeal to the English Wikipedia Arbcom. We will consider unlocking them if the Arbcom deems their appeal credible. Ruslik (talk) 20:17, 5 February 2023 (UTC)Reply

Global lock for Karsingtimer

Status:    In progress

Long-term abuse. Cross-wiki abuse. See de:WP:Checkuser/Anfragen/Olympiasontrial, Jidsareonolympia, GLGermann / en:WP:Sockpuppet investigations/Europefan [6][7]. --Johannnes89 (talk) 15:54, 4 February 2023 (UTC)Reply

Global lock for Altdewapkr

Status:    In progress

Spam / spambot. Blocked locally. See past disruption documented in various spam reports. [8]. -- -- Tamzin[cetacean needed] (she|they|xe) 22:41, 5 February 2023 (UTC)Reply

Global lock for Vandman49

Status:    In progress

Long-term abuse. --Someone who's wrong on the internet (talk) 03:36, 6 February 2023 (UTC)Reply

Global lock for AlessandroIX

Status:    In progress

Long-term abuse. A1cb3. --Mtarch11 (talk) 06:14, 6 February 2023 (UTC)Reply

Global lock for Seoanalystwosa

Status:    In progress

Spam / spambot. --IWI (talk) 09:53, 6 February 2023 (UTC)Reply

Global lock for Jaincu

Status:    In progress

Cross-wiki abuse. Spam / spambot. --A09 (talk) 10:20, 6 February 2023 (UTC)Reply

Global lock for Healthandhealmedia

Status:    In progress

Spam / spambot. --IWI (talk) 11:16, 6 February 2023 (UTC)Reply

Global lock for Nobh is back again and is even tougher than before!

Status:    In progress

Long-term abuse. --DarkMatterMan4500 (talk) (contribs) 12:32, 6 February 2023 (UTC)Reply

Also Nobh is back again one more time (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser) (and Nobh is back again (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser)), ping @Martin Urbanec, who locked Nobh is back (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser)). ~~~~
User:1234qwer1234qwer4 (talk) 20:33, 7 February 2023 (UTC)Reply

Global lock

Status:    In progress

Spam-only account, blocked in viwiki. (see [9], [10] and [11])  ☀DefenderTienMinh☽  (discussion) 23:10, 6 February 2023 (UTC)Reply

Global lock for Discover.23

Status:    In progress

See w:Wikipedia:Sockpuppet investigations/Physo172. --MarioGom (talk) 23:13, 6 February 2023 (UTC)Reply

Global lock for JunoTheShark1111

Status:    In progress

Long-term abuse. Giratto. --Someone who's wrong on the internet (talk) 07:16, 7 February 2023 (UTC)Reply

Global lock for Pagnluvs

Status:    In progress

Long-term abuse. Cross-wiki abuse. NewsRoyal e Arthur Brum. --79a (talk) 10:51, 7 February 2023 (UTC)Reply

Global lock for Jhim45

Status:    In progress

Long-term abuse. Cross-wiki abuse. Straatmeester, per findings of the nlwiki checkusers. --Daniuu (talk) 11:10, 7 February 2023 (UTC)Reply

Global lock for Abbasshaikh124 sock

Status:    In progress

Sockpuppet found in enwiki sockpuppet investigation, see w:en:Wikipedia:Sockpuppet investigations/Abbasshaikh124. Girth Summit (blether) 14:40, 7 February 2023 (UTC)Reply

Global lock for Lumtechled

Status:    In progress

Spam / spambot. --Tryvix t 14:44, 7 February 2023 (UTC)Reply

Global lock for Cloudsecuritysolutions

Status:    In progress

Spam / spambot. --IWI (talk) 17:04, 7 February 2023 (UTC)Reply

Global lock for harasser

Status:    In progress

Long-term abuse. Abusive username. --~~~~
User:1234qwer1234qwer4 (talk) 17:27, 7 February 2023 (UTC)Reply

Global lock for BiaBoia

Status:    In progress

Long-term abuse. Cross-wiki abuse. --Airtransat236 (talk) 18:57, 7 February 2023 (UTC)Reply

Global lock for صفی اعظمی

Status:    In progress

Long-term abuse. --IWI (talk) 20:15, 7 February 2023 (UTC)Reply

Global lock for 王台北

Status:    In progress

Cross-wiki abuse. Spam / spambot. --Daniuu (talk) 20:22, 7 February 2023 (UTC)Reply

Global lock for Caluma.co

Status:    In progress

Spam / spambot. --LuchoCR (talk) 23:10, 7 February 2023 (UTC)Reply

Global lock for Rplying

Status:    In progress

Lock all:

Long-term abuse. --― Blaze WolfTalkBlaze Wolf#6545 01:47, 8 February 2023 (UTC)Reply

Global lock for Ned Rex

Status:    In progress

Long-term abuse. Risto hot sir. --Mtarch11 (talk) 05:15, 8 February 2023 (UTC)Reply

Global lock for Rebecca Spiteri beating up men

Status:    In progress

Lock evasion: Cynthia Rothrock beating up males. --Mtarch11 (talk) 05:19, 8 February 2023 (UTC)Reply

+2 --A09 (talk) 13:59, 8 February 2023 (UTC)Reply

Global lock for 208wfgt21f2

Status:    In progress

Long-term abuse. Blocked on jawiki. --SCP-2000 06:47, 8 February 2023 (UTC)Reply

Global lock for spambots

Status:    Done

Spambots. --Mtarch11 (talk) 06:51, 8 February 2023 (UTC)Reply

Robot clerk note: Done by RadiX. MajavahBot (talk) 12:45, 8 February 2023 (UTC)Reply

Global lock for Emma Jame133

Status:    In progress

Spam / spambot. --Johannnes89 (talk) 10:17, 8 February 2023 (UTC)Reply

Global lock for Mahedi65

Status:    Done

Spam / spambot. Spamming link to a malicious website. --Fancy Refrigerator (talk) 12:14, 8 February 2023 (UTC)Reply

Robot clerk note: Done by Jon Kolbert. MajavahBot (talk) 13:05, 8 February 2023 (UTC)Reply

Global lock for 二ウスさん

Status:    In progress

Long-term abuse. Cross-wiki abuse. ja:LTA:SUMOSONG. --Daraku K. (talk) 12:23, 8 February 2023 (UTC)Reply

Global lock for Black History Month is in October not Feburary.

Status:    Done

Long-term abuse. --DarkMatterMan4500 (talk) (contribs) 13:12, 8 February 2023 (UTC)Reply

Robot clerk note: Done by RadiX. MajavahBot (talk) 13:25, 8 February 2023 (UTC)Reply

Global lock for 時は今 3月の中 あの未来変えるのはあなた

Status:    In progress

Long-term abuse. Cross-wiki abuse. --SCP-2000 13:54, 8 February 2023 (UTC)Reply

Global lock for Shubham Dongare

Status:    In progress

Cross-wiki abuse. --Dragoniez (talk) 14:18, 8 February 2023 (UTC)Reply

Global lock for DJdjPollard15 socks

Status:    In progress

Long-term cross-wiki abuse and sockpuppetry. Ivanvector (talk) 15:01, 8 February 2023 (UTC)Reply

See also

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

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