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

JesseDegenerate

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

Rationale, discussion and results

Reason: After Jesse unsuccessfully tried to delete a perfectly OK image from Commons , while revealing in the process that they work for the person depicted in the picture , this desperate account has now appeared trying to delete every image portraying that same person. Obvious sock; duck. See also this CheckUser request on enwiki. Yacàwotçã (talk) 18:22, 17 June 2026 (UTC)

Likely Blocked Sean1493 for abusing multiple accounts. --Lymantria (talk) 05:37, 18 June 2026 (UTC)

TheBellaTwins1445

Status: resolved • view • edit • history • watch
Filed: 14:07, 16 June 2026 (UTC)

Rationale, discussion and results

This user,TheBellaTwins1445, globally blocked, is creating sockpuppets mainly to attack this project uploading copyvios, please, is possible, block his/her ip range to avoid more evasion of block evasion, Regards! --Ezarateesteban 14:04, 16 June 2026 (UTC)

@Ezarate: If you want to to fishing for a global lock evader's socks, please try another watering hole, perhaps m:srg.   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 21:46, 16 June 2026 (UTC)
@Ezarate You are asking for common practice. If there is a range that can be blocked without blocking regular users, we always take that possibility into account. But we never communicate about it and we do not reveal any information on IPs (or TAs). --Lymantria (talk) 07:13, 17 June 2026 (UTC)

Banksulselbar13

Status: resolved • view • edit • history • watch
Filed: 07:58, 14 June 2026 (UTC)

Rationale, discussion and results

Reason: In the last days, I learned about spamming attempts around an Indonesian bank. By the look and opinions of several other Wikimedians, they likely have a nefarious scamming intention. I'd like to ask the Checkuser colleagues if they can:

  • look for sleepers,
  • save technical evidence that may be used for edit filters or range blocks;

in order to fight this behaviour smoothly.
I'm using "Banksulselbarmakassar" as case name, as it's the apparent name of the bank chosen as scamming target. Vandalism evidence:

Regards, Grand-Duc (talk) 07:58, 14 June 2026 (UTC)

Results: Likely or Confirmed to each other:

Blocked and tagged.

 Possilikely to these:

There is some switching of range and device. Regards, --Lymantria (talk) 13:16, 14 June 2026 (UTC)

Kazi arifujjaman

Status: resolved • view • edit • history • watch
Filed: 12:06, 12 June 2026 (UTC)

Rationale, discussion and results

Reason: Both accounts uploaded the same photographs (Link 1 & Link 2) to two different contests. In addition, the usernames are very similar, which raises the possibility that they are operated by the same individual. Requesting a CheckUser to determine whether there is a technical connection. --Moheen (keep talking) 12:06, 12 June 2026 (UTC)

Is it forbidden to participate in different contest with the same photo? Krd 13:09, 12 June 2026 (UTC)
@Krd No. My concern is not that the same photo was submitted to different contests. Rather, the combination of the identical uploads and the very similar usernames suggests that the two accounts may be operated by the same person. -- Moheen (keep talking) 14:39, 12 June 2026 (UTC)
If that is as suspected, is it a violation? Honest question, it may perhaps be, but I actually don't see it. Krd 05:34, 13 June 2026 (UTC)
For older requests, please see Commons:Requests for checkuser/Archives
Category:Sockpuppet investigations