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]

Baginda 480

[edit]

Status: resolved • view • edit • history • watch
Filed: 09:42, 4 November (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: Like uploading images of former Malaysian prime minister Mahathir Mohamad. Created just two days after the previous sock was indeffed. A1Cafel (talk) 06:22, 26 October 2025 (UTC)[reply]

Confirmed, blocked and tagged. --Lymantria (talk) 21:26, 4 November 2025 (UTC)[reply]


OmarAlhamdi

[edit]

Status: resolved • view • edit • history • watch
Filed: 04:31, 4 November 2025 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: Same interest in uploading images relating to the Yemen Arab Republic, mainly its flag, and North Yemen in general, all taken from this Pinterest folder/board/collection/thing, consisting of educationally valueless AI-generated imagery and likely copyright-infringing photos.

Compare these files uploaded by Yar...:

  1. File:علم الجمهورية العربية اليمنية ، الحراك الشمالي العربي.png
  2. File:علم الجمهورية العربية اليمنية ، الحراك الشمالي اليمني.png
  3. File:علم العربية اليمنية ، الحراك الشمالي اليمني.png
  4. File:علم الجمهورية العربية اليمنية ، الحراك الشمالي.png

...with these uploaded by Omar:

  1. File:علم الجمهورية العربية اليمنية ، محافظة أب.jpg
  2. File:علم الحراك الشمالي اليمني ، الجمهورية العربية اليمنية.jpg
  3. File:علم الحراك الشمالي اليمني ، العربية اليمنية.jpg
  4. File:علم الجمهورية العربية اليمنية ، الحراك الشمالي اليمني.jpg

⎯⎯⎯ Rubýñ 🇨🇷 (scold) 04:31, 4 November 2025 (UTC)[reply]

Declined Both users are Stale, so there is nothing we can investigate. --Lymantria (talk) 21:11, 4 November 2025 (UTC)[reply]

The Southern Hemisphere

[edit]

Status: resolved • view • edit • history • watch
Filed: 16:10, 2 November 2025 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: same interest in logo of sports team, recreate the same logo (Adelaide Rams Logo.png vs. Adelaide Rams Rugby League Football Club Logo.webp) and overlapping file creation log: [1] --0x0a (talk) 16:10, 2 November 2025 (UTC)[reply]

Confirmed Blocked and tagged. --Lymantria (talk) 17:06, 2 November 2025 (UTC)[reply]

GMatteotti

[edit]

Status: resolved • view • edit • history • watch
Filed: 09:47, 1 November 2025 (UTC)

GMatteotti (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log)

[edit]

Rationale, discussion and results

[edit]

Reason: Interest in the same files, e.g. Special:History/File:Ohannés Gurekian (cropped).jpg and Special:History/File:Ohannes Gurekian.jpg were edited by their sock Puffettino. My check on itwiki returned a technical match. EDIT: they also asked for autopatrol rights (cf. this AN discussion). --Titore (talk) 09:47, 1 November 2025 (UTC)[reply]

Confirmed as the same user

Several of these were already blocked and tagged as suspected GMatteotti socks.

There are probably more socks, but to find them, I'm going to have to run another check later when I have a proper mouse and keyboard (or another CU can step in).

This is not ready to close yet. The Squirrel Conspiracy (talk) 11:07, 1 November 2025 (UTC)[reply]

 Doing… --Lymantria (talk) 18:28, 1 November 2025 (UTC)[reply]
Confirmed additionally to the above and to socks confirmed the 21st of August (a couple already blocked/tagged):
Likely:
Blocked and tagged. --Lymantria (talk) 19:20, 1 November 2025 (UTC)[reply]


James R Hawley

[edit]

Status: resolved • view • edit • history • watch
Filed: 12:51, 30 October 2025 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: Two weirdly nonsensical comments came in today on COM:Help desk: Special:Diff/1106710904/1106743255 (James R Hawley) and Special:Diff/1106758575/1106766907 (BreyDay). Individually, these edits are appearing as nothing more than a commons keyboard test. But their content is both related to some money-earning scheme and a complaint about it. Hence, if a CU demonstrates a relationship between both accounts, we're likely in the realm of multiple account abuse for the purpose of spamming. That would be an offense warranting a block, but it would have to be founded upon positive CU evidence as it's likely hard to justify without it. Regards, Grand-Duc (talk) 12:51, 30 October 2025 (UTC)[reply]

Unrelated The Squirrel Conspiracy (talk) 14:21, 30 October 2025 (UTC)[reply]

Yerbas Buenas 2024

[edit]

Status:  to be archived • view • edit • history • watch
Filed: 15:18, 27 October 2025 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: (a) similar username as previous socks. (b) same interest in uploading image for Honor X6b 5G (File:Honor X6b 5g.png vs. File:Honor X6B 5G.png) and Yerbas Buenas. (c) File recreation: [2]. — Preceding unsigned comment added by 0x0a (talk • contribs)

Results: Confirmed to 13 Oct socks:

Blocked and tagged. --Lymantria (talk) 16:15, 27 October 2025 (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=1108898718"