Steward requests/Global: Difference between revisions

From Meta, a Wikimedia project coordination wiki
Browse history interactively
← Older editNewer edit →
Content deleted Content added
VisualWikitext
Line 572: Line 572:
Spam / spambot. --
Spam / spambot. --
[[User:Deepest the|Deepest the]] ([[User talk:Deepest the|talk]]) 09:15, 24 August 2022 (UTC)
[[User:Deepest the|Deepest the]] ([[User talk:Deepest the|talk]]) 09:15, 24 August 2022 (UTC)
::Sorry? I'm not a spambot. [[User:Stuartyeates|Stuartyeates]] ([[User talk:Stuartyeates|talk]]) 09:24, 24 August 2022 (UTC)



=== Global lock for spamaccounts===
=== Global lock for spamaccounts===

Revision as of 09:24, 24 August 2022

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 comments48 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 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 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 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 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

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

Global block for 49.228.0.0/18

Status:    In progress

Spammy range, see [6]. ----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.[7][8][9] The user is already blocked up to 2028 at en.wiki[10], so I would highly recommend a long-term block because I just reverted this person on multiple wikis that seem to lack recent patrollers. --Tbhotch (talk) 20:35, 30 May 2022 (UTC)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 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 8.21.110.0/24

Status:    In progress

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

Global lock IP rangeblock requested (85.140.14.80/16)

Status:    In progress

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

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

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

Moved to appropriate section. ~~~~
User:1234qwer1234qwer4 (talk) 17:40, 29 June 2022 (UTC)Reply
@Koavf: If they are trusted, why aren’t they autoconfirmed? – Ilovemydoodle (talk) 19:16, 21 August 2022 (UTC)Reply

Global block for 102.182.0.0/16

Status:    In progress

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

Global block for 86.120.190.41

Status:    In progress

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

Global block for 109.107.171.0/24

Status:    In progress

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

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

Status:    In progress

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

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

Global block for LTA

Status:    In progress

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

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

Global block for 200.14.81.208

Status:    In progress

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

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

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

Status:    In progress

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

Global block for 61.221.125.204

Status:    In progress

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

Appears to be handled locally; no edits since blocks were imposed. ~~~~
User:1234qwer1234qwer4 (talk) 12:54, 11 August 2022 (UTC)Reply

Global block for 8.29.105.0/24

Status:    In progress

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

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

Status:    In progress

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

Global block for long-term abuse

Status:    In progress

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

For clarification, this request is not stale. The vandal primarily targets the English Wikipedia and sequentially waits for one of the three blocks to be lifted, before almost immediately going to that part of Auckland and attacking their usual targets -- the next one is 122.56.192.0/20, which expires next Friday. In the meantime, they ocassionally target certain editors on other wikis, as Meta-Wiki contributors Mtarch11 and Daniuu may attest. Botto (talk) 17:38, 1 August 2022 (UTC)Reply
Unfortunately, I can confirm the statement made by colleague Botto. Daniuu (talk) 18:19, 1 August 2022 (UTC)Reply
Yeah I doubt this person will ever want to contribute to Wikipedia or any sister projects in a productive way.StarTrekker (talk) 21:30, 2 August 2022 (UTC)Reply
Primefac extended 122.56.192.0/20 immediately prior to its expiration. The next range to expire will be 115.189.0.0/16, in October. I would otherwise believe this would cut it, but considering this individual's track record and their persistence on other wikis, I would still push for a fresh 1-year-block for all three ranges, so they lose interest. Botto (talk) 18:58, 15 August 2022 (UTC)Reply

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

Status:    In progress

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

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

Global unblock for 197.210.53.3

Status:    In progress

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

Global block for 83.26.0.0/16

Status:    In progress

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

Global block for 68.78.104.87

Status:    In progress

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

Last edited on July 31. ~~~~
User:1234qwer1234qwer4 (talk) 11:33, 23 August 2022 (UTC)Reply

Global block for 176.59.32.0/19

Status:    In progress

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

Global block for 36.73.32.0/22

Status:    In progress

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

Global block for 149.126.236.73

Status:    In progress

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

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

Global block/unblock for spammers

Status:    In progress

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

Global block for 103.249.77.0/24

Status:    In progress

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

Global block for 102.23.96.0/22

Status:    In progress

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

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

Status:    In progress

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

Global block for 66.181.187.130

Status:    In progress

