Commons:RCU

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.
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.

Requests

Anogenyogan5

Status: open • view • edit • history • watch
Filed: 08:04, 20 June 2025 (UTC)

Rationale, discussion and results

Reason: LTA with uploading copyright violations to nominate them for deletion immediately after uploading. GPSLeo (talk) 08:04, 20 June 2025 (UTC)

Foryejileader0526

Status: open • view • edit • history • watch
Filed: 03:25, 20 June 2025 (UTC)

Rationale, discussion and results

Reason: Obvious DUCK. Re-uploading deleted materials. Related user was already blocked for abusing multiple accounts hence I believe that the sockmaster's username is another which I'm not sure which since the block log doesn't state such on Commons. — Paper9oll (🔔 • 📝) 03:25, 20 June 2025 (UTC)

Baginda 480

Status: resolved • view • edit • history • watch
Filed: 15:15, 18 June 2025 (UTC)

Rationale, discussion and results

Reason: Like uploading images related to Mahathir Mohamad, but some of them were out of scope or falsely licensed. A1Cafel (talk) 15:15, 18 June 2025 (UTC)

Results: Confirmed Baginda 480 = BujangLapok05. --Lymantria (talk) 19:21, 18 June 2025 (UTC)

Liaaaapple

Status: resolved • view • edit • history • watch
Filed: 07:47, 18 June 2025 (UTC)

Rationale, discussion and results

Reason: All users uploaded photos of girl group Itzy's member Lia falsely claiming they were own works. They follow the same pattern with naming conventions and may be linked to another bunch of users who has been uploading copyrighted photos of K-pop girl groups for around 6 months, some of which were already object of check-user requests. Chiyako92 (talk) 07:47, 18 June 2025 (UTC)

Inconclusive --Krd 16:56, 18 June 2025 (UTC)

DJ Mixify FUL

Status: resolved • view • edit • history • watch
Filed: 17:33, 14 June 2025 (UTC)

Rationale, discussion and results

Reason: LTA, re-uploading File:DJ Parisa.jpg for io:DJ_Parisa. Bencemac (talk) 17:33, 14 June 2025 (UTC)

Declined / ✓ Done anyways Based on the cadence of socks, I don't think running a CU would be useful. However, we can block and tag based on behavioral evidence, which I've done. The Squirrel Conspiracy (talk) 04:06, 15 June 2025 (UTC)

Amitsharma009

Status: resolved • view • edit • history • watch
Filed: 11:33, 14 June 2025 (UTC)

Rationale, discussion and results

Reason: All recently created accounts uploading a few files for advertisements in India. Also similar usernames (one word + numbers), and similar named files. Already blocked, but please check for sleepers and, if possible, block the range. Yann (talk) 11:33, 14 June 2025 (UTC)

Results: I come to Confirmed or very Likely to each other:

Blocking and tagging. --Lymantria (talk) 12:49, 14 June 2025 (UTC)

The accounts are globally locked. 〈興華街〉📅❓ 03:08, 16 June 2025 (UTC)
Thank you. --Lymantria (talk) 05:18, 16 June 2025 (UTC)

Jordanene7

Status: resolved • view • edit • history • watch
Filed: 08:56, 14 June 2025 (UTC)

Rationale, discussion and results

Reason: Both users were reported at COM:RFPP. TyraFan638 was blocked right away, then FamilyFan633 appeared shortly after that. I think it is good to check for sleepers. Lymantria (talk) 08:56, 14 June 2025 (UTC)

Results: Confirmed:

Most of them have already been locked and/or identified at en:Wikipedia:Sockpuppet investigations/Jordanene7. Tagging. Blocking and requesting global lock if necessary. --Lymantria (talk) 09:10, 14 June 2025 (UTC)

Vladimir Nimčević

Status: resolved • view • edit • history • watch
Filed: 05:41, 12 June 2025 (UTC)

Rationale, discussion and results

Reason: Per Commons:Administrators' noticeboard/Vandalism, it may be a good opportunity to check here on Commons for more socks of this LTA before any socks are being reported into COM:ANV. 〈興華街〉📅❓ 05:41, 12 June 2025 (UTC)

+3. 〈興華街〉📅❓ 04:38, 13 June 2025 (UTC)
Some are possibly related to others, For the whole group, I'd call this Inconclusive for the moment. Please report further occurences. --Krd 08:00, 14 June 2025 (UTC)

서울출장

Status: open • view • edit • history • watch
Filed: 23:08, 31 May 2025 (UTC)

Rationale, discussion and results

Reason: Same picture Cyberwolf (talk) 23:08, 31 May 2025 (UTC)

Please provide the exact reason for the check. --Krd 04:06, 3 June 2025 (UTC)
I understand what Cyberwolf is saying. They're pointing at the deleted version history of File:Ujawal Jha.jpg. The Squirrel Conspiracy (talk) 11:50, 8 June 2025 (UTC)


This one is a mess. There's a huge amount of spam coming from this range, and it's difficult to tell how many humans are behind these accounts.

 It looks like the same person in the photos to me:

Likely a set:

Confirmed as a set:

Possible as part of one of these sets:

Inconclusive

  • At least a dozen other accounts in this range that have had their contribs wiped as spam already.

I've blocked UjawalJha34, Ujawal Jha A, Latifat97, and Odeyalepeter13 for abuse of multiple accounts. I'm only comfortable tagging the first two as socks of 서울출장. If a more experienced CU wants to take a look at this case themselves, I'd encourage them to do so. The Squirrel Conspiracy (talk) 11:50, 8 June 2025 (UTC)

Added Fathia 9 (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log ) to the group of Latifat97 and Odeyalepeter13. --Lymantria (talk) 11:18, 10 June 2025 (UTC)
For older requests, please see Commons:Requests for checkuser/Archives