close
Jump to content

Steward requests/Global

From Meta, a Wikimedia project coordination wiki
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 or accounts; and (un)locks apply to global accounts (except temporary accounts).

Cross-wiki requests
Meta-Wiki requests

Requests for global (un)block

Global block for ~2026-29194-05

Status:    In progress

Spambot. SuperPianoMan9167 (talk) 22:45, 15 May 2026 (UTC)Reply

Global mass (b)lock

Status:    In progress

Lock allGlobal block all:

Open proxy XReport --Peterxytalk02:08, 16 May 2026 (UTC)Reply

Global block for ~2026-29636-43

Status:    In progress

Cross-wiki abuse XReport --نوفاك اتشمان (talk) 21:06, 16 May 2026 (UTC)Reply

Global block for ~2026-29625-22

Status:    In progress

Long-term abuse. Tenshi! (Talk page) 10:21, 17 May 2026 (UTC)Reply

Global block for ~2026-29644-57

Status:    In progress

Long-term abuse. Astrawiki. SuperPianoMan9167 (talk) 14:09, 17 May 2026 (UTC)Reply

Global block for ~2026-28812-00

Status:    In progress

Cross-wiki abuse. Der-Wir-Ing ("DWI") talk 17:22, 17 May 2026 (UTC)Reply

Global block for OnlyFansStatsEditor

Status:    In progress

Cross-wiki external link spam. Requesting a gblock rather than a lock because they've clearly declared their COI on Wikidata, and there doesn't seem to be sockpuppetry involved. lp0 on fire () 10:07, 18 May 2026 (UTC)Reply

Global block for 38.147.106.0/24

Status:    In progress

Open proxy XReport --Mt.Asahidake (talk) 10:19, 18 May 2026 (UTC)Reply

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

Suggested global lock for Masood Masjoody

Status:    In progress