Cross-wiki abuse. Proxy BatlaaTs & Enkhsaihan2005 --Munkhzaya.E (talk) 05:55, 12 August 2022 (UTC)Reply

Global block for 192.82.70.181

Status:    In progress

Long-term abuse-banned editor tried using, machine translation. BatlaaTs & Enkhsaihan2005 --Munkhzaya.E (talk) 05:55, 12 August 2022 (UTC)Reply

Global block for 157.100.132.55

Status:    In progress

Open proxy used by WMF-banned user. --SHB2000 (talk | contribs) 06:39, 15 August 2022 (UTC)Reply

Global block for 190.57.140.84

Status:    In progress

Long-term abuse. Open proxy used by WMF-banned user. --SHB2000 (talk | contribs) 09:16, 15 August 2022 (UTC)Reply

Global block for 2400:ADC1:10C:C000:4941:A895:BB9D:AC96

Status:    In progress

Spam / spambot. --A09 (talk) 12:08, 15 August 2022 (UTC)Reply

Stopped on the day of the report. ~~~~
User:1234qwer1234qwer4 (talk) 11:38, 23 August 2022 (UTC)Reply

Global block for 2A04:CEC0:10D8:7B85:2DE9:AC91:7E4E:D29

Status:    In progress

Cross-wiki abuse. ----NGC 54 (talk｜contribs) 21:24, 15 August 2022 (UTC)Reply

Global block for 80.70.111.168

Status:    In progress

Cross-wiki abuse. Spam / spambot. See abuse log. --~~~~
User:1234qwer1234qwer4 (talk) 15:51, 16 August 2022 (UTC)Reply

Global block for 69.251.136.198

Status:    In progress

Linkspam the buygames.ps spammer see here. Hoyanova (talk) 08:20, 17 August 2022 (UTC)Reply

Global block for 176.83.42.73

Status:    In progress

Spam / spambot. --A09 (talk) 13:05, 18 August 2022 (UTC)Reply

Global block for 178.121.18.93

Status:    In progress

Cross-wiki spam. --HiyoriX (talk) 13:28, 18 August 2022 (UTC)Reply

Global block for 220.211.26.224

Status:    In progress

Cross-wiki abuse. --Drummingman (talk) 08:24, 19 August 2022 (UTC)Reply

Global block for 92.40.170.0/19

Status:    In progress

Long-term abuse. Cross-wiki abuse. --Ilovemydoodle (talk) 08:26, 20 August 2022 (UTC)Reply

Global block for 27.63.181.130

Status:    In progress

Spam / spambot. --A09 (talk) 11:08, 20 August 2022 (UTC)Reply

Global block for 119.205.222.209

Status:    In progress

Spam / Spambot. --しみはる君 (talk) 19:36, 20 August 2022 (UTC)Reply

Global block for 2A04:CEC0:1042:7890:609F:40A6:709E:9C5C

Status:    In progress

Cross-wiki abuse. --Tiger (talk) 22:41, 20 August 2022 (UTC)Reply

Global block for 2409:4064:250C:C981:1C25:759D:342B:6F82

Status:    In progress

Spam / spambot. https://hi.wikipedia.org/w/index.php?title=user_talk:Sajidperwez&oldid=5617973. --~aanzx ✉ © 06:03, 21 August 2022 (UTC)Reply

Global block/unblock for 137.101.64.238

Status:    In progress

This is an obvious sock of DaisyBus2017 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye. Same editing pattern: welcoming themselves, adding incorrect information e.g. incorrect dates/silly occupations/unlikely languages, returning to articles edited by previous socks. [11] [12] [13][14] [15]. --Sjö (talk) 06:18, 21 August 2022 (UTC)Reply

Global block for 60.120.162.139

Status:    In progress

Cross-wiki abuse. --Xiplus (talk) 11:47, 22 August 2022 (UTC)Reply

Global block for 176.161.229.123

Status:    In progress

Cross-wiki abuse. --Tiger (talk) 21:46, 22 August 2022 (UTC)Reply

Global block for 95.124.185.65

Status:    In progress

Cross-wiki abuse. --Syunsyunminmin 🗨️Talk 14:57, 23 August 2022 (UTC)Reply

Global block for 176.161.227.235

Status:    Done

Cross-wiki abuse. --Mykola 19:10, 23 August 2022 (UTC)Reply

Robot clerk note: Done by Base. MajavahBot (talk) 19:45, 23 August 2022 (UTC)Reply

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

Latest comment: 1 year ago67 comments35 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 Joe biden

