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]

Fabe56

[edit]

Status: resolved • view • edit • history • watch
Filed: 10:13, 19 March 2026 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: Please see evidence presented in this diff by @Gladcape2013: . Ideally they should present anything further here themselves, please. 🇵🇸‍🇺🇦 Timtrent 🇺🇦 talk to me 🇺🇦‍🇵🇸 10:13, 19 March 2026 (UTC)[reply]

Declined CU cannot reveal any information about connections between users and IP's or temporary accounts. --Lymantria (talk) 12:27, 19 March 2026 (UTC)[reply]
Hi @Lymantria,
I would like to clarify my recent activity. I have been helping @~2026-16139-88 sort images from the category Midway Journey III into Midway Journey III – birds; this is a purely collaborative effort to improve the organization.
I categorically deny the accusations of sockpuppetry. We are two different contributors working on the same set of files. I am happy to provide any necessary clarification to put these baseless insinuations to rest, as I would prefer to focus my energy back on contributing to the project.
Regards. Fabe56 (talk) 14:40, 19 March 2026 (UTC)[reply]
@Fabe56: it's not a great help putting every bird image into Category:Phoebastria immutabilis like you did e.g. here (cf my correction: different species).
@Timtrent: I'm just a long-term "anon user", and found the (imo absurd) Commons:Deletion requests/Files in Category:Midway Journey III, where you even declined to correct obvious errors yourself (which would be easy, as requester), and therefore risk deletion of hundreds of valuable files (mainly of birds). And yeah, it would have been useful to (at least once) click "oldest edits" to see when and where I've started this session (different stuff, completely unrelated to Fabe56). ~2026-16139-88 (talk) 15:07, 19 March 2026 (UTC)[reply]
Hi @~2026-16139-88, yep I have to admit I'm not good at identifying birds; I rushed through the categories trying to save them, but that was an obvious mistake. Anyway thanks a lots for your works, really amazing. Sorry to have but you into this! Fabe56 (talk) 15:19, 19 March 2026 (UTC)[reply]
As I stated, I declined the request to perform a sockpuppet investigation with CU tools. Further discussion does not belong here. --Lymantria (talk) 17:36, 19 March 2026 (UTC)[reply]

Chhanchhana zote hmar

[edit]

Status: resolved • view • edit • history • watch
Filed: 19:15, 18 March 2026 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: The first one is an obvious duck. The second account imported photos from this persons Flickr account and adds descriptions with the same pattern. GPSLeo (talk) 19:15, 18 March 2026 (UTC)[reply]

The results for Lalchhanhima zote picture vs. JM082 are Inconclusive. --Lymantria (talk) 07:14, 19 March 2026 (UTC)[reply]

Fetutxini31416

[edit]

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

[edit]

Rationale, discussion and results

[edit]

Reason: There is a possibility in these accounts uploading images taken from the Internet without indicating the source or metadata. One of the accounts (Martimero), has already his uploads deleted. They all share a common pattern: images of tennis tournaments, tennis courts, and tennis players. Taichi (talk) 19:42, 16 March 2026 (UTC)[reply]

Results: Confirmed:

Blocked and tagged. --Lymantria (talk) 21:07, 16 March 2026 (UTC)[reply]

@Taichi It might be worth opening a case at eswiki, as these socks seem to have been quite active at that project. --Lymantria (talk) 21:15, 16 March 2026 (UTC)[reply]

HollywoodActors33

[edit]

Status: resolved • view • edit • history • watch
Filed: 04:00, 15 March 2026 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: Constant uploading of movie logos and video captures on YouTube suggests it may be an LTA account known on English and Spanish Wikipedia as UsuarioFeliz33 (talk · contribs)/Arqueo Historia Maya (talk · contribs), which has already been blocked globally. I compare it with the most recently detected sockpuppet account. Taichi (talk) 04:00, 15 March 2026 (UTC)[reply]

Confirmed to each other and blocked. Tagged as suspected socks of UsuarioFeliz33. --Lymantria (talk) 21:02, 15 March 2026 (UTC)[reply]

Mongies

[edit]

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

[edit]

Rationale, discussion and results

[edit]

Reason: Fresui re-uploaded a non free picture of Sarah Toscano with the microphone edited out (File:Sarah Toscano (June 2025).jpg, cf. the previous request below). The picture was imported from Flickr with a forged CC-BY license, and promptly deleted on Flickr after it was speedly deleted on Commons. Please check for sleepers. --Titore (talk) 18:58, 14 March 2026 (UTC)[reply]

OswaldLR just added Verupo and Jamopre, who imported pictures from the same Flickr account.--Titore (talk) 01:23, 15 March 2026 (UTC)[reply]

Results: From CU data I have: Stale:

Likely to each other and Possible to this case:

Possible to this case:

Combined with behavioural data I'll block and tag them as suspected socks. --Lymantria (talk) 08:11, 15 March 2026 (UTC)[reply]

Truthfindervert

[edit]

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

[edit]

Rationale, discussion and results

[edit]

Reason: Lock evasion, Sikh-related POV edits. I think there are more accounts, please check. There is already en:Wikipedia:Sockpuppet investigations/Truthfindervert. --Achim55 (talk) 19:16, 11 March 2026 (UTC)[reply]

Results: Confirmed or very Likely to each other:

Of these at least Guesswhocanbe is Likely at enwiki to the master. All blocked and tagged. No comment on temporary accounts. --Lymantria (talk) 21:43, 11 March 2026 (UTC)[reply]

Additional suspected account:
Reason:
New account editing Sikh Empire related pages and leaving unclear comments similar to previous socks. JaydenChao (talk) 15:55, 13 March 2026 (UTC)[reply]
Confirmed Blocked and tagged. --Lymantria (talk) 16:29, 13 March 2026 (UTC)[reply]
Possible additional account:
Reason:
Account created about 10 minutes after the previous sock was confirmed and blocked.
Currently has no edits yet, but the timing seems suspicious. Mentioning here in case it becomes active. JaydenChao (talk) 16:49, 13 March 2026 (UTC)[reply]

Nv7801

[edit]

Status: resolved • view • edit • history • watch
Filed: 21:22, 3 March 2026 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: New user that is very interested in renaming files created by @HoosierMan1816: , see Special:Diff/1175218239, Special:Diff/1175217564 or Special:Diff/1175217875. The same thing they did under the account User:HoosietMan1816, Special:Diff/1013434633, back in March 2025. Presumably the latest sock from User:Nv7801 is at work here. Please also look for other possible socks. Thank you very much. זיו「Ziv」 • For love letters and other notes 21:22, 3 March 2026 (UTC)[reply]

Unrelated I am unable to connect Alohun9191 to any of Nv7801, Jurisdrew, or Crimea Republic - the three flag LTAs that are frequently confused for one another. However, that shouldn't stop you from placing a behavioral block. The Squirrel Conspiracy (talk) 23:09, 3 March 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=1183603196"