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]

Democfest

[edit]

Status: open • view • edit • history • watch
Filed: 14:35, 10 April 2026 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: All of these have already been confirmed as socks on enwiki, and have been active on Commons. Requesting a CU block of these accounts. CutlassCiera 14:35, 10 April 2026 (UTC)[reply]

+1. Exact same cropping style. Mirroring same behaviour. I  Strong support these accounts being indeffed for sockpuppeting. LuvsMG481 (talk) 14:53, 10 April 2026 (UTC)[reply]

Josefo Ludovico

[edit]

Status: open • view • edit • history • watch
Filed: 02:46, 10 April 2026 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: They upload the same type of files, using the date and time of the photograph as the title. It's currently in the verification queue on the Spanish Wikipedia, but due to the urgency, I request that it be check here, considering it has already created sockpuppets here. Taichi (talk) 02:46, 10 April 2026 (UTC)[reply]

Results: These data are not easy to judge, consider these as preliminary results:

Confirmed to each other and Likely to this case
Likely to each other and to the case:
Blocked and tagged. I cannot dive deeper into this case today, probably in the weekend. Other CUs: feel free to step in. --Lymantria (talk) 05:51, 10 April 2026 (UTC)[reply]

Trantrongnam~conmonswiki

[edit]

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

[edit]

Rationale, discussion and results

[edit]

Reason: similar username and modus operandi. M.Bitton (talk) 15:22, 9 April 2026 (UTC)[reply]

Results: Confirmed to earlier socks:

Blocked and tagged. --Lymantria (talk) 05:17, 10 April 2026 (UTC)[reply]

Emanuel Sefullahu

[edit]

Status: resolved • view • edit • history • watch
Filed: 03:33, 8 April 2026 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: Cross-wiki promotion for the same person. Regards, ZI Jony (Talk) 03:33, 8 April 2026 (UTC)[reply]

Results: Confirmed:

Blocked and tagged. These results appear to be equal to those at enwiki. --Lymantria (talk) 05:46, 8 April 2026 (UTC)[reply]

@Lymantria, thanks for quick response, and take action on Wikidata as well. Regards, ZI Jony (Talk) 05:59, 8 April 2026 (UTC)[reply]

Rishabam4

[edit]

Status: resolved • view • edit • history • watch
Filed: 12:03, 7 April 2026 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: Copyvio supporting UPE, potential sockpuppetry. Please see en:Wikipedia:Sockpuppet investigations/Rishabam4 for details and check for sleepers.   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 12:03, 7 April 2026 (UTC)[reply]

Rakshita24 is not registered here. Rishabam4 does not yield sleepers. I see that enwiki CU has confirmed socking. No comment on IPs. --Lymantria (talk) 16:35, 7 April 2026 (UTC)[reply]
@Lymantria: Thank you. Done for me.   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 18:14, 7 April 2026 (UTC)[reply]

DJ Mixify FUL

[edit]

Status:  to be archived • view • edit • history • watch
Filed: 19:36, 2 April 2026 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: same pattern (re-creating the category and uploading a file), might be other accounts as well. Bencemac (talk) 19:36, 2 April 2026 (UTC)[reply]

 It looks like a duck to me, IAmJollie tagged, was already locked. --Lymantria (talk) 06:07, 3 April 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=1194911049"