Likely deceased editor (or w:WP:REALNAME violation). There is a single-edit (March 2025) user, User:Masood Masjoody, whose eponymous real-life counterpart was murdered in March 2026 (The Iranian Royalists' Thuggish Edge (Q139718149), The Guardian, CTVNews). There is a COI tag warning that the person, possibly Masjoody or else someone pretending to be him, added the main text in the Twitter lawsuits list article in the section on Masjoody's lawsuits: w:list of lawsuits involving X Corp.#Defamation and conspiracy cases in Canada by Masood Masjoody. Given the info that we do have about the real person, it does sound credible that he was the actual one-time editor. It would likely be reasonable to lock the account: if the editor was not him, then the account should be locked per w:WP:REALNAME; if the editor was him, then it should be locked because he's deceased. Boud (talk) 00:29, 11 May 2026 (UTC)Reply

I re-read w:WP:DWGA. In the case that the editor was actually Masjoody, the lack of new edits is a lack of evidence of the account having been compromised; however, it's a case where extra security is likely justified: whether he was killed by w:Reza Pahlavi supporters or by the IRGC, if he wrote down his password on a Microsoft OS or a non-FOSS mobile phone, then there do exist at least two types of actors (non-state and state) with motivations for abuse of the account who may have found that password. So that probably does justify locking. Boud (talk) 08:53, 12 May 2026 (UTC)Reply
I don’t see a reason to take global action. There is no evidence of account compromise (the account has been inactive for more than a year) and there is also no evidence that the account belongs to a dead person (it’s not uncommon for COI accounts to be named after an article subject even if someone else is operating the account). We should decline this request imo as long as local admins don’t come to a different conclusion. Johannnes89 (talk) 14:22, 16 May 2026 (UTC)Reply
I wasn't aware that it's common for COI accounts named after the subject to be actually run by someone else. I guess that if the account starts being used again, especially in a damaging way, then people will quickly notice that and then the case can be handled on enwiki. Boud (talk) 19:35, 16 May 2026 (UTC)Reply

Global lock for 樋井 漣 and socks

Status:    In progress

Lock allGlobal block all:

Cross-wiki abuse. Long-term abuse. Is indefinitely blocked on jawiki (though not globally locked) for CU-verified socking. Also uploaded fictional images on Commons, first as 漣 樋井 and now as Sakura Lens. XReport --Whyiseverythingalreadyused (t · c · he/him) 08:55, 16 May 2026 (UTC)Reply

Global lock for Ishihara Mayi

Status:    In progress

User Death. RIP. Manchiu (talk) 15:19, 16 May 2026 (UTC)Reply

RIP and sorry for the edit conflict. Source: w:zh:Special:Diff/92675361 1F616EMO (on zhwiki) 15:22, 16 May 2026 (UTC)Reply
Notice: zh:Wikipedia:互助客栈/其他#【紧急】关于此前因看护端医学误判导致误报死亡及请求后续行政操作逆转的说明: Taiwanese Elephant🐘(talk|contribs) 12:28, 17 May 2026 (UTC)Reply
It since like the user is still alive. Taiwanese Elephant🐘(talk|contribs) 12:29, 17 May 2026 (UTC)Reply

Global lock for Mutark2026

Status:    In progress

Long-term abuse. 𝐖𝐢𝐤𝐢𝐁𝐚𝐲𝐞𝐫 👤💬 (WikiBayerCatHelper) 17:48, 16 May 2026 (UTC)Reply

I do not think about this new user looks. It looks like not to get blocked. Esteban McKeever (talk) 18:00, 16 May 2026 (UTC)Reply
Unfortunately, I got banned from Wikidata due to LTA out of Henry425. Do not worry, I will find you a better place that is not socking and try again. Esteban McKeever (talk) 18:09, 16 May 2026 (UTC)Reply

┌──────┘
Feel free to ignore the globally blocked user with an outdent below their comment. Whyiseverythingalreadyused (t · c · he/him) 12:49, 17 May 2026 (UTC)Reply

Global mass (b)lock

Status:    In progress

Lock allGlobal block all:

LTA XReport --Sincerely, Qədir (talk) 19:58, 16 May 2026 (UTC)Reply

Global lock for Ayy88

Status:    In progress

Lock allGlobal block all:

Cross-wiki abuse. Spam / spambot. Harry Mitchell (talk) 20:03, 16 May 2026 (UTC)Reply

Global mass (b)lock

Status:    In progress

Lock allGlobal block all:

Cross-wiki abuse. Long-term abuse. Lock/ban evasion XReport --نوفاك اتشمان (talk) 00:24, 17 May 2026 (UTC)Reply

As the person who accidentally duplicate-reported Ghana Potage below, I endorse this report Whyiseverythingalreadyused (t · c · he/him) 12:47, 17 May 2026 (UTC)Reply

Global lock for Hadeeb Rehman

Status:    In progress

Lock allGlobal block all:

Spammers confirmed to each other and likely to the previously locked MobeenYuans/Hashdata spam farms (which might be the same farm). Harry Mitchell (talk) 13:25, 17 May 2026 (UTC)Reply

Global mass (b)lock

Status:    In progress

Lock allGlobal block all:

Long-term abuse. Lock/ban evasion XReport --NDG (talk) 20:20, 17 May 2026 (UTC)Reply

Global lock for Joél be back

Status:    In progress

Looks like a compromised account, see deleted edits on enwiki: reappeared after a five-year gap to make offensive redirects to Natanyahu, which is completely out of character for this account. Harry Mitchell (talk) 20:46, 17 May 2026 (UTC)Reply

Global lock for Bots Rogério da Silva Santana

Status:    In progress

Cross-wiki abuse. Icodense (talk) 21:44, 17 May 2026 (UTC)Reply

Global lock for 1 Alitta Cat sock

Status:    Done

Sockpuppet found in enwiki sockpuppet investigation, see w:en:Wikipedia:Sockpuppet investigations/Alitta Cat. asilvering (talk) 22:38, 17 May 2026 (UTC)Reply

Robot clerk note: BERJAYA Done by EPIC. MajavahBot (talk) 07:25, 18 May 2026 (UTC)Reply

Global lock for 11 9K1A7 socks

Status:    Done

Lock allGlobal block all:

Sockpuppets found in enwiki sockpuppet investigation. asilvering (talk) 00:11, 18 May 2026 (UTC)Reply

They weren't, that's just spihelper lying to you. All confirmed to User:HellMessenger666 via SI. -- asilvering (talk) 00:12, 18 May 2026 (UTC)Reply
@Asilvering: I'm confused, who is the sockmaster behind these accounts? (and what is "that's just spihelper lying to you" meant to mean in this context?) HellMessenger666, I take it? (9K1A7 isn't locked btw). //shb (tc) 01:52, 18 May 2026 (UTC)Reply
@SHB2000, spihelper is the script that generated the edit with the list of socks and the "found in enwiki sockpuppet investigation" comment. These are all BERJAYA Confirmed to HellMessenger666, which is glocked. I know 9K1A7 isn't locked. That's why I've reported it. -- asilvering (talk) 06:57, 18 May 2026 (UTC)Reply
Ah, right. However, in most such instances, it would have been far better to just fix up the mess caused by the script instead of leaving it in some kind of limbo – anyway, BERJAYA Done. //shb (tc) 07:00, 18 May 2026 (UTC)Reply

Global lock for Deanlondontv1

Status:    In progress

Long-term abuse. Joseph kargbo 1. Mtarch11 (talk) 02:34, 18 May 2026 (UTC)Reply

Global lock for Bubble Marinc

Status:    Done

Lock allGlobal block all:

Long-term abuse. Salebot1. Kim Nito (talk) 04:39, 18 May 2026 (UTC)Reply

+1 Emk9 (talk) 04:44, 18 May 2026 (UTC)Reply
Robot clerk note: BERJAYA Done by M7. MajavahBot (talk) 06:25, 18 May 2026 (UTC)Reply

Global lock for ARBORIO, RÁDIO RAÍZES DE UMBANDA

Status:    Done

Lock allGlobal block all:

Long-term abuse. --Morkoz (talk) 04:55, 18 May 2026 (UTC)Reply

Robot clerk note: BERJAYA Done by M7. MajavahBot (talk) 06:25, 18 May 2026 (UTC)Reply

Global lock for Jovan Ramirez

Status:    In progress

Cross-wiki abuse. Sporadic interwiki vandalism. Two vandalistic edits (1, 2) on 1 May 2022 (UTC), one on 14 January 2026, and two (1, 2) just today; those five edits comprise their entire editing history across our projects. XReport --Whyiseverythingalreadyused (t · c · he/him) 05:16, 18 May 2026 (UTC)Reply

Global lock for ЭчкКиеме

Status:    In progress

Long-term abuse ja:LTA:BULUT. しのしん (talk) 07:18, 18 May 2026 (UTC)Reply

Global lock for Alphaticvietnam2024

Status:    Done

Cross-wiki abuse. Advertising-only account. Kim Nito (talk) 07:30, 18 May 2026 (UTC)Reply

Robot clerk note: BERJAYA Done by MarcGarver. MajavahBot (talk) 11:25, 18 May 2026 (UTC)Reply

Global lock for Themagicmagician50

Status:    In progress

Block evasion by TheBellaTwins1445. Madamebiblio (talk) 09:48, 18 May 2026 (UTC)Reply

Global lock for JL NU and Morkozz

Status:    In progress

Long-term abuse. --Morkoz (talk) 10:17, 18 May 2026 (UTC)Reply

Global lock for PI 3.14159954141.3 IP

Status:    Done

Long-term abuse. MinhVN1863 (talk) 10:53, 18 May 2026 (UTC)Reply

Robot clerk note: BERJAYA Done by M7. MajavahBot (talk) 11:05, 18 May 2026 (UTC)Reply

Global lock for Rangasamarakoon

Status:    In progress

Spam / spambot. Icodense (talk) 11:08, 18 May 2026 (UTC)Reply

Global lock for Mirrorenglish

Status:    In progress

Long-term abuse. Lock/ban evasion. Lucyspears, see here

. Lymantria (talk) 11:24, 18 May 2026 (UTC)Reply

Global lock for それいけ妨害マン

Status:    In progress

Cross-wiki long-term abuse: Sidowpknbkhihj (w:ja:LTA:HEATHROW). 郊外生活Kogaiseikatsu (talk,contribs) 12:01, 18 May 2026 (UTC)Reply

Global lock for 1 ChronicleBooks885 sock

Status:    In progress

Sockpuppet found in enwiki sockpuppet investigation, see w:en:Wikipedia:Sockpuppet investigations/ChronicleBooks885. asilvering (talk) 12:02, 18 May 2026 (UTC)Reply

Global lock for Anzaiku

Status:    In progress

Cross-wiki long-term abuse: Sidowpknbkhihj (w:ja:LTA:HEATHROW). 郊外生活Kogaiseikatsu (talk,contribs) 12:02, 18 May 2026 (UTC)Reply

Global lock for Alakmarsaify socks

Status:    In progress

Sockpuppets found in enwiki sockpuppet investigation, see w:en:Wikipedia:Sockpuppet investigations/Alakmarsaify. RoySmith (talk) 12:51, 18 May 2026 (UTC)Reply

Global lock for BL Radio 1242

Status:    In progress

Long-term abuse. Special:CentralAuth/ME_Radio_1530. MathXplore (talk) 13:07, 18 May 2026 (UTC)Reply

Global lock for Jattsabh1224i

Status:    In progress

Long-term abuse. Spam / spambot. Special:CentralAuth/Jattsabh1224ii. MathXplore (talk) 13:08, 18 May 2026 (UTC)Reply

Global lock for Km masud90

Status:    In progress

Long-term abuse. Special:CentralAuth/Omagol_official. MathXplore (talk) 13:09, 18 May 2026 (UTC)Reply

See also