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]

Ekecdnkoewihdouuepiw

[edit]

Status: resolved • view • edit • history • watch
Filed: 19:35, 30 September 2025 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: Reasoning below is copied from COM:AN/B --Lymantria (talk) 19:35, 30 September 2025 (UTC):[reply]

Two accounts uploading a lot of photos of and strange claims about a person called "Robbie (Leo) Edward Sayers" or his apparent full pseudonym of "Leocrain Thunderbolt", mainly focusing on how he ran his own civil engineering company at the age of 13 and designed a culvert system in southern Spain. More context in this deletion request.
File:Engineering design of Arroyo De Monterroso subsurface canal system by Robbie E. Sayers.jpg and File:DESIGNS OF THE RIO MONTERROSO CULVERT. ESTEPONA, MALAGA.jpg both use the same drawing credited to Sayers, and both are claimed as own work.
The two accounts have also uploaded several fake photoshopped images of the late Robert Earl Hughes, discussed at Commons:Deletion requests/File:Robert Earl Hughes, worlds largest man. Electrical engineer.jpg and Commons:Deletion requests/File:Robert Earl Hughes Carnival.jpg. Belbury (talk) 15:14, 30 September 2025 (UTC)[reply]
Dear administrators,
Please take action to remove any and all duplicate content pertaining to that of Robbie Sayers within Wikipedia.
There seems to be sensitive content related to national security, as well as an attempt to take credit for Sayers’s work for the purposes of potential financial gain from Wikimedia Commons.
An absurd case of plagiarism, and I hope that Sayers is reassured by any action taken, if he is even aware. 5.151.181.17 15:46, 30 September 2025 (UTC)[reply]
Dear Belbury,
300px|Operation_Justitia_Infrared_Aeroplane
File:Operation Justitia images of St. Peter Port, Guernsey.jpg 5.151.181.17 15:54, 30 September 2025 (UTC)[reply]
Thanks, so it also looks like we should add User:500 ton man to the list of connected accounts, if they've also been uploading files with descriptions like Infrared images of dwellings and structures situated around St. Peter Port, Guernsey. CPS / SIA exhibit of an illegal international private investigation-"Operation Justitia" ordered by Robbie E. Sayers JP this month. --Belbury (talk) 15:57, 30 September 2025 (UTC)[reply]

Results: Confirmed:

Blocked and tagged. --Lymantria (talk) 19:47, 30 September 2025 (UTC)[reply]

チ一牛フジタ拓也

[edit]

Status: open • view • edit • history • watch
Filed: 05:20, 30 September 2025 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: In the last several hours, two reports on COM:ANV came in. They have the subject of a cross-wiki harassing originating from JA-WP and directed against an admin there, see Special:PermaLink/1093059458#フズィータ・弱男・チ一午拓也. It's likely that a CU may unearth or safeguard technical evidence to fight that kind of abuse. Grand-Duc (talk) 05:20, 30 September 2025 (UTC)[reply]

Confirmed. Moved to master, which is ネメンデス. Full list of socks at Category:Sockpuppets of ネメンデス. The Squirrel Conspiracy (talk) 17:32, 30 September 2025 (UTC)[reply]

AgathaVegaX

[edit]

Status: resolved • view • edit • history • watch
Filed: 06:24, 29 September 2025 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: Mono-thematic uploads from both accounts related to en:Bunny Colby imagery. All images are probable copyvios. The possible sockmaster was created on 2025-09-21 and uploaded 3 images on the same day. These images got a DR with the rationale "Professional shots + film screenshot(?), no EXIF data, unlikely to be own works."
Then, today, the alleged sock uploaded a PNG also depicting the actress. This may be a try at circumventing scrutiny, by choosing an inherently EXIF-less format. If the CU is performed and results in demonstrating an affiliation of these two accounts, this technical evidence is helpful in demonstrating a disregard to our project rules and a readiness to engage in several misconducts at once: copyvio uploads + socking. Grand-Duc (talk) 06:24, 29 September 2025 (UTC)[reply]

Noting that Nosghxbrd17—one of the accounts listed under Sockpuppets of SudoX7—also created Category:Bunny Colby, which aligns with the mono-thematic uploads observed from AgathaVegaX and the other suspected accounts. This adds further weight to the pattern of coordinated uploads and possible sockpuppetry. Saroj (talk) 07:10, 29 September 2025 (UTC)[reply]
Thanks for the info. I just saw an account named AgathaVega in the sock category, also some accounts with the "Error##" naming schema. The check has been run by Lymantria after the messages in Commons:Administrators' noticeboard/User problems/Archive 125#Removal of speedy tag and sockpuppetry. Would this warrant a move of this investigation page towards th actual sockmaster name, SudoX7? Regards, Grand-Duc (talk) 07:20, 29 September 2025 (UTC)[reply]
Confirmed (almost duck) to SudoX7. Moved case to SudoX7. Blocked and tagged. --Lymantria (talk) 07:57, 29 September 2025 (UTC)[reply]
Most likely a newly created sock, their contributions are solely uploading photos of Bunny Colby as well. Thanks. Tvpuppy (talk) 20:33, 29 September 2025 (UTC)[reply]
Confirmed The Squirrel Conspiracy (talk) 02:22, 30 September 2025 (UTC)[reply]

BASEL SANNIB.SANEEB

[edit]

Status: resolved • view • edit • history • watch
Filed: 10:47, 27 September 2025 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: BASEL SANNIB.SANEEB uploaded several files, all of which D.Sabah has edited or overwrote:

D.Sabah also created en:Draft:Basel Saneeb. NguoiDungKhongDinhDanh 10:47, 27 September 2025 (UTC)[reply]

Confirmed both are the same user. D.Sabah is blocked and tagged. --Lymantria (talk) 13:57, 27 September 2025 (UTC)[reply]
Master has been globally locked for crosswiki abuse. --Lymantria (talk) 13:07, 28 September 2025 (UTC)[reply]

A3cb1

[edit]

Status: resolved • view • edit • history • watch
Filed: 07:41, 24 September 2025 (UTC)

[edit]

Rationale, discussion and results

[edit]

Some files uploaded by Börranga are recreations from previous cited known socks. Also, similar main subjects and edit pattern as both master and other socks. -- 80.29.203.133 07:41, 24 September 2025 (UTC)[reply]

Börranga and Marlongos are Confirmed, together with some other accounts already locked. Others are Stale and already (b)locked. --Lymantria (talk) 16:32, 24 September 2025 (UTC)[reply]




ChanComThemPho

[edit]

Status: open • view • edit • history • watch
Filed: 20:43, 20 September 2025 (UTC)

[edit]

and probable more...

Rationale, discussion and results

[edit]

Reason: Could you please block the range? Or create a filter? Well anything to block them preventively. Yann (talk) 20:43, 20 September 2025 (UTC)[reply]

There are 213 confirmed socks, and the sockmaster is highly resistant to rangeblocks. I'll reach out to someone about seeing if filters are an option. The Squirrel Conspiracy (talk) 02:24, 21 September 2025 (UTC)[reply]
@Yann: As far as I know, this LTA use many proxies to evade lock/ban, so I think range blocking might be less effective. Filter is a more robust option. See also this disscussion in viwiki (in Vietnamese). Nvdtn19 (talk) 08:45, 24 September 2025 (UTC)[reply]
About the filter, @Plantaest: maybe you can help them create a filter here to block this LTA? This would be useful and they can update the filter whenever they want, without having to rely on the global filter, which currently seems to be weaker. Nvdtn19 (talk) 05:17, 25 September 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=1093544692"