Jump to content

Steward requests/Checkuser

From Meta, a Wikimedia project coordination wiki
Shortcut:
SRCU
Checkuser icons
These indicators are used by CheckUsers and stewards for easier skimming of their notes, actions and comments.
{{Confirmed}}:  Confirmed {{MoreInfo}}: MoreInfo Additional information needed
{{Likely}}: Likely Likely {{Deferred}}: Deferred Deferred to
{{Possible}}: Possible Possible {{Completed}}: Completed Completed
{{Unlikely}}: Unlikely Unlikely {{TakeNote}}: Note Note:
{{Unrelated}}: Unrelated Unrelated {{Doing}}: Doing...
{{Inconclusive}}: Inconclusive Inconclusive {{StaleIP}}: Stale
{{Declined}}:  Declined {{Fishing}}: Fishing CheckUser is not for fishing
{{Pixiedust}}: Pixiedust CheckUser is not magic pixie dust {{8ball}}: 8ball The CheckUser Magic 8-Ball says
{{Duck}}:  It looks like a duck to me {{Crystalball}}: Crystalball CheckUser is not a crystal ball

This page is for requesting CheckUser information on a wiki with no local CheckUsers (see also requesting checkuser access). Make sure to follow the following instructions, or your request may not be processed in a timely manner.

Before making a request:

  1. Make sure you have a good reason for the check. It will only be accepted to counter vandalism or disruption to Wikimedia wikis. Valid reasons include needing a block of the underlying IP or IP range, disruptive sockpuppetry, vote-stacking, and similar disruption where the technical evidence from running a check would prevent or reduce further disruption.
  2. Be specific in your reasons. Ambiguous or insufficient reasons will cause delays. Explain the disruption and why you believe the accounts are related, ideally using diff links or other evidence.
  3. Make sure there are no local checkusers.
  4. Please ensure that the check hasn't already been done:


How to make a request

How to make a request:

  • Place your request at the bottom of the section, using the template below (see also {{srcu}} help).
    === Username@xx.project ===
    {{CU request
     |status          = <!--don't change this line-->
     |language code   = 
     |project shortcut= 
     |user name1      = 
     |user name2      = 
     |user name3      = 
    <!-- Add more if necessary -->
     |discussion      = [[Example]]<!-- local confirmation link / local policy link -->
     |reason          = Reasons here. ~~~~
    }}
    

    For example:

    === Example@en.wikipedia ===
    {{CU request
     |status          = <!--don't change this line-->
     |language code   = en
     |project shortcut= w
     |user name1      = Example
     |user name2      = Foo
     |user name3      = Bar
    <!-- Add more if necessary -->
     |discussion      = [[:w:en:Example]]<!-- local confirmation link / local policy link -->
     |reason          = Reasons here. ~~~~
    }}
    
  • Specify the wiki(s) you want to perform the check on.

Cross-wiki requests
Meta-Wiki requests

Requests

[edit]

Radulescuanamariaelena@ro.wikipedia

[edit]

DEbopexe@zh.wikipedia

