Commons:Requests for checkuser

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.	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:

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.)
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.
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.
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

Ricardinho da Souza Silva 7

Status: resolved • view • edit • history • watch
Filed: 03:41, 25 August 2025 (UTC)

Ricardinho da Souza Silva 7 (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log • checkuser)

Suspected related users

Martinuti6 (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log • checkuser)
Yarmolenku (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log • checkuser)

Rationale, discussion and results

Reason: Martinuti6 and Yarmolenku are confirmed socks at frwiki by local CUs, both accounts are adding uploads at Commons. There may be more socks adding bank/money photographies like these two, whose uploads must be deleted - if true, I'll report them all at m:SRG. --Stïnger （会話） 03:41, 25 August 2025 (UTC).[reply]

Confirmed

Martinuti6 (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log • checkuser)
Nderson787 (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log • checkuser)
Jourmala (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log • checkuser)
Andres movilla caucil (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log • checkuser)

Blocked and tagged. I've also blocked and tagged user:Yarmolenku per fr.wiki and upload history. The Squirrel Conspiracy (talk) 03:54, 25 August 2025 (UTC)[reply]

@Stïnger: Thanks! The Squirrel Conspiracy (talk) 04:01, 25 August 2025 (UTC)[reply]

PayamAvarwand

Status: resolved • view • edit • history • watch
Filed: 16:28, 24 August 2025 (UTC)

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

Suspected related users

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

Rationale, discussion and results

Reason: On the same day when PayamAvarwand was blocked, MMisaghian was created. They uploaded the same file:5-Nakhl.jpg. Taivo (talk) 16:28, 24 August 2025 (UTC)[reply]

Confirmed Blocking and tagging. --Lymantria (talk) 19:20, 24 August 2025 (UTC)[reply]

BiggCooker

Status: resolved • view • edit • history • watch
Filed: 12:56, 21 August 2025 (UTC)

BiggCooker (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log • checkuser)
Later appointed to Thebigboi6572 (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log • checkuser)

Suspected related users

BashBuilder (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log • checkuser)
ToncianTaien (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log • checkuser)

Rationale, discussion and results

Reason: Per request at Commons:Administrators' noticeboard/Blocks and protections#Unicode data semi-protection, these 3 users replied to the thread on the same day with similar writing style. It appears these users were attempting to sway opinion on lowering the protection for the unicode characters. Also, all 3 users mainly edits files related to unicode characters. You can also see them at another thread Commons:Administrators' noticeboard/Blocks and protections#Unicode data semi-protection.

@Surjection pointed out these may be related to the blocked user Thebigboi2025. I wasn’t sure about that, since it appears that user is instead a sock of another LTA. Perhaps Surjection can provide more insight to these users. Anyways, since this user was blocked more than 90 days ago, I believe it may be a stale for this user, so I have not include this user. Thanks. Tvpuppy (talk) 12:56, 21 August 2025 (UTC)[reply]

This is almost certainly the same person as behind Thebigboi2025. I've blocked numerous of their socks (confirmed via CU) on en.wikt. They've edited both with socks as well as offline using IPs. Some of their edits were straight up vandalism, but most are at least attempts to contribute. They've also issued threats against me, but most of them were rather juvenile in how they were worded. I suspect this person is rather young, but naturally cannot prove it, and it shouldn't be treated as anything else than a hunch.

A short and incomplete list of other confirmed accounts from en.wikt:

Coolingy (talk · contributions · Move log · block log · uploads · Abuse filter log) block user
Coolingian (talk · contributions · Move log · block log · uploads · Abuse filter log) block user
Cooʟs dowɴ (talk · contributions · Move log · block log · uploads · Abuse filter log) block user
Thebigboi6572 sucks (talk · contributions · Move log · block log · uploads · Abuse filter log) block user
No need to go (talk · contributions · Move log · block log · uploads · Abuse filter log) block user
Memeziki (talk · contributions · Move log · block log · uploads · Abuse filter log) block user

— SURJECTION ^{/ T / C / L /} 13:58, 21 August 2025 (UTC)[reply]

Results: Confirmed:

BiggCooker (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log • checkuser)
BashBuilder (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log • checkuser)
ToncianTaien (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log • checkuser)
SuperlyDuperly (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log • checkuser)
BiggChug (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log • checkuser)
Coolingian (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log • checkuser)
Malboy1611 (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log • checkuser)

I have appointed Malboy1611 as master. Blocked and tagged. Abuse clear because of a form of vote stacking. --Lymantria (talk) 13:56, 21 August 2025 (UTC)[reply]

With the help of en.wikt CU here are additional results:

Confirmed also