Steward requests/Global: Difference between revisions

From Meta, a Wikimedia project coordination wiki
Latest comment: 9 months ago by Blua lago in topic Requests for global (un)block
Content deleted Content added
Reporting 81.84.80.164 (TwinkleGlobal)
Line 41: Line 41:
Cross-wiki abuse. [[User:TenWhile6|TenWhile6]] <small>([[User_Talk:TenWhile6|talk]] <nowiki>|</nowiki> [[SWMT]])</small> 09:43, 21 July 2023 (UTC)
Cross-wiki abuse. [[User:TenWhile6|TenWhile6]] <small>([[User_Talk:TenWhile6|talk]] <nowiki>|</nowiki> [[SWMT]])</small> 09:43, 21 July 2023 (UTC)
:{{done}} --'''--'''[[User:علاء |<span style="color:black;font-family:Script MT Bold;font-size:16px;">Alaa</span> ]] [[User_talk:علاء |:)..!]] 13:48, 21 July 2023 (UTC)
:{{done}} --'''--'''[[User:علاء |<span style="color:black;font-family:Script MT Bold;font-size:16px;">Alaa</span> ]] [[User_talk:علاء |:)..!]] 13:48, 21 July 2023 (UTC)

=== Global block for [[Special:Contributions/81.84.80.164|81.84.80.164]] ===
{{Status}}
* {{Luxotool|81.84.80.164}}
Cross-wiki abuse. [[User:Blua lago|<span style='color:#596e95;'>'''Blua lago'''</span>]] [[user talk:Blua lago|<span style='color:#596e95; font-size: smaller;'>(talk)</span>]] 19:43, 21 July 2023 (UTC)


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

Revision as of 19:43, 21 July 2023

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

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 47.243.198.62

Status:    On hold

XFF trusted hosts list IP, should not be blocked. Please unblock this IP sparately in the range. --AnYiLinTalk 06:14, 21 April 2023 (UTC)Reply

@Martin Urbanec: given you were working on another XFF whitelist project. -- Amanda (she/her) 17:53, 29 April 2023 (UTC)Reply
@AmandaNP: If possible, please temporarily set the block to only apply to anonymous users. Thank you. A hard block doesn't make much sense and can actually affect normal usage, rendering the trusted list meaningless. AnYiLinTalk 04:13, 19 May 2023 (UTC)Reply
@AnYiLin: Now Not done The range gave up on giving XFF out about a month ago, right around the time you requested this. -- Amanda (she/her) 05:23, 19 May 2023 (UTC)Reply
@AmandaNP: The single IP that provides XFF information is 47.243.198.62, which is still available now. However, the entire /16 block has been blocked, resulting in this single IP unable to bypass the block. Please refer to the mentioned task below (https://phabricator.wikimedia.org/T335176#8802126) for more details. Thank you. AnYiLinTalk 05:29, 19 May 2023 (UTC)Reply
Point taken, but at the same time, this is still not actionable in my opinion. We have a process for applying for IPBE for this reason, we don't need to invite spambots and sockpuppets to start using this webhost to get around a block. We don't do this normally when people ask for their individual IP to be whitelist on any other webhost, and I don't know why we should start now. This is a software issue (of accepting the XFF or ability to whitelist IPs). If @MarcoAurelio: wishes to proceed with it, that is their choice, but it's not mine. Also, please be very careful in reverting status changes as those are only meant to be done by stewards. -- Amanda (she/her) 05:44, 19 May 2023 (UTC)Reply
This IP is a reverse proxy instead of a VPN, and it will correctly pass on the user's real IP. This ensures that those who use it are not spambots, and also ensures that CU can function properly. As for why this IP has been added to the trusted list, I believe it is precisely because it can pass on the correct XFF header, and thousands of people are using it. AnYiLinTalk 06:19, 19 May 2023 (UTC)Reply
@AmandaNP: This is an error with the GlobalBlocking extension, and it's unclear when it will be resolved. In the meantime, I suggest temporarily change the hard block on this /16 block to only anonymous users until the extension is fixed. We can observe for a period of time to see if there are any spambots or sockpuppets, and then take further action if necessary. For Chinese users, applying for IPBE on meta-wiki is a relatively unfamiliar and cumbersome process. What's more, it's not the expected result when users are prompted to be blocked while editing on a server with a trust level similar to Wikimedia cache servers. AnYiLinTalk 06:36, 19 May 2023 (UTC)Reply
I don't recall a function that would only enable the release of specific IPs within ranges, so I think something technically supported would be needed. --Sotiale (talk) 23:49, 29 April 2023 (UTC)Reply
@Sotiale: Maybe try this method. Zhwiki has a admin robot, and its white list of blocked IP uses this method. Under this method, even if all IPs cannot be blocked in the form of IP range, I think that the remaining unblocked IPs will not cause any very bad consequences. If there is a problem, just ban that IP alone (this is exactly the goal of Steward_requests/Global). After all, these IPs belong to Alibaba Cloud, and they cost money to use. It is impossible for saboteurs to hold a lot of them. AnYiLinTalk 04:57, 30 April 2023 (UTC)Reply

Global block for 2600:6C55:4800:0:0:0:0:0/48

Status:    In progress

LTA TyMega. Hoyanova (talk) 07:15, 19 July 2023 (UTC)Reply

Global block for 197.250.102.89

Status:    Done

Cross-wiki abuse. Linkspam. TenWhile6 (talk | SWMT) 09:37, 21 July 2023 (UTC)Reply

Done ----Alaa :)..! 13:49, 21 July 2023 (UTC)Reply

