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]

PradaSaetiew

[edit]

Status: resolved • view • edit • history • watch
Filed: 08:55, 4 July 2025 (UTC)

[edit]

Rationale, discussion and results

[edit]

I would like to request a CheckUser investigation on the following accounts: User:Evrdkmkm, and User:Golf-ben10 (blocked and banned)

Thank you for your consideration. — Preceding unsigned comment added by Tomarzig (talk • contribs) 10:55, 4 July 2025 (UTC)[reply]

Please provide a reason and evidence. --Krd 09:04, 4 July 2025 (UTC)[reply]
If you are creating a new request about this user, please add it to the top of the page, above this notice. Don't forget to add
{{Commons:Requests for checkuser}}
to the checkuser page here. Previous requests (shown below), and this box, will be automatically hidden on Requests for checkuser (but will still appear here).

Jordanene7

[edit]

Status: resolved • view • edit • history • watch
Filed: 12:19, 3 July 2025 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: After TyraFan638 and FamilyFan633 was blocked, a new user suspected as Jordanene7's sockpuppet was created. There's 82 users that related to Jordanene7's sock that already blocked, and it may be 83rd account related to Jordanene7 that may be blocked. We don't a new sockpuppets of Jordanene7 awaken again after it was blocked, because their behaviour may distrupt Wikimedia project. Yayan550 (talk) 12:18, 3 July 2025 (UTC)[reply]

Confirmed:
Blocked and tagged. --Lymantria (talk) 20:48, 3 July 2025 (UTC)[reply]


Remitbuber

[edit]

Status: resolved • view • edit • history • watch
Filed: 15:03, 1 July 2025 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: New users who created Category:Nicolás Atanes and added/edited photos on Commons (e.g. File:Pedro Sánchez y Nicolás Atanes.jpg by Mitheranis), in addition to creating articles about Nicolás Atanes, Virus Matemático, and other Spanish math activism on various language Wikipedias (e.g. gl:Nicolás Atanes) in the same manner as the dozens of globally-locked Remitbuber socks. MarkH21 (talk) 15:08, 1 July 2025 (UTC)[reply]

Working The Squirrel Conspiracy (talk) 23:13, 1 July 2025 (UTC)[reply]
Confirmed -
Also, I created Wikidata:Requests for checkuser/Case/Remitbuber because there's one account active there but not registered on Commons that looks to be part of the same group. The Squirrel Conspiracy (talk) 23:25, 1 July 2025 (UTC)[reply]
Blocked and tagged. Leaving open in case Wikidata CU finds anything. The Squirrel Conspiracy (talk) 23:29, 1 July 2025 (UTC)[reply]
Thanks. Have global locks for the socks been requested already? Also File:Pedro Sánchez y Nicolás Atanes.jpg was created by an already-locked Remitbuber sock, so I suppose that should be deleted? MarkH21 (talk) 00:25, 2 July 2025 (UTC)[reply]
Blocked and tagged Gebcat234 (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log ) based on wikidata CU, where they were found as Likely. Closing. --Lymantria (talk) 06:58, 2 July 2025 (UTC)[reply]


GMatteotti

[edit]

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

[edit]

Rationale, discussion and results

[edit]

Reason: Special:Diff/1049879095 per MrKeefeJohn.   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 10:33, 28 June 2025 (UTC)[reply]

MrKeefeJohn/Jeff G. Please explain why you think Kaplowey is a sock in this case. --Lymantria (talk) 12:14, 28 June 2025 (UTC)[reply]
It's my first time for such things. After a "technical messagge to LadySerina, I was contacted for some question by this user user, I mean LadySerina, before the block. After it, I notice some edits by Kaplowey in some categories and files in my watchlist. So I took a look to Special:CentralAuth/Kaplowey and I noticed some edits in it.wiki and in commons with an edit pattern similar to Special:CentralAuth/Ladyserina, By the way Kaplowey was registered in wiki the same day, 11 June 2025, when LadySerina was blocked. Anyway I can be wrong ;-) MrKeefeJohn (talk) 07:43, 29 June 2025 (UTC)[reply]
MrKeefeJohn: Thanks. We need to have a good reason to use checkuser tools. Therefore a request here requires an explanation. --Lymantria (talk) 10:09, 29 June 2025 (UTC)[reply]

