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]

Jorse García

[edit]

Status: resolved • view • edit • history • watch
Filed: 05:31, 9 March 2025 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: There is a high coincidence between the two suspicious accounts in the persistent uploading of Hollywood movie logos, all of them assuming that they are licensed under Creative Commons, when it is obvious that they do not have these licenses. The users have a similar pattern with another account already blocked globally, Erickpérez596 (talk · contributions · Statistics). I have the additional suspicion that one of the suspected accounts bears a striking resemblance to my username, since I was the one who detected the Erickpérez596's puppet. Taichi (talk) 05:31, 9 March 2025 (UTC)[reply]

Confirmed CRITOEP7 = Taichanx. --Krd 05:02, 10 March 2025 (UTC)[reply]

Wemerson Inácio da Silva

[edit]

Status: resolved • view • edit • history • watch
Filed: 12:29, 7 March 2025 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: Very same behavior of Emerson and Wemerson Inácio da Silva (talk · contribs), the latter already banned. Probably a duck, but perhaps there are more of them. RodRabelo7 (talk) 12:29, 7 March 2025 (UTC)[reply]

Confirmed --Krd 05:06, 10 March 2025 (UTC)[reply]

Guishín Pastofrio

[edit]

Status: resolved • view • edit • history • watch
Filed: 02:20, 6 March 2025 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: Another puppet by Guishín Pastofrio. See [1] y [2]. Same behavior here and at sp:wp Rastamby (talk) 02:20, 6 March 2025 (UTC)[reply]

Inconclusive --Krd 08:09, 6 March 2025 (UTC)[reply]

Bbonilla1986

[edit]

Status:  to be archived • view • edit • history • watch
Filed: 15:22, 2 March 2025 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: Three brand new accounts requesting deletion of the same file all within a few days. The file has a valid license at source. See also Commons:Deletion requests/File:Lucia Jaramillo SESIÓN PARLAMENTARIA DE POSESIÓN DE LAS Y LOS ASAMBLEÍSTAS PARA EL PERÍODO LEGISLATIVO 2023 - 2024, ECUADOR, 17 DE NOVIEMBRE DEL 2023 02.jpg. Yann (talk) 15:22, 2 March 2025 (UTC)[reply]

Inconclusive --Krd 06:35, 3 March 2025 (UTC)[reply]

Anonymous Hong Kong Photographer 1

[edit]

Status: open • view • edit • history • watch
Filed: 00:42, 24 February 2025 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: Raised by m:Requests for comment/Blatant sockpuppetry in good faith, it looks like there may also have sleepers IDK before?! Liuxinyu970226 (talk) 00:42, 24 February 2025 (UTC)[reply]

See Category:Sockpuppets of Anonymous Hong Kong Photographer 1. There are over 650 of these sockpuppets, without a main account that the user is associated. The name "Anonymous Hong Kong Photographer 1" is a term that describes this user by the community (this name was never created by this user). 〈興華街〉📅❓ 09:43, 24 February 2025 (UTC)[reply]
These are a real lot of accounts with a real lot of uploads each. What is the exact behaviour pattern? What is the proposed action against the confirmed socks? --Krd 12:14, 27 February 2025 (UTC)[reply]
Commons:Requests_for_checkuser/Case/Liauyu_Riuhwa#c-Elcobbola-2019-08-12T16:45:00.000Z-Rationale,_discussion_and_results. RoyZuo (talk) 13:21, 27 February 2025 (UTC)[reply]
What is the exact behaviour pattern?
  1. Extremely serious socking without a main account, even though there are no warnings to the user (except FoP-related deletion requests).
  2. Using strange names in accounts.
  3. Serious FoP-violation in respective countries/regions.
  4. Systematic, but inconsistent categorization.
  5. Creation of categories with bilingual names.
  6. User pages only created as galleries.
  7. Never replied in talk pages.
  8. Intentionally removing sockpuppetry tags.
  9. Indirect disclosure of personal information.
What is the proposed action against the confirmed socks?
Getting the user globally locked. And if new socks appear, immediately lock it. 〈興華街〉📅❓ 15:33, 27 February 2025 (UTC)[reply]
There is no use by means of using the admins' noticeboard as this is now a difficult case. The best thing to do is to get the new accounts locked and contribs deleted just like what used to be done with MOHLEAOSONDWN 2300. If this was taken into account, he is deliberately evading blocks, and this is spamming. 〈興華街〉📅❓ 15:49, 27 February 2025 (UTC)[reply]

Ricardinho da Souza Silva 7

[edit]

Status: open • view • edit • history • watch
Filed: 15:10, 11 February 2025 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: All of these accounts -some only registered on Commons- started making banking edits here, and some of them continued the same behavior at eswiki. All of them have similarities to Ricardinho da Souza Silva 7. --Stïnger （会話） 15:10, 11 February 2025 (UTC).[reply]

 Doing…. This will end Confirmed for most accounts, but it takes more time to check all other accounts that show up. Krd 17:01, 11 February 2025 (UTC)[reply]
FYI, I've just found and added six more to the list. --Stïnger （会話） 16:22, 12 February 2025 (UTC).[reply]
+Two more. Will be still updating if I find more. --Stïnger （会話） 15:06, 13 February 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=1007853421"