Global block for 109.243.144.149

Status:    Done

Cross-wiki abuse. TenWhile6 (talk | SWMT) 09:43, 21 July 2023 (UTC)Reply

Done ----Alaa :)..! 13:48, 21 July 2023 (UTC)Reply

Global block for 81.84.80.164

Status:    In progress

Cross-wiki abuse. Blua lago (talk) 19:43, 21 July 2023 (UTC)Reply

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 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 zh:LTA:莒光號列車

Status:    Done

Lock all:

Long-term abuse. Cookai🍪 (💬talk) 15:17, 25 June 2023 (UTC)Reply

Done ----Alaa :)..! 13:50, 21 July 2023 (UTC)Reply

Global lock for Nishānt Omm

Status:    Done

Cross-wiki abuse. Descriptive editing on various wikis, so Globally lock required for this user. →ÀvîRâm7(talk) 08:14, 29 June 2023 (UTC). →ÀvîRâm7(talk) 08:14, 29 June 2023 (UTC)Reply

Done ----Alaa :)..! 13:51, 21 July 2023 (UTC)Reply

Global lock for EaseUS spammers

Status:    In progress

Lock all:

Cross-wiki spam, see Talk:Wikiproject:Antispam#EaseUS Software. MER-C 17:10, 1 July 2023 (UTC)Reply

@MER-C: is there a reason why a lot of them don't have any local blocks? Jon Kolbert (talk) 03:41, 20 July 2023 (UTC)Reply
You'll have to ask the Japanese Wikipedia admins. MER-C 16:27, 21 July 2023 (UTC)Reply

Global lock for Nelo accounts

Status:    Done

Promotion, lock evasion: Nelo / Business App spam (Lilbiz); see User:Tol/D/NBA for documentation. Tol (talk | contribs) @ 00:54, 3 July 2023 (UTC)Reply

Also noting CU confirmation on Spanish Wikipedia. Tol (talk | contribs) @ 00:56, 3 July 2023 (UTC)Reply
Adding Nelodigital. Tol (talk | contribs) @ 01:29, 3 July 2023 (UTC)Reply
Done ----Alaa :)..! 13:52, 21 July 2023 (UTC)Reply

Global lock for Mofa1995

Status:    Done

Cross-wiki abuse. Spam / spambot. ‎מקףHyphen 02:11, 3 July 2023 (UTC)Reply

Done ----Alaa :)..! 13:53, 21 July 2023 (UTC)Reply