Results: Confirmed Kaplowey (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log ) to this case. Blocked and tagged. --Lymantria (talk) 10:09, 29 June 2025 (UTC)[reply]


Arnulfo1952

[edit]

Status: open • view • edit • history • watch
Filed: 02:26, 26 June 2025 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: Suspected socks of indef-blocked Arnulfo1952. Kaseria123 and Gaha123 both had recreated the template {{Edit semi-protected}} after it was deleted twice (first created by Arnulfo1952).

All users mentioned above mainly edit/upload files related to logos and poodles (Arnulfo1952: [1], Kaseria123: [2], Gaha123: [3], Ruskli123 in en-wiki: [4]). There is also the similarities with their usernames.

Thanks. Tvpuppy (talk) 02:26, 26 June 2025 (UTC)[reply]

Confirmed
Blocked and tagged. The Squirrel Conspiracy (talk) 03:15, 26 June 2025 (UTC)[reply]
Thank you for the confirmation. Just one more thing, can you also check if this is also a sock?
I just noticed Arnulfo1952 edited their talk page before [5], they also edit files related to poodles [6] and they have a similar username with 2 of the socks above. Thanks. Tvpuppy (talk) 03:42, 26 June 2025 (UTC)[reply]
They're stale, but  It looks like a duck to me. Blocked and tagged. The Squirrel Conspiracy (talk) 23:24, 26 June 2025 (UTC)[reply]
All accounts are globally locked. 〈興華街〉📅❓ 05:53, 5 July 2025 (UTC)[reply]

Yuuuuuuuuuuuyiut

[edit]

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

[edit]

Rationale, discussion and results

[edit]

Reason: This user keeps uploading the same selfie, then gets blocked, and then creates a new account. Already 5 accounts in 4 days. Please block any sleeper, and the range. Thanks, Yann (talk) 15:57, 25 June 2025 (UTC)[reply]

Confirmed, no range block possible. --Krd 16:04, 25 June 2025 (UTC)[reply]
@Krd: Yuuuuuuuuuuuyiut (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log ) has an empty block log.   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 05:39, 26 June 2025 (UTC)[reply]
Done. Krd 07:03, 26 June 2025 (UTC)[reply]
@Krd: Thanks!   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 23:17, 26 June 2025 (UTC)[reply]
That was on purpose. I only blocked the socks, not the master. Yann (talk) 18:24, 26 June 2025 (UTC)[reply]
@Yann: I was asking Krd for a Checkuser block. "Abusing multiple accounts to ... evade blocks or other sanctions" is specifically mentioned within Commons:Blocking policy.   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 23:17, 26 June 2025 (UTC)[reply]

Two more accounts uploading the same file in recent days. Marbletan (talk) 12:59, 1 July 2025 (UTC)[reply]

Confirmed:
Blocking and tagging. Adebaregoke is the oldest account, moving case to them as sock master. --Lymantria (talk) 16:11, 2 July 2025 (UTC)[reply]
All accounts are globally locked. 〈興華街〉📅❓ 05:38, 5 July 2025 (UTC)[reply]

Anogenyogan5

[edit]

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

[edit]

Rationale, discussion and results

[edit]

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

Working The Squirrel Conspiracy (talk) 19:59, 20 June 2025 (UTC)[reply]
Confirmed:
The Squirrel Conspiracy (talk) 20:09, 20 June 2025 (UTC)[reply]
All accounts are globally locked. 〈興華街〉📅❓ 08:24, 27 June 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=1052255788"