Jump to content

Commons:Requests for checkuser

From Wikimedia Commons, the free media repository

Shortcuts: COM:CHECK • COM:RFCU • COM:SOCK

This is the place to request investigations of abuse of multiple accounts or of other circumstances that require use of checkuser privileges.

Requesting a check

These indicators are used by CheckUsers to allow easier at-a-glance reading of their notes, actions and comments.
Request completed
Confirmed  Technically indistinguishable
Likely  Possilikely
Possible Unlikely
Inconclusive Unrelated
 No action Stale
Request declined
Declined Checkuser is not for fishing
Checkuser is not magic pixie dust. 8ball The CheckUser Magic 8-Ball says
 It looks like a duck to me Checkuser is not a crystal ball.
Information
Additional information needed Deferred to
 Doing…  Info

Please do not ask us to run checks without good reason; be aware of the following before requesting a check:

  1. Checkuser is a last resort for difficult cases; pursue other options first, such as posting on the administrator's noticeboard. (This is not a venue for requesting administrative action such as blocks or file clean-up.)
  2. Running a check will only be done to combat disruption on Commons, or as required to assist checkuser investigations on other Wikimedia wikis.
    • Valid reasons for running a check include, for example: vandalism where a block of the underlying IP or IP range is needed and suspected block evasion, vote-stacking, or other disruption where technical evidence would prevent or reduce further disruption.
    • Requests to check accounts already confirmed on other projects may be declined as redundant.
    • Requests to run a check on yourself will be declined.
  3. Evidence is required. When you request a check, you must include a rationale that demonstrates (e.g., by including diffs) what the disruption to the project is, and why you believe the accounts are related.
    • Requests to run a check without evidence or with ambiguous reasoning will result in delays or the request not being investigated.
  4. The privacy policy does not allow us to make a check that has the effect of revealing IP addresses.

Outcome

Responses will be brief in order to comply with Wikimedia privacy policy. Due to technical limitations, results are not always clear. Closed requests are archived after seven days.

Privacy concerns

If you feel that a checkuser request has led to a violation of the Wikimedia Foundation privacy policy regarding yourself, please refer the case to the Ombuds commission.

If this page is displaying outdated contents even after you refresh the page in your browser, please purge this page's cache.

To request a check:

Cases are created on subpages of Commons:Requests for checkuser/Case.

Creating a request
  • Insert the name of the suspected sockpuppeteer (the main account or puppetmaster, not the sockpuppet!) in the box below, leaving out the "User:" prefix. Do not remove the text in the box, add to the end only.
  • Please explain/justify the request by saying what it is you suspect and why it is important that the check be carried out. Indicate the usernames you suspect, using {{checkuser}}. Please do not use this template in the section header, as that makes it difficult to read the account names. Include the diffs or links required to support the request and reason for it.
  • There are people to assist you and help with maintenance of the page. Just ask for help on the admin noticeboard if you really are stuck, or take your best shot and note that you weren't completely sure of what to say.
  • If a case subpage already exists, edit the existing page instead, either adding to the currently open section (if the case is not yet archived) or adding a new section to the top using {{subst:Commons:Requests for checkuser/Inputbox/Sample}} (if the case has been archived). When editing an existing case, be sure to list/transclude the subpage here.
Example
If you want to request a checkuser on User:John Doe, enter the text Commons:Requests for checkuser/Case/John Doe then click "Request a checkuser". You will be taken to a page where you can fill out the request. Please make your request there brief and concise.


Then transclude your subpage on the top of the list at Commons:Requests for checkuser and remove {{Checkuser requests to be listed}} from the top of the case subpage.

Checkuser requests to be listed (empty)
nothing found

Requests

[edit]

Trantrongnam~conmonswiki

[edit]

Status: resolved • view • edit • history • watch
Filed: 14:03, 27 March 2026 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: An obvious sock of Trantrongnam~conmonswiki (similar username to Skibididopdop~commonswiki). Please compare VNM_EST.1976's contributions to theirs. M.Bitton (talk) 14:03, 27 March 2026 (UTC)[reply]

Results: Confirmed to each other:

Based on behaviour, I judge these as Likely to this case. Blocked and tagged. --Lymantria (talk) 13:48, 28 March 2026 (UTC)[reply]

Yensid98

[edit]

Status: resolved • view • edit • history • watch
Filed: 15:19, 27 March 2026 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: All four accounts uploaded and inserted self-made drawings into articles about Vietnamese historical figures on wiki projects. 3 out of 4 accounts above contain "SỬ" in their usernames. Kim Nito (talk) 15:19, 27 March 2026 (UTC)[reply]

  • Confirmed YÊU SỬ VIỆT NAM = Lịch Sử Hisory
  • Likely LỊCH SỬ VIỆT NAM VÀ THẾ GIỚI = the above two
  • Inconclusive that any of them are Yensid98

Blocking and tagging the three that are connected. The Squirrel Conspiracy (talk) 17:27, 27 March 2026 (UTC)}[reply]

Jordanene7

[edit]

Status: resolved • view • edit • history • watch
Filed: 13:14, 27 March 2026 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: Highly similar user name to their other sockpuppet accounts. 痛Designism (talk) 13:14, 27 March 2026 (UTC)[reply]

 It looks like a duck to me Blocked and tagged. --Lymantria (talk) 16:51, 27 March 2026 (UTC)[reply]

Worvandae

[edit]

