Commons:Requests for checkuser/Case

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.

nothing found

Requests

Drella8566

Rationale, discussion and results

Reason: Reuploaded File:Garry Apgar.jpg. - Alexis Jazz ping plz 18:11, 6 June 2026 (UTC)

Dummy Bhaava

Rationale, discussion and results

Reason: Repeatedly reupload pictures, which are copyright violations, of the same person: Joseph Vijay, Chief Minister of Tamil Nadu. Please check for sleepers, and if possible, block the IP/range. Yann (talk) 15:45, 6 June 2026 (UTC)

Inconclusive --Krd 16:07, 6 June 2026 (UTC)

Elektrogurke

Rationale, discussion and results

Reason: Compare de:Wikipedia:Checkuser/Anfragen/Elektrogurke and Commons:Requests for checkuser/Case/Xocolatl, suspected Sockpuppets of Xocolatl et al. NDG (talk) 14:28, 6 June 2026 (UTC)

What is the abuse part you want to protect Commons from? I see the three accounts have been confirmed at dewiki, we would accept that outcome here as well. But I fail to see the reason to block any of them here. --Lymantria (talk) 20:34, 6 June 2026 (UTC)

Hoanghung150814

Rationale, discussion and results

Reason: attached Commons account today just to agree with Subeosack on Commons:Deletion requests/Files uploaded by Subeosack. Indeffed on viwiki 1 year ago for socking. (indef comment: "Rối", see w:vi:WP:Rối) - Alexis Jazz ping plz 14:57, 2 June 2026 (UTC)

Results: Confirmed:

A clear example of vote stacking. Hoanghung150814 is the oldest account and is blocked at viwiki for socking as well. Blocked and tagged. --Lymantria (talk) 17:30, 2 June 2026 (UTC)

NotLessOrEqual

Rationale, discussion and results

Reason: The four accounts listed have been blocked on behavioral evidence, I'm requesting a sweep for other/sleeper accounts per Commons:Administrators' noticeboard/Blocks and protections/Archive 43#More NotLessOrEqual socks. This is an LTA who uses a lot of single-upload sock accounts to add images, some copyrighted or AI-altered with false descriptions, later using other burner accounts and/or TAs to add the images to Wikipedia. Back in March we blocked thirty such sock accounts. Belbury (talk) 16:14, 1 June 2026 (UTC)

The following sleepers I found as Likely or better:
Blocked and tagged. --Lymantria (talk) 21:03, 1 June 2026 (UTC)

Need Reqer

Rationale, discussion and results

Reason: Suspected lock evasion: Same kind of kid-like trolling. --Achim55 (talk) 21:10, 31 May 2026 (UTC)

Confirmed together with
Blocked (if not already) and tagged. --Lymantria (talk) 05:39, 1 June 2026 (UTC)

Hfhtdjf

Rationale, discussion and results

Reason: As first edits, Whatjapeenedtoyou removed 3 deletion requests from files uploaded by Hfhtdjf. New account created after Hfhtdjf block. Similar interests. Also tests/nonsense edits like . Yann (talk) 18:59, 22 May 2026 (UTC)

This seems obvious from the first edits by Whatjapeenedtoyou, but from CU data I just can say it is Possible. Meatpuppetry more likely. --Lymantria (talk) 20:09, 23 May 2026 (UTC)
OK, blocked. Yann (talk) 17:18, 26 May 2026 (UTC)
@Lymantria: A new account came up today. Yann (talk) 22:09, 30 May 2026 (UTC)
@Yann: do you have an account name? --Lymantria (talk) 07:03, 31 May 2026 (UTC)
@Lymantria: I added it above: Hfthdjf. Yann (talk) 10:39, 31 May 2026 (UTC)
Same conclusion as previous one: Possible. --Lymantria (talk) 15:21, 31 May 2026 (UTC)
 Info Whatjapeenedtoyou has made proxying attempts at enwiki. HyperAnd [talk] 23:26, 31 May 2026 (UTC)
Noted. --Lymantria (talk) 10:38, 1 June 2026 (UTC)
For the record, all 3 accounts are now globally locked. Yann (talk) 13:08, 1 June 2026 (UTC)
Yann: You're welcome.   — 🇺🇦Jeff G. please ping or talk to me🇺🇦 14:20, 1 June 2026 (UTC)

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