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

Carlosarevalohn

Status: resolved • view • edit • history • watch
Filed: 16:07, 7 May 2026

Rationale, discussion and results

Reason: Newly created account jumping straight into nominating a C24 Honduras file for deletion: Commons:Deletion requests/File:C24 Honduras.jpg. Nakonana (talk) 16:07, 7 May 2026 (UTC)

Results: Confirmed to Jairojimenez6 and I now judge as Likely to master:

Blocked and tagged. --Lymantria (talk) 05:28, 8 May 2026 (UTC)

Soumava2002

Status: resolved • view • edit • history • watch
Filed: 11:13, 7 May 2026 (UTC)

Rationale, discussion and results

Reason: Suspected use of multiple accounts to continue uploading non-free logos after being blocked. JaydenChao (talk) 11:13, 7 May 2026 (UTC)

Confirmed W.Debraj.M = William Debraj.M. Blocked and tagged as suspect sock of Soumava2002. --Lymantria (talk) 05:34, 8 May 2026 (UTC)

Alptugsezgin

Status: resolved • view • edit • history • watch
Filed: 04:38, 6 May 2026 (UTC)

Rationale, discussion and results

Reason: Aksaalp reuploaded a bunch of AI-generated landscapes that were originally uploaded by Alptugsezgin. See Commons:Deletion requests/Files uploaded by Aksaalp and Commons:Deletion requests/Files uploaded by Alptugsezgin. The files are the same: Special:Diff/1209223821#mw-diff-ntitle1.

Alptugsezgin had already accumulated a bunch of copyvio warnings and Aksaalp continues that trend. CU needed to determine if all these copyvio warnings should be totted up. - Alexis Jazz ping plz 04:38, 6 May 2026 (UTC)

Confirmed Blocked Aksaalp as sock. No action taken on the master. --Lymantria (talk) 05:25, 6 May 2026 (UTC)

TheBellaTwins1445

Status: resolved • view • edit • history • watch
Filed: 22:10, 4 May 2026 (UTC)

Rationale, discussion and results

Reason: Following the block of the sockmaster from the Spanish Wikipedia, a new, highly suspicious account has been detected attempting to edit the article created by the master a few months ago. I prefer to clear up any doubts, as this account has also posted a photo of a dog edited with AI. Taichi (talk) 22:10, 4 May 2026 (UTC)

Given that TheBellaTwins1445 and the locally known socks are Stale here, we can only block on behavioural evidence at eswiki... Behaviourally  It looks like a duck to me. A quick look gives Chiwisrecargada as a sleeper. Blocking and tagging on behavioural evidence. --Lymantria (talk) 10:41, 5 May 2026 (UTC)

Nv7801

Status: resolved • view • edit • history • watch
Filed: 00:10, 3 May 2026 (UTC)

Rationale, discussion and results

Reason: Same pattern of showing up, doing mass useless reverts on flag SVGs. Blocked on the DUCK principle; this is a request for sleepers.

N.B. might be also be Commons:Requests for checkuser/Case/Jurisdrew. Magog the Ogre (talk) (contribs) 00:10, 3 May 2026 (UTC)

No sleepers found, and I don't see a clear technical connection to either Nv7801 or Jurisdrew (or Crimea Republic). Now Jurisdrew/Nv7801/Crimea Republic seems to be a complex of sock- and meatpuppets, so that should not mean they are not connected. --Lymantria (talk) 07:08, 3 May 2026 (UTC)

Carlosarevalohn

Status: resolved • view • edit • history • watch
Filed: 16:07, 7 May 2026

Rationale, discussion and results

Reason: Newly created account jumping straight into nominating a C24 Honduras file for deletion: Commons:Deletion requests/File:C24 Honduras.jpg. Nakonana (talk) 16:07, 7 May 2026 (UTC)

Results: Confirmed to Jairojimenez6 and I now judge as Likely to master:

Blocked and tagged. --Lymantria (talk) 05:28, 8 May 2026 (UTC)

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