Status:  to be archived • view • edit • history • watch
Filed: 08:04, 25 March 2026 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: The new account has the same behavior as Worvandae and manually reverts at [1]. Thank you. --Henry (dat) 08:04, 25 March 2026 (UTC)[reply]

Results: Already done:

Confirmed:

Likely:

Blocked and tagged. --Lymantria (talk) 17:56, 25 March 2026 (UTC)[reply]

Zjholder

[edit]

Status: resolved • view • edit • history • watch
Filed: 04:21, 25 March 2026 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: vandal/nastiness accounts with same modus operandi: including that both vandalized File:January 2025 Official Vice Presidential Portrait of JD Vance.jpg , then vandalized Commons:Administrators' noticeboard/Vandalism identically once reported.

What I'd like to do here is form the basis for an IP range block, if possible; I don't know under current rules if CU will be any use, because I gather that we no longer can discuss the particular IPs associated with particular accounts. If there is no imaginable way to get from conclusions drawn here to an IP range block, then don't even bother. Jmabel ! talk 04:21, 25 March 2026 (UTC)[reply]

I found Confirmed:
and very Likely to these
All these accounts are already blocked and/or globally locked. They use different IPs in several ranges and those are taken care of (often by the stewards). I'll move the case to Jamesond88 and tag accordingly. --Lymantria (talk) 07:50, 25 March 2026 (UTC)[reply]
P.S. @Jmabel Checkusers cannot discuss IPs, IP ranges or temporary accounts in public. That does not mean they don't take measures like (requesting global) range blocks. --Lymantria (talk) 14:29, 25 March 2026 (UTC)[reply]
@Lymantria: Thanks, but I'd like to add Imu Nerona (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log), who just vandalized this page.   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 17:06, 28 March 2026 (UTC)[reply]
Just so you know, the accounts are actually made by Zjholder, who is an LTA (long-term abuser) and does CWA (cross-wiki abuse) with his disruptive edits. NX3710 (talk) 00:48, 29 March 2026 (UTC)[reply]
Imu Nerona is Confirmed to these accounts. Thank you, NX3710, for pointing to Zjholder. From data I have seen, I can confirm this case to Zjholder. Will move this case and retag socks. --Lymantria (talk) 07:23, 29 March 2026 (UTC)[reply]

Jorse García

[edit]

Status:  to be archived • view • edit • history • watch
Filed: 18:37, 24 March 2026 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: Constant uploading of movie logos under a fake public domain license, similar to the behavior of the LTA. He has already received numerous warnings and continues to upload logos without any problems. Taichi (talk) 18:37, 24 March 2026 (UTC)[reply]

Using that Govemeki has been identified as sock at eswiki, I still cannot say more than Possible. --Lymantria (talk) 07:41, 26 March 2026 (UTC)[reply]

Mongies

[edit]

Status:  to be archived • view • edit • history • watch
Filed: 03:23, 21 March 2026 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: Same area of interest. Screenshots of singers interviewed on radio stations. Created Sarah Toscano articles crosswiki.--Titore (talk) 03:23, 21 March 2026 (UTC)[reply]

Likely Blocked and tagged. --Lymantria (talk) 21:31, 21 March 2026 (UTC)[reply]

Mongies

[edit]

Status:  to be archived • view • edit • history • watch
Filed: 18:58, 14 March 2026 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: Fresui re-uploaded a non free picture of Sarah Toscano with the microphone edited out (File:Sarah Toscano (June 2025).jpg, cf. the previous request below). The picture was imported from Flickr with a forged CC-BY license, and promptly deleted on Flickr after it was speedly deleted on Commons. Please check for sleepers. --Titore (talk) 18:58, 14 March 2026 (UTC)[reply]

OswaldLR just added Verupo and Jamopre, who imported pictures from the same Flickr account.--Titore (talk) 01:23, 15 March 2026 (UTC)[reply]

Results: From CU data I have: Stale:

Likely to each other and Possible to this case:

Possible to this case:

Combined with behavioural data I'll block and tag them as suspected socks. --Lymantria (talk) 08:11, 15 March 2026 (UTC)[reply]

Mongies

[edit]

Status:  to be archived • view • edit • history • watch
Filed: 03:23, 21 March 2026 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: Same area of interest. Screenshots of singers interviewed on radio stations. Created Sarah Toscano articles crosswiki.--Titore (talk) 03:23, 21 March 2026 (UTC)[reply]

Likely Blocked and tagged. --Lymantria (talk) 21:31, 21 March 2026 (UTC)[reply]

Mongies

[edit]

Status:  to be archived • view • edit • history • watch
Filed: 18:58, 14 March 2026 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: Fresui re-uploaded a non free picture of Sarah Toscano with the microphone edited out (File:Sarah Toscano (June 2025).jpg, cf. the previous request below). The picture was imported from Flickr with a forged CC-BY license, and promptly deleted on Flickr after it was speedly deleted on Commons. Please check for sleepers. --Titore (talk) 18:58, 14 March 2026 (UTC)[reply]

OswaldLR just added Verupo and Jamopre, who imported pictures from the same Flickr account.--Titore (talk) 01:23, 15 March 2026 (UTC)[reply]

Results: From CU data I have: Stale:

Likely to each other and Possible to this case:

Possible to this case:

Combined with behavioural data I'll block and tag them as suspected socks. --Lymantria (talk) 08:11, 15 March 2026 (UTC)[reply]

For older requests, please see Commons:Requests for checkuser/Archives
Retrieved from "https://commons.wikimedia.org/w/index.php?title=Commons:Requests_for_checkuser&oldid=1188656722"