Status:    Not done

Abusive username. WP:SNOW that this is real. --Ilovemydoodle (talk) 13:14, 11 August 2022 (UTC)Reply

This is an 11 year old account only registered on wikiversity. There's no point in locking it. Please only make SRG requests for ongoing cross-wiki abuse, spam, etc. Vermont 🐿️ (talk) 13:21, 11 August 2022 (UTC)Reply

Not done.-Jon Kolbert (talk) 06:16, 21 August 2022 (UTC)Reply

Global lock for Spantoots

Status:    In progress

Long-term abuse. Marat Gubaiev. --Mykola 13:30, 11 August 2022 (UTC)Reply

Lurchboxer (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser) per uk:Спеціальна:Журнал зловживань/463971 vs uk:Спеціальна:Журнал зловживань/464070 ~~~~
User:1234qwer1234qwer4 (talk) 14:19, 11 August 2022 (UTC)Reply

Global lock for IKE sock 12082022

Status:    In progress

Cross-wiki long-term abuse. w:ja:LTA:IKE sock. This account has already been blocked on jawiki, and now doing harassment of User:わたらせみずほ at c:User talk:わたらせみずほ; which IKE socks are usually appeared. --郊外生活Kogaiseikatsu (talk,contribs) 17:11, 12 August 2022 (UTC)Reply

Global lock for cross-wiki abuse and LTA sock

Status:    In progress

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

Global lock for Metaverse Yadav and socks

Status:    In progress

Lock all:

A CU might be worthwhile on hiwiki as there are definitely a ton of socks of this guy there. Praxidicae (talk) 14:44, 13 August 2022 (UTC)Reply

Global lock for Kaly cordova socks

Status:    In progress

Cross-wiki abuse. --Njd-de (talk) 21:22, 13 August 2022 (UTC)Reply

Global lock for Tommy JS socks

Status:    In progress

Long-time abuse. Cross-wiki abuse. LTA Tommy Jonathan Sinaga. – Symphonium264 (talk) 12:49, 15 August 2022 (UTC)Reply

Global block for Camaroperu

Status:    In progress

Confessed conflict of interest [16], multiple uploads of promotional material by corporate mandate[17] and spam on Commons[[18] [19]]. The second user is likely a sockpuppet created just after his ban on Commons.--MexTDT (talk) 19:30, 15 August 2022 (UTC)Reply

Global lock for 中央系統

Status:    In progress

Same user of Special:CentralAuth/顓如,also,please check sleepers and block IP/IP range(s) when account not stale. --MCC214#ex umbra in solem 09:18, 16 August 2022 (UTC)Reply

Global lock for 逐風鬼地

Status:    In progress