Global lock for UPE spammers

Status:    Done

Lock all:

Cross-wiki spam, see Special:Permanentlink/25255597#Enzo_Zelocchi. MER-C 17:10, 4 July 2023 (UTC)Reply

@MER-C: Those accounts seems to be all active over a year ago -- I don't see any activity which would be stopped by a lock? Am I missing something? --Martin Urbanec (talk) 21:19, 9 July 2023 (UTC)Reply
I habitually block spammers in cases like this - I've seen accounts post spam, do nothing for a few months, then return to post spam again (see e.g. w:Special:Contributions/Operationz - four month gap). MER-C 19:38, 10 July 2023 (UTC)Reply
Done ----Alaa :)..! 13:51, 21 July 2023 (UTC)Reply

Global lock

Status:    In progress

Lock all:

Cross-wiki abuse. ☀DefenderTienMinh⛤☯☽ (talk) 15:50, 6 July 2023 (UTC)Reply

Global lock for Sunrise600

Status:    In progress

Cross-wiki spam, see Talk:Wikiproject:Antispam#Global_Tech_Summit_+_related_pages. MER-C 16:52, 6 July 2023 (UTC)Reply

+ lock evasion Applus2021, added three other confirmed sockpuppets en:WP:Sockpuppet investigations/Applus2021/Archive. --Johannnes89 (talk) 09:16, 20 July 2023 (UTC)Reply

Global lock for Hien1975 sock

Status:    In progress

Long-term abuse. H78c67c (talk) 00:08, 7 July 2023 (UTC)Reply

Global lock for Uiop09876/Tea0987 sock

Status:    In progress

Lock evasion. See also zh:Wikipedia:傀儡調查/案件/Uiop09876 H78c67c (talk) 00:08, 7 July 2023 (UTC)Reply

Global lock for Koatochij and Tlamichin

Status:    In progress

Lock all:

Evasion by sockpuppets from Marrovi. The evasion was confirmed onNahuatl Wikipedia there Koatochij was confronted and I discussed with him, who accepted that he is Marrovi himself. Actually, there was block.

The connection with the user Tlamichin was also confirmed, he is another sockpuppet of Marrovi, who uses and uploads photos to ‘’Commons’’ from Manuel Rodriguez Villegas (Marrovi) that we see on his Facebook about his familia.

The review of records and other evidences were organized in Marrovi’s Blocked Puppet Discussion (Discusión de Títeres bloqueados de Marrovi). Akapochtli (talk) 18:41, 7 July 2023 (UTC)Reply

Global lock for Guilherme36912

Status:    In progress

Lock all:

Long-term abuse. Guilherme Gava Bergami. Sleeper check would be appreciated. ~~~~
User:1234qwer1234qwer4 (talk)
22:55, 8 July 2023 (UTC)Reply

Global lock for Yıldız01 socks

Status:    In progress

Lock all:

Sockpuppets. Long term abuse. Relevant to these requests. Please check the investigation. Mentioning the checkuser @Vincent Vega: --Tün (talk) 10:13, 9 July 2023 (UTC)Reply

Global lock for Annetyner

Status:    In progress

Cross-wiki abuse. Eihel (talk) 10:21, 10 July 2023 (UTC)Reply

Global lock for わん時計

Status:    In progress

Cross-wiki abuse. Eiyafirayoku (talk) 14:36, 10 July 2023 (UTC)Reply

Global unlock for Long Bamening Hong

Status:    In progress

Not apparently the LTA intended. cc Martin Urbanec and Johannnes89. ~~~~
User:1234qwer1234qwer4 (talk)
18:48, 10 July 2023 (UTC)Reply

Indeed, seems to be just a random vandal, no known dewiki LTA Johannnes89 (talk) 18:50, 10 July 2023 (UTC)Reply

Global lock for Emma Von Der Lerchenburg

Status:    In progress

Long-term abuse. AlPaD (talk) 20:23, 11 July 2023 (UTC)Reply

Global lock for SJasminum

Status:    In progress

