Commons:Requests for checkuser

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.

Category:Sockpuppet investigations#Requests%20for%20checkuser

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.
Transcluding the request
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.

Checkuser requests to be listed (empty)
nothing found

Requests

Mellmot

Status: resolved • view • edit • history • watch
Filed: 12:37, 15 July 2026 (UTC)

Rationale, discussion and results

Reason: Mellmot had many of their files deleted recently. After deletion, many new accounts were created to upload images under those exact same file names. – Pbrks (t • c) 12:37, 15 July 2026 (UTC)

Results: Confirmed to master:

Blocked and tagged. --Lymantria (talk) 06:13, 16 July 2026 (UTC)

Solomon203

Status: resolved • view • edit • history • watch
Filed: 20:36, 14 July 2026 (UTC)

Rationale, discussion and results

Reason: Both uploaded images from the same non-public Flickr account, Bryan Treiber), hours apart (File:Mimi wearing bikini at Clearwater Beach (2149990804).jpg & File:Mimi wearing bikini at Clearwater Beach (2144946112).jpg for Solomon203 and File:Vanessa 08.jpg & File:Amelie 2 Dec 2008.jpg for Ilia Kulunov I as examples). Solomon203 also went into at least three of the photos uploaded by Ilia Kulunov I to add categories (File:Model Mija South Beach Miami 2007.jpg was the first one that I saw it on). I only found these cases by looking at Category:Flickr images not found. This makes me think this is a sockpuppet (especially with the duck test), even if it is an innocent one. Elisfkc (talk) 20:36, 14 July 2026 (UTC)

Interaction Timeline shows six files with edits from both in 2026. Elisfkc (talk) 21:03, 14 July 2026 (UTC)
As long as there is no abuse, there is not point in investigating here. --Lymantria (talk) 07:49, 15 July 2026 (UTC)
Fair enough. I was on the fence about it, but figured sockpuppeting still is an issue. Elisfkc (talk) 02:51, 18 July 2026 (UTC)

Firstclassidiot123

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

Rationale, discussion and results

Reason: User seems to be Commons:NOTHERE, since their main activity seems now to be reverting CoA files to previous versions, which happenned twice (June 25th, July 9th) without any valid reason, nor even bothering to answer a simple question.
This behaviour, as well as the user's registration period (January 2026), is very similar to IW0A-P7’s who also reverts files to bad revisions (example file, among others), and very similar to StyraCDF’s, who also reverts files to wrong revisions (example file, among others).
Certain marginal contributions which may be intended to give the impression of participation can, in my view, hardly conceal a presence whose sole aim is to cause disruption, especially as the last two cited accounts have already been blocked on simple.wiki for being sockpuppets of Massiota, who, by the way, is quoted here only for information purposes, despite problematic file reversions too (example file). Kontributor 2K (talk) 16:19, 12 July 2026 (UTC)

Results: Firstclassidiot123 is Unrelated to the other users. Based on technical data the connection between StyraCDF and IW0A-P7 is at best Possible, but there is a strong behavioral connection. I see no direct reason to block. No action taken. --Lymantria (talk) 06:07, 13 July 2026 (UTC)

For older requests, please see Commons:Requests for checkuser/Archives
Category:Sockpuppet investigations