Jump to content

Commons:Requests for checkuser

From Wikimedia Commons, the free media repository
(Redirected from Commons:RFCU)

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.
Transcluding the request
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.


nothing found

Requests

[edit]

Need Reqer

[edit]
[edit]

Rationale, discussion and results

[edit]

Reason: Suspected lock evasion: Same kind of kid-like trolling. --Achim55 (talk) 21:10, 31 May 2026 (UTC)[reply]

Carlosarevalohn

[edit]
[edit]

Rationale, discussion and results

[edit]

Reason:

To be fair, none of the users reported in this batch have acted disruptively so far (unless we count uploading seemingly promotional stuff as disruption). I don't know whether they should be blocked for socking alone, but am still reporting them for the record and in case there are more accounts which I have not discovered yet and that may be acting disruptive in the meantime. Nakonana (talk) 16:06, 29 May 2026 (UTC)[reply]

Another TA (just for the sake of completeness):
Reason: Edits on eswiki revolve around brands of C24 Honduras[3][4][5] and they also made a questionable edit on Commons[6]. Nakonana (talk) 16:36, 29 May 2026 (UTC)[reply]
The two accounts are Likely to this case. Blocked and tagged. No comment on TA's. --Lymantria (talk) 17:01, 29 May 2026 (UTC)[reply]

毕明明

[edit]
[edit]

Rationale, discussion and results

[edit]

Reason: RichardGao0011 created an incomplete DR at Commons:Deletion requests/File:Xiaomi Auto logo.svg, similar to what the indef-blocked User:毕明明 did at the same DR page. Also, RichardGao0011 has a similar username as the indef-blocked account User:RichardBi0129. So I suspected RichardGao0011 is a sockpuppet.

Note that User:毕明明 and User:RichardBi0129 has already been confirmed as sockpuppets at their en-wiki page.

Thanks. Tvpuppy (talk) 22:02, 28 May 2026 (UTC)[reply]

Difficult to conclude, because of proxy use. I'd say it is Possible from a technical point of view, but behaviourally it is quite clear. Blocking and tagging. --Lymantria (talk) 14:29, 29 May 2026 (UTC)[reply]
P.S. Contrary to the enwiki case, I was able to find
as Likely to 毕明明. --Lymantria (talk) 14:35, 29 May 2026 (UTC)[reply]

Kattie Katey (Storm)

[edit]
[edit]

Rationale, discussion and results

[edit]

Reason: Suspected block-evading sock, see Category:Sockpuppets of Kattie Katey (Storm). Removed the related entry twice from my sock list. Created d:Q139960527 shortly after d:Q139916112 was deleted. --Achim55 (talk) 12:15, 28 May 2026 (UTC)[reply]

See also Kitty Rena Chan (talk contribs Luxo SUL deleted contribs logs block user block log).   — 🇺🇦Jeff G. please ping or talk to me🇺🇦 13:30, 28 May 2026 (UTC)[reply]
From CU data Kitty Rena Chan is Likely to one of the earlier Category:Sockpuppets of Kattie Katey (Storm) socks, and behaviour strongly supports it. Blocked and tagged. --Lymantria (talk) 07:08, 29 May 2026 (UTC)[reply]
Added to this thread as Likely:
--Lymantria (talk) 07:14, 29 May 2026 (UTC)[reply]

Antonypiano

[edit]
[edit]

Rationale, discussion and results

[edit]

Reason: StrangeTraveler created Category:Antonis Fragakis. Obviously a duck, so please check for sleepers. NguoiDungKhongDinhDanh 00:13, 28 May 2026 (UTC)[reply]

Confirmed, no sleepers found. --Lymantria (talk) 05:23, 28 May 2026 (UTC)[reply]

Charles Jimenez

[edit]

Suspected missed related user: User:Andrew_Franco1992

Dotyoyo (talk) 19:51, 23 May 2026 (UTC)[reply]

Results: Confirmed:

All blocked. Case moved to Charles Jimenez as oldest account and all socks in this case tagged accordingly. --Lymantria (talk) 07:06, 24 May 2026 (UTC)[reply]

Hfhtdjf

[edit]
[edit]

Rationale, discussion and results

[edit]

Reason: As first edits, Whatjapeenedtoyou removed 3 deletion requests from files uploaded by Hfhtdjf. New account created after Hfhtdjf block. Similar interests. Also tests/nonsense edits like [7]. Yann (talk) 18:59, 22 May 2026 (UTC)[reply]

This seems obvious from the first edits by Whatjapeenedtoyou, but from CU data I just can say it is Possible. Meatpuppetry more likely. --Lymantria (talk) 20:09, 23 May 2026 (UTC)[reply]
OK, blocked. Yann (talk) 17:18, 26 May 2026 (UTC)[reply]
@Lymantria: A new account came up today. Yann (talk) 22:09, 30 May 2026 (UTC)[reply]
@Yann: do you have an account name? --Lymantria (talk) 07:03, 31 May 2026 (UTC)[reply]
@Lymantria: I added it above: Hfthdjf. Yann (talk) 10:39, 31 May 2026 (UTC)[reply]
Same conclusion as previous one: Possible. --Lymantria (talk) 15:21, 31 May 2026 (UTC)[reply]
 Info Whatjapeenedtoyou has made proxying attempts at enwiki. HyperAnd [talk] 23:26, 31 May 2026 (UTC)[reply]

Carlosarevalohn

[edit]
[edit]

Rationale, discussion and results

[edit]

Reason:

To be fair, none of the users reported in this batch have acted disruptively so far (unless we count uploading seemingly promotional stuff as disruption). I don't know whether they should be blocked for socking alone, but am still reporting them for the record and in case there are more accounts which I have not discovered yet and that may be acting disruptive in the meantime. Nakonana (talk) 16:06, 29 May 2026 (UTC)[reply]

Another TA (just for the sake of completeness):
Reason: Edits on eswiki revolve around brands of C24 Honduras[10][11][12] and they also made a questionable edit on Commons[13]. Nakonana (talk) 16:36, 29 May 2026 (UTC)[reply]
The two accounts are Likely to this case. Blocked and tagged. No comment on TA's. --Lymantria (talk) 17:01, 29 May 2026 (UTC)[reply]



For older requests, please see Commons:Requests for checkuser/Archives