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]

Salah1933

[edit]

Status: resolved • view • edit • history • watch
Filed: 00:00, 24 February 2026 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: Salah1933 was blocked for 3 days for uploading copyvios and removing DR templates. A few hours after the block, HidemoshiNobita was created and began uploading the exact same copyvios at the exact same titles as Salah1933. See Special:Log/HidemoshiNobita and the recreated files: File:Norman Powell Miami Heat.jpg, File:Andrew Wiggins Miami Heat.jpg, File:Kasparas Jakučionis Miami Heat.jpg, and File:Pelle Larsson Miami Heat.jpg. Also, both accounts edited from mobile web. HurricaneZetaC 00:00, 24 February 2026 (UTC)[reply]

Results: Confirmed

All blocked and tagged. --Lymantria (talk) 06:47, 24 February 2026 (UTC)[reply]

Universalnews23

[edit]

Status: resolved • view • edit • history • watch
Filed: 05:17, 22 February 2026 (UTC)

[edit]

Omphalographer (talk) 05:17, 22 February 2026 (UTC)[reply]

Rationale, discussion and results

[edit]

Results: Confirmed or very Likely:

Blocked and tagged. @Omphalographer: Please, next time include a rationale. In this case it was clear that the MO was the same as in the previous request, but please, explain. --Lymantria (talk) 07:54, 22 February 2026 (UTC)[reply]

Will do. First time I've had to relist a RFCU; wasn't sure how much of the original listing needed to be repeated. Omphalographer (talk) 08:21, 22 February 2026 (UTC)[reply]
Thanks in advance. --Lymantria (talk) 22:05, 23 February 2026 (UTC)[reply]

Same behavioral pattern on:

Omphalographer (talk) 22:42, 23 February 2026 (UTC)[reply]

All Confirmed to earlier socks. No sleepers found. Blocked and tagged. --Lymantria (talk) 06:22, 24 February 2026 (UTC)[reply]

Ignacy743

[edit]

Status: resolved • view • edit • history • watch
Filed: 21:02, 21 February 2026 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: Użytkownicy ci ładują na Commons grafiki przedstawiające niewolne awatary. Wawrzec (nowe konto) (talk) 21:02, 21 February 2026 (UTC)[reply]

Declined Despite one upload of a similar copyvio by Trovggfd, the behaviour of Trovggfd and Ignacy743 does not show enough similarity to allow the use of checkuser tools. --Lymantria (talk) 07:37, 22 February 2026 (UTC)[reply]

ScientiaMonde

[edit]

Status: resolved • view • edit • history • watch
Filed: 13:02, 21 February 2026 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: These users are listed as vandals and sockpuppets on various projects, and they remove banners from files here. Examples: 1, 2 —Eihel (talk) 13:02, 21 February 2026 (UTC)[reply]

Results: Confirmed:

Eikyoupix is Stale, but already confirmed to Group 2 at other projects and globally locked. Moving case to ScientiaMonde as oldest account. Blocking and tagging. --Lymantria (talk) 21:12, 21 February 2026 (UTC)[reply]

Hanmediawk

[edit]

Status: resolved • view • edit • history • watch
Filed: 02:31, 21 February 2026 (UTC)


[edit]

Rationale, discussion and results

[edit]

Reason: These accounts have the same editing pattern as Hanmediawk: uploading images that contain gambling links in the description, including copyrighted files such as File:The pear tree blooms white in Moc Chau.jpg. Cherry Cotton Candy (talk) 03:19, 21 February 2026 (UTC)[reply]

Confirmed Conco12345 = Conco123456.
Inconclusive Conco1221.
All blocked. --Krd 06:07, 21 February 2026 (UTC)[reply]


Slowking4

[edit]

Status: resolved • view • edit • history • watch
Filed: 12:42, 19 February 2026 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: This user has exactly the same pattern of uploads as Slowking4: dumping a huge number of small duplicate artworks with improper information and license. Yann (talk) 12:42, 19 February 2026 (UTC)[reply]

Hochithecreator did not make many recent edits. From the available CU data I conclude however that they are Unrelated or at least Unlikely to be related to Slowking4. --Lymantria (talk) 14:48, 19 February 2026 (UTC)[reply]
OK, thanks. However the similarities are striking. I will talk with Hochithecreator, and see that they correct their uploads, and avoid doing it again. Yann (talk) 10:38, 21 February 2026 (UTC)[reply]


Worvandae

[edit]

Status: resolved • view • edit • history • watch
Filed: 03:40, 19 February 2026 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: This new account has uploaded photos from Yen Hoa Park, Hanoi and edited old photos of sockpuppets Worvandae and Suulabe258. It is very likely a sock as well. ~2026-11204-05 (talk) 03:40, 19 February 2026 (UTC)[reply]

Confirmed to each other and to Worvandae:
Blocked and tagged. --Lymantria (talk) 07:39, 19 February 2026 (UTC)[reply]

Ikaoch

[edit]

Status: resolved • view • edit • history • watch
Filed: 15:21, 9 February 2026 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: There's a possibility that one or more people are working and uploading promotional content for a Japanese band. These two accounts have been uploading content unsuitable for use on Commons for use on the English and Spanish Wikipedias; all of this material has been removed. It's worth noting that there's another suspicious account editing on the English and Spanish Wikipedias but not on Commons, doing something similar. The suspected account was blocked on the Spanish Wikipedia, and an attempt was made to verify the connection, but it's not entirely conclusive, although the editing pattern doesn't rule out the possibility that it's the same person. Now I'm looking here to see if there's a connection to Ikaoch. Taichi (talk) 15:21, 9 February 2026 (UTC)[reply]

Declined Ikaoch is stale, and you only listed one suspected sock with activity on Commons, so a CheckUser check would be unlikely to provide useful data. The Squirrel Conspiracy (talk) 17:21, 9 February 2026 (UTC)[reply]
You may be able to get some useful information from the Stewards checking loginwiki though. The Squirrel Conspiracy (talk) 17:23, 9 February 2026 (UTC)[reply]

DJRubinitoYtxd

[edit]

Status:  to be archived • view • edit • history • watch
Filed: 22:34, 8 February 2026 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: After the previous accounts were blocked, this account started uploading more similar images about the Comerciantes Unidos club of Peru. --Ovruni (talk) 22:34, 8 February 2026 (UTC)[reply]

Confirmed Blocked and tagged. --Lymantria (talk) 06:26, 9 February 2026 (UTC)[reply]
Please see Commons:Deletion requests/Files uploaded by CulturaNacional. Yann (talk) 08:56, 9 February 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=1171023396"