abusive uploads on multiple projects, blocked at least on commons and en.wp, sock of Judgefloro, AKA en:Florentino Floro --Beeblebrox (talk) 17:58, 13 July 2023 (UTC)Reply

Global lock for 분홍분홍 토야

Status:    In progress

Lock all:

Sock puppetry and cross-wiki abuse. Dragoniez (talk) 11:07, 14 July 2023 (UTC)Reply

Global lock for Raquel Baranow

Status:    In progress

Cross-wiki abuse. Banned in 2021 on the English Wikipedia for Holocaust denial, and was just blocked on Commons for much of the same. I don't see this user being constructive any time soon. LilianaUwU (talk / contribs) 05:37, 15 July 2023 (UTC)Reply

This user is basically inactive outside of the two wikis mentioned. I currently don't see the necessity in a global lock. ~~~~
User:1234qwer1234qwer4 (talk)
11:13, 15 July 2023 (UTC)Reply

Global lock for Pelle Tuurenpoika

Status:    In progress

Sock puppet for globally blocked Risto hot sir. Account created hours after global ban of Risto's latest sock puppet Ile Masi Sameli. Thuresson (talk) 12:39, 15 July 2023 (UTC)Reply

Global lock for Faster328 sock

Status:    In progress

Long-term abuse. Faster328. LilianaUwU (talk / contribs) 02:48, 16 July 2023 (UTC)Reply

Global lock for LeonChow99 sock

Status:    In progress

Long-term abuse. Cross-wiki abuse. Cross-wiki spam and lock evasion of LeonChow99 socks. Please also CU and lock all sleeper accounts. LuciferianThomas 03:41, 16 July 2023 (UTC)Reply

Global lock for Zildzi

Status:    In progress

Long term abuse on idwiki and have been blocked indefinitely. The account moved to wikidatawiki and started making disruptive edits shortly after been blocked on idwiki. Nyilvoskt (talk) 03:50, 16 July 2023 (UTC)Reply

Global lock for Bodiadub socks

Status:    In progress

WMF banned spammer, see Wikiproject:Antispam/Archives/2021/Wikibusiness and Talk:Wikiproject:Antispam#Wikibusines round_3. MER-C 10:12, 16 July 2023 (UTC)Reply

Global lock for Kingkongpu

Status:    In progress

Cross-wiki abuse. Post off-topic discussions on the talk pages of several wiki projects.

Check his edits on the talk page, the content may be related to backing up his own published content[1][2] or reproducing en.wikipedia.org's en:Wang Puchen([3]). Rastinition (talk) 12:33, 17 July 2023 (UTC)Reply

Global lock for accounts vandalizing crwiki

Status:    In progress

Lock all:

vandalism-only accounts. Leonidlednev (talk) 04:14, 18 July 2023 (UTC)Reply

Global lock for Bogartlipa1989

Status:    In progress

Vandalism on multiple projects. Blocked on Commons for uploading attack images, blocked on EnWiki for ethnicity-focused vandalism. Behavior also extends to Wikidata. --The Squirrel Conspiracy (talk) 05:29, 18 July 2023 (UTC)Reply

Global lock for MDR Jumpwelle HIT-RADIO Halle-Leipzig *3

Status:    In progress

Long-term abuse. Likely HoY. LilianaUwU (talk / contribs) 05:03, 19 July 2023 (UTC)Reply

@LilianaUwU that's not HoY but rather a dewiki LTA (-> de:Special:AbuseFilter/394). The LTA registered at enwiki to try circumventing dewiki account creation filters [4][5]. Johannnes89 (talk) 08:49, 20 July 2023 (UTC)Reply
Huh, interesting. LilianaUwU (talk / contribs) 22:12, 20 July 2023 (UTC)Reply

Global lock for ScoobyDooandDCComicsFan900

Status:    In progress

Long-term abuse. TyMega. ---Hoyanova (talk) 07:04, 19 July 2023 (UTC)Reply

Global lock for BuickCenturyDriver socks

Status:    In progress

Long-term abuse. BuickCenturyDriver. LilianaUwU (talk / contribs) 07:01, 19 July 2023 (UTC)Reply