[edit]
Hi all - Just updating on the request: all accounts listed except FitchPepys, Alsafa365, Roxanne Godwin, Frisonnit, EginaldTrosin946885, Gsgarzo, WadeRussell, Captain Jack Lee, Kknksnfd, Yiberifowuti, 刘巴伦, 香蕉凤梨酥, Alfgaws, Chris5655, Deirdremoss, and 为世界做贡献 have been locally blocked through duck. Again, thanks in advance for processing the check. --)dt 09:02, 29 June 2026 (UTC)[reply]
It does not seem wise to spend too much time investigating all the numerous accounts. If not all of them need to be investigated and some are merely for reference, I request that you categorize them.
For example, dividing them into three groups—1) accounts that have not yet been blocked and require investigation, 2) accounts that have already been investigated, and 3) accounts that have already been blocked by Duck—would make our work a little easier. Thank you in advance. --Sotiale (talk) 13:48, 4 July 2026 (UTC)[reply]
Extended content
Group1: accounts that have not yet been blocked and require investigation:
Group2: Accounts that have already been investigated:
Group3: Accounts that have already been blocked by Duck:
Group 4: Accounts that have already been infinitely blocked by reasons that are not related to sockpuppeting and have not yet been investigated:
Taiwanese Elephant🐘(talk|contribs) 17:39, 4 July 2026 (UTC)[reply]
@Sotiale: See above. Many thanks to @臺灣象象:. Seems like I missed a few of them in my prior comment. )dt 19:41, 4 July 2026 (UTC)[reply]
I'm just going to start a table below it's so large. This is In progress… and will take a few rounds to go through. Please be patient with us. -- Amanda (she/her) 23:40, 5 July 2026 (UTC)[reply]
Extended content
User Group Status Comment
DEbopexe
Toby Amelia Group 1 Likely Likely
Kjklj Group 1  Confirmed
Hjgjkhj Group 1  Confirmed Not part of original list
Venice90
KellyReiff Group 1  Confirmed
NellumHeading Group 1 Likely Likely
Harrisonpatricia
Memaji Group 1  Confirmed
Hungquan1 Group 1  Confirmed
FitchPepys
Xinx19
BoaSimple Group 1 Likely Likely
Regannnick
Alsafa365 Group 1  Confirmed
Trevelyany
CQCOYY Group 1  Confirmed
Jcmnaeit Group 1
Roxanne Godwin
Frisonnit
EginaldTrosin946885 Group 1 Likely Likely
Gsgarzo
Midasbaldo356 Group 1 Likely Likely
Tomas anderin
WadeRussell
Captain Jack Lee
Msdwqb
神笔可乐 Group 1  Confirmed
Kknksnfd
Yiberifowuti
刘巴伦
Kucmanet
香蕉凤梨酥
Alfgaws
Chris5655
Deirdremoss
为世界做贡献
Dayanalarso396
Godshur
Qwrqfeq
Edumde
Wrightpnabi
Allenweaker
Jucklee1111
Doubeer
Ruth Evan Group 1  Confirmed Not part of original list
Scldbf Group 1 Possible Possible Not part of original list
大奇琪 Group 1 Likely Likely Not part of original list
Constancace Group 1  Confirmed Not part of original list
Sendsendsend Group 1  Confirmed Not part of original list
Minelog Group 1 Possible Possible Not part of original list
化高兴 Group 1 Likely Likely Not part of original list
Wuntaerm Group 1 Possible Possible Not part of original list
@Hamish and ATannedBurger: I went and assisted with finding my own evidence, as this was a massive list, and I understand the undertaking it is. The problem is, I got through what is the bulk of the farm with Group 1, and the rest is not easily coming together for me. So my compromise here, is to ask you to grab a few more (~4 accounts) of the most prolific ones that I haven't checked yet, show me the evidence for those high edit accounts, which are likely to yield the most in CU, and I can look at that. I definitely think you have a bot farm or a UPE editing farm going on, but the extent and connections are very blurry now after dealing with group 1. -- Amanda (she/her) 01:29, 7 July 2026 (UTC)[reply]
Hi, I've been caught in the middle of some real life stuff recently, will soon respond. Hamish one great show can change the world 03:21, 10 July 2026 (UTC)[reply]
Hi, I personally would prefer to run check on Venice90, FitchPepys, Trevelyany, WadeRussell. Although their editing patterns aren't identical, I strongly suspect they are operated by the same person,, main common behaviour is original research. Details:
  1. Venice90 is on the same VPN range and starts to edit articles with regard to Inner Mongolia, then they do newcomers tasks to reach 50 contributions (to gain AC?) and soon stopped. [1]
  2. FitchPepys initials account with editing to Xinjiang, Tibet, and copyvio. [2]
  3. Trevelyany edits Xinjiang related articles and did copyvio as well. Their reply to SPI and edit summary (compared to [3]) share noticeable stylistic similarity.
  4. WadeRussell introduced copyvio and have a similar writing style like confirmed socks, edits Xinjiang related articles.
Thank you in advance. Hamish one great show can change the world 22:07, 10 July 2026 (UTC)[reply]

Sayaanakmalaysia92@ms.wikipedia

[edit]
V92 has been locked for 11 months, there would be no checkuser data to compare, What do you want us to compare? — xaosflux Talk 15:15, 8 July 2026 (UTC)[reply]
Is there any other ways to check whether Sayaanakmalaysia92 is block evading the Visnu92? Hakimi97 (talk) 16:01, 9 July 2026 (UTC)[reply]
The primarily based on behavioural evidence suggesting possible block evasion. Sayaanakmalaysia92 appears to show editing patterns similar to Visnu92, including a strong focus on India- and Tamil-related articles, adding Tamil script to articles not specifically related to Tamil Nadu or the Tamil language, and removing Chinese-language or China-related content from various articles.
The discussion page contains diffs showing these similarities between the two accounts. Since a technical CheckUser comparison is no longer possible, could you please advise whether the behavioural evidence can be reviewed for possible block evasion, or whether there is another appropriate process for handling this case?
Thank you. Foryou42686 (talk) 05:41, 10 July 2026 (UTC)[reply]
mswiki has active local admins that can review user conduct/behavior. Is there anything else requiring technical steward action here? — xaosflux Talk 15:33, 10 July 2026 (UTC)[reply]
Okay then, if nothing could be done here, please close this request as it is currently hard to take any further actions here. Hakimi97 (talk) 14:11, 11 July 2026 (UTC)[reply]

Ss993d@eu.wikipedia

[edit]

See also

[edit]