Viwiki raider (Nipponese Dog Calvero's sockpuppet) KhanhCN Defender1st Minh (talk) 02:55, 17 August 2022 (UTC)Reply

Global lock for Dribbler sock(s)

Status:    In progress

Lock evasion Dribbler/Rülpsmann. Sockpuppet(s) found in dewiki sockpuppet investigation w:de:Wikipedia:Checkuser/Anfragen/Dribbler.. [20]. --Johannnes89 (talk) 07:23, 17 August 2022 (UTC)Reply

Global lock for Huonggiangidol + Huonggiangidol's sockpuppets

Status:    In progress
User list

Cross-wiki abuse + viwiki raider KhanhCN Defender1st Minh (talk) 09:11, 17 August 2022 (UTC)Reply

Global lock for Rosenenaidol + Rosenenaidol's sockpuppets

Status:    In progress
User list

Cross-wiki abuse (+1 and +2 RfCU) - KhanhCN Defender1st Minh (talk) 14:15, 17 August 2022 (UTC)Reply

Global lock for Mike Matthews17

Status:    In progress

Long-term abuse. For the sake of completeness. I've noticed this account through the talk page watchlist and the edits seen are the same as previous socks of Mike Matthews, see en:Wikipedia:Sockpuppet investigations/Mike Matthews17/Archive with this account as an example, and "Geraint Harris2319" followed the same naming pattern as this one. --Iggy the Swan (talk) 16:14, 17 August 2022 (UTC)Reply

Global lock for STRUMPH-BLUE SWEET

Status:    In progress

Appears to be a lock-evading sockpuppet of Urossusa; see Stewards' noticeboard/Archives/2019-05#User making tests/comments since at least May 2017. Rambling cross-wiki; most recent locked account is probably LEGIONAR~(SAS). Other accounts include Vinsent Constantine. Sdrqaz (talk) 12:18, 18 August 2022 (UTC)Reply

Global lock for Baranov107

Status:    In progress

Cross-wiki spam. Reverted and warned on multiple wikis. Huñvreüs (talk) 08:11, 20 August 2022 (UTC)Reply

Global lock for It'sFridayAgain 19

Status:    In progress

Long-term abuse. Lock evasion: Kingshowman. --DarkMatterMan4500 (talk) (contribs) 11:34, 20 August 2022 (UTC)Reply

Global lock for TheKingdomofHeavenonEarth

Status:    In progress

Cross-wiki abuse. Both accounts have resorted to hostile behavior, and legal threats on 2 wikis. --DarkMatterMan4500 (talk) (contribs) 12:31, 20 August 2022 (UTC)Reply

Global lock for Samet Yücel socks

Status:    In progress

Lock evasion. --Njd-de (talk) 12:38, 20 August 2022 (UTC)Reply

Global lock for Hansley West

Status:    In progress

Lock evasion: ASIANPOPCHANNEL. --DarkMatterMan4500 (talk) (contribs) 15:36, 20 August 2022 (UTC)Reply

Added another account that apparently was missed, but is still within the 3-4 month range here. — The preceding unsigned comment was added by DarkMatterMan4500 (talk)

Global lock for LTA:SUMOSONG

Status:    In progress

Long-term abuse. w:ja:LTA:SUMOSONG or copycat. --しみはる君 (talk) 19:36, 20 August 2022 (UTC)Reply

Global lock for 似た傾向 and 개성

Status:    In progress

Lock evation: User:A good Wikipedian from Osaka (w:ja:WP:VIP#A good Wikipedian from Osaka). --しみはる君 (talk) 19:36, 20 August 2022 (UTC)Reply

Global lock for Narendra Varma ( Musical Artist ) and sock

Status:    Done

X-wiki sockspam, see also w:en:Wikipedia:Sockpuppet investigations/Narendra Varma ( Musical Artist ). --Blablubbs (talk) 14:00, 21 August 2022 (UTC)Reply

Done Ruslik (talk) 20:38, 23 August 2022 (UTC)Reply

Global lock for zh:LTA:2077

Status:    Done

Long-term abuse. zh:LTA:2077. --Xiplus (talk) 08:36, 22 August 2022 (UTC)Reply

Done Ruslik (talk) 20:50, 23 August 2022 (UTC)Reply

Global lock for Trevor807

Status:    In progress

Long-term abuse. Looks like impersonation accounts out of Trevor807 and Unnamedgoon that were created specifically to troll me or whatever. I don't know which LTA is running these 2 accounts, but these 2 look like sock accounts specifically made to target me. --DarkMatterMan4500 (talk) (contribs) 15:34, 22 August 2022 (UTC)Reply

Come to think of it, this seems like something that either Sinlu22, Abigblueworld, or possibly a copycat would do and/or say with either impostor accounts or hateful usernames, but it could be either one of the 2, or just a copycat perhaps. Either way, I don't think those 2 accounts were legitimately made to edit on Wikipedia, but rather here to make personal attacks and such. DarkMatterMan4500 (talk) (contribs) 17:53, 22 August 2022 (UTC)Reply

Global lock for 1Goldberg2 socks

Status:    Done

Another pair of socks of a WMF-banned user. See w:ru:Википедия:Проверка участников/КорольЮлий. SummerKrut (talk) 07:40, 23 August 2022 (UTC)Reply

Done Ruslik (talk) 20:37, 23 August 2022 (UTC)Reply

Global lock for cross-wiki abuse and LTA sock

Status:    Done

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

Done Ruslik (talk) 20:48, 23 August 2022 (UTC)Reply

Global lock for Yoga Dunia

Status:    Done

Spam / spambot. --SHB2000 (talk | contribs) 11:36, 23 August 2022 (UTC)Reply

Done Ruslik (talk) 20:35, 23 August 2022 (UTC)Reply

Global lock for Blogs19 sock(s)

Status:    In progress

Sockpuppet(s) found in enwiki sockpuppet investigation, see w:en:Wikipedia:Sockpuppet investigations/Blogs19. GeneralNotability (talk) 11:48, 23 August 2022 (UTC)Reply

Global lock for Мадина Ларина

Status:    Done

Long-term abuse. Мадина Омарова. Suggesting an LWCU. --~~~~
User:1234qwer1234qwer4 (talk) 13:21, 23 August 2022 (UTC)Reply

Done Ruslik (talk) 20:32, 23 August 2022 (UTC)Reply

Global block for User:Blablubbs Is THCNVN Channel

Sock puppet of cross-wiki abuser. SunilNevlaFan✨ 14:06, 23 August 2022 (UTC)Reply

Global lock for Prince Muntasir

Status:    Done

Cross-wiki abuse. Blocked on the Simple English Wikipedia for spamming. --JarvisJones95 (talk) 16:12, 23 August 2022 (UTC)Reply

Done Ruslik (talk) 20:29, 23 August 2022 (UTC)Reply

Global lock for KBC 14 in a nutshell

Status:    Done

Long-term abuse. --DarkMatterMan4500 (talk) (contribs) 17:27, 23 August 2022 (UTC)Reply

Done Ruslik (talk) 20:28, 23 August 2022 (UTC)Reply

Global lock for Advancetestinglabs

Status:    In progress
User list

Spam / spambot. all accounts related to each other [21][22] and to globally locked Special:CentralAuth/Tattoomagz3. --Johannnes89 (talk) 18:06, 23 August 2022 (UTC)Reply

Global lock for Mmoreno25 sock(s)

Status:    Done

Sockpuppet(s) found in enwiki sockpuppet investigation, see w:en:Wikipedia:Sockpuppet investigations/Mmoreno25. See checkuser wiki. Dreamy Jazz talk to me | enwiki 18:51, 23 August 2022 (UTC)Reply

Robot clerk note: Done by Hasley. MajavahBot (talk) 19:05, 23 August 2022 (UTC)Reply

Global lock for AmazianMassage

Status:    In progress

Spam / spambot. --Mykola 19:15, 23 August 2022 (UTC)Reply

49.145.32.44 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye is spamming the same website --Johannnes89 (talk) 19:54, 23 August 2022 (UTC)Reply

Global lock for Ishaanalvar

Status:    Done

Spam / spambot. --Francisco (talk) 20:30, 23 August 2022 (UTC)Reply

Done Ruslik (talk) 20:49, 23 August 2022 (UTC)Reply

Global lock for 419*chain

Status:    Done

Cross-wiki abuse. ----*Fehufangą ♮ ✉ Talk page ♮ 00:52, 24 August 2022 (UTC)Reply

Seems to be a lock evasion of Special:CentralAuth/418*chain --*Fehufangą ♮ ✉ Talk page ♮ 00:53, 24 August 2022 (UTC)Reply
Robot clerk note: Done by AntiCompositeNumber. MajavahBot (talk) 01:45, 24 August 2022 (UTC)Reply

Global lock for 204Rmwiki

Status:    In progress

Cross-wiki abuse. Making nonsense redirects xwiki. ----*Fehufangą ♮ ✉ Talk page ♮ 01:17, 24 August 2022 (UTC)Reply

Global lock for EverettGuy90

Status:    Done

Spam / spambot. --Mtarch11 (talk) 01:58, 24 August 2022 (UTC)Reply

Robot clerk note: Done by Jon Kolbert. MajavahBot (talk) 07:25, 24 August 2022 (UTC)Reply

Global lock for 落花时节又逢君

Status:    In progress

x-wiki abusee. --GY Fan★ 03:01, 24 August 2022 (UTC)Reply

Global lock for LTA Beautypagant socks of Dyhp612

Sockpuppets still active cross-wiki. See also cu-file on en-wiki. Hoyanova (talk) 06:38, 24 August 2022 (UTC)Reply

Global lock for Arvind2717

Status:    In progress

Spam / spambot. --Johannnes89 (talk) 07:50, 24 August 2022 (UTC)Reply

Global lock for Outsourcingb

Status:    In progress

Spam / spambot. --Johannnes89 (talk) 08:03, 24 August 2022 (UTC)Reply

Global lock for Hiey khay ljha

Status:    In progress

Spam / spambot. --Johannnes89 (talk) 08:23, 24 August 2022 (UTC)Reply

Global lock for Stuartyeates

Status:    In progress

Spam / spambot. -- Deepest the (talk) 09:15, 24 August 2022 (UTC)Reply

Sorry? I'm not a spambot. Stuartyeates (talk) 09:24, 24 August 2022 (UTC)Reply

Global lock for spamaccounts

Status:    In progress

Spam. -- Hoyanova (talk) 09:23, 24 August 2022 (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=23710795"