Global lock for Willy on wheels~enwiki socks

Status:    Done

Sockpuppets found in enwiki sockpuppet investigation, see w:en:Wikipedia:Sockpuppet investigations/CHEEIZY. Probably Willy on Wheels Girth Summit (blether) 12:03, 19 July 2023 (UTC)Reply

Robot clerk note: Done by HakanIST. MajavahBot (talk) 15:45, 21 July 2023 (UTC)Reply

Global lock for الیزام

Status:    On hold

Long-term abuse. Impersonating, see user page history at Meta. EstrellaSuecia (talk) 13:41, 19 July 2023 (UTC)Reply

EstrellaSuecia Maybe this user copy/paste another user page only? as usernames too different --Alaa :)..! 18:29, 19 July 2023 (UTC)Reply
@علاء It's exactly what they did. The first edit the account did was copy the user page of a GS into their own and then tried to blank my deletion tag. Also not the first time that user was impersonated today. In my opinion it's obvious nothing constructive will come from this account and it should be locked, or at least locally indefblocked on Meta. EstrellaSuecia (talk) 18:33, 19 July 2023 (UTC)Reply

Global lock for Explainotes

Status:    In progress

Spam / spambot. →ÀvîRâm7(talk) 10:57, 20 July 2023 (UTC)Reply

Global lock for Praelongum sock

Status:    In progress

Sockpuppet found in enwiki sockpuppet investigation, see w:en:Wikipedia:Sockpuppet investigations/Praelongum. Girth Summit (blether) 11:20, 20 July 2023 (UTC)Reply

Global lock for Abdulaziz Haji Mohammed

Status:    In progress

Cross-wiki abuse. Francisco (talk) 12:23, 20 July 2023 (UTC)Reply

Global lock for Piermark socks

Status:    In progress

Lock all:

Long-term abuse. Piermark or a copycat. — Prodraxis {talkcontribs} (she/her) 15:33, 20 July 2023 (UTC)Reply

Global lock for Aryamyherono1

Status:    In progress

Long-term abuse. Aryashahnaughty. Ingenuity (talk) 15:56, 20 July 2023 (UTC)Reply

Global lock for HitGirl97 and sock

Status:    In progress

X-wiki socking, copyvios, and other disruption - blocked on en.wiki, de.wiki, and commons. Эlcobbola talk 16:23, 20 July 2023 (UTC)Reply

Global lock for Phạm Văn Rạng sock

Status:    In progress

Self-admitted sock of User:Phạm Văn Rạng who is also globally locked. Sir Sputnik (talk) 21:06, 20 July 2023 (UTC)Reply

Global lock for Nosoyyososvos

Status:    In progress

Long-term abuse. Zhigg et. al. LuchoCR (talk) 22:46, 20 July 2023 (UTC)Reply

Global lock for Auprésent

Status:    In progress

Cross-wiki abuse. Spam / spambot. A09 (talk) 07:14, 21 July 2023 (UTC)Reply

Global lock for OlivierL69

Status:    In progress

Cross-wiki abuse. Spam / spambot. A09 (talk) 07:30, 21 July 2023 (UTC)Reply

Global lock for Jeffry3691

Status:    Done

Spambot account, blocked on nl.wiktionary after attempts to add blacklisted spamlinks. --MarcoSwart (talk) 09:43, 21 July 2023 (UTC)Reply

Done ----Alaa :)..! 13:56, 21 July 2023 (UTC)Reply

Global lock for Oqu.news1

Status:    In progress

Cross-wiki abuse. Leonidlednev (talk) 09:46, 21 July 2023 (UTC)Reply

Global lock for AXXXXK socks

Status:    Done

Lock all:

Long-term abuse. AXXXXK sock. --Minorax«¦talk¦» 10:42, 21 July 2023 (UTC)Reply

Done ----Alaa :)..! 13:56, 21 July 2023 (UTC)Reply

Global lock for Jaipurcitycab

Status:    Done

Cross-wiki abuse. Spam / spambot. MathXplore (talk) 11:17, 21 July 2023 (UTC)Reply

Robot clerk note: Done by Tegel. MajavahBot (talk) 11:45, 21 July 2023 (UTC)Reply

Global lock for Dakuloves Films

Status:    Done

Cross-wiki abuse. Spam / spambot. MathXplore (talk) 11:18, 21 July 2023 (UTC)Reply

Done ----Alaa :)..! 13:55, 21 July 2023 (UTC)Reply

Global lock for Ochukoevidence02

Status:    Done

Spam / spambot. 79a (talk) 12:13, 21 July 2023 (UTC)Reply

Done ----Alaa :)..! 13:55, 21 July 2023 (UTC)Reply

Global lock for MHNIR

Status:    Done

Spammer sock. — Prodraxis {talkcontribs} (she/her) 12:17, 21 July 2023 (UTC)Reply

Done ----Alaa :)..! 13:55, 21 July 2023 (UTC)Reply

Global lock for Larendo Valdez Operator from Iconfinder If you'd like you can ask the team for help

Status:    Done

Long-term abuse. Larendo Valdez. ~~~~
User:1234qwer1234qwer4 (talk)
12:55, 21 July 2023 (UTC)Reply

Done ----Alaa :)..! 13:54, 21 July 2023 (UTC)Reply

Global lock for WikiPainfulDeath

Status:    Done

Lock all:

Abusive username. Likely George Reeves Person. ~~~~
User:1234qwer1234qwer4 (talk)
13:02, 21 July 2023 (UTC)Reply

Robot clerk note: Done by HakanIST. MajavahBot (talk) 15:25, 21 July 2023 (UTC)Reply

Global lock for Davaha socks

Status:    Done

CU-confirmed on enwiki. Girth Summit (blether) 13:09, 21 July 2023 (UTC)Reply

Done ----Alaa :)..! 13:53, 21 July 2023 (UTC)Reply

Global lock for もぐりの中古車屋ビッグモーター

Status:    Done

Long-term abuse w:ja:LTA:ISECHIKA.--Nnh (talk) 13:25, 21 July 2023 (UTC)Reply

Done ----Alaa :)..! 13:53, 21 July 2023 (UTC)Reply

Global lock for Heymid intercourse your mom

Status:    Done

Long-term abuse. 𝐖𝐢𝐤𝐢𝐁𝐚𝐲𝐞𝐫 👤💬 15:06, 21 July 2023 (UTC)Reply

Robot clerk note: Done by HakanIST. MajavahBot (talk) 15:25, 21 July 2023 (UTC)Reply

Global lock for ISECHIKA

Status:    In progress

Lock all:

Long-term abuse. w:ja:LTA:ISECHIKA. Syunsyunminmin 🗨️talk 15:50, 21 July 2023 (UTC)Reply

Global lock for Ихор Охирко

Status:    Done

Long-term abuse. Lock evasion. Oгірко. reNVoy (user talk) 15:58, 21 July 2023 (UTC)Reply

Robot clerk note: Done by Mykola7. MajavahBot (talk) 17:45, 21 July 2023 (UTC)Reply

Global lock for Papa2004 socks

Status:    In progress

Lock all:

Respamming of Moscow Social Pedagogical Institute. See Talk:Wikiproject:Antispam#Papa2004,_or_Wikibusines_again. MER-C 16:32, 21 July 2023 (UTC)Reply

Global lock for YassarBukhari

Status:    In progress

Spam / spambot. Crosswiki spam, undisclosed paid editing, see enwp. Count Count (talk) 17:31, 21 July 2023 (UTC)Reply

Global lock for VernonMoorhouse

Status:    In progress

Spam / spambot. Syunsyunminmin 🗨️talk 18:02, 21 July 2023 (UTC)Reply

Global lock for 3 spambots

Status:    In progress

Global lock on 3 spambots for spamming the same links and the same Polish text in the English Wikipedia. --LDM2003 (talk) 18:24, 21 July 2023 (UTC)Reply

See also