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]

Max the Flag Subdivision Creator

[edit]

Status: resolved • view • edit • history • watch
Filed: 21:36, 18 December 2025 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: RealFlagSubdivisioner was blocked today as a suspected sock with unknown master. Their username and flag uploads are very similar to the edits by SubdivisionFlagger and All flags of Subdivisions. Emk9 (talk) 21:36, 18 December 2025 (UTC)[reply]

I found another. Emk9 (talk) 21:39, 18 December 2025 (UTC)[reply]
Found Max the Flag Subdivision Creator, which is the oldest of this bunch. Emk9 (talk) 21:41, 18 December 2025 (UTC)[reply]
This is reminiscent of the behavior of ThecentreCZ, SagoShader, Hom Ling Zum and 112.206.98.106 (talk • contribs • WHOIS • RBL • abusefilter • tools • guc • stalktoy • block user • block log • Abuse filter log).   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 06:02, 19 December 2025 (UTC)[reply]
Confirmed blocked and tagged. --Lymantria (talk) 06:40, 19 December 2025 (UTC)[reply]

Atomiccocktail

[edit]

Status: resolved • view • edit • history • watch
Filed: 10:29, 18 December 2025 (UTC)

[edit]

Potential socks already checked by User:Squasher at dewiki:

Rationale, discussion and results

[edit]

Reason: Due to a massive case of potential paid editing by using sockpuppets on dewp I would like to start an investigation here. User:Atomiccocktail has an account for paid editing User:Einfach machen Hamburg. The dewiki Arbcom forbid AC/EmH to cross-edit in paid articles as well as overreferencing and promotional language, see de:Wikipedia:Schiedsgericht/Anfragen/Einfach machen Hamburg. Since then, EmH went inactive but the customer's pages were still maintained. Some new pages were created which perfectly fit in style and laguage of AC, see de:Wikipedia:Administratoren/Anfragen#Verschleiertes Bezahltes Schreiben in großem Stil. A checkuser-investigation at dewiki was only able to found a single sockpuppet (User:Koblenmr7 with dewiki as homewiki (but never edited here), see de:Wikipedia:Checkuser/Anfragen/Atomiccocktail et al.

For a complete investigation it would be neccesary to check, if there are other accounts involved. NDG (talk) 10:29, 18 December 2025 (UTC)[reply]

  • Confirmed - Koblenmr7
  • Unrelated as far as I can tell - Communications & Marketing HCOB
  • Stale - All other accounts
The Squirrel Conspiracy (talk) 15:39, 18 December 2025 (UTC)[reply]

TimeoRN24

[edit]

Status: resolved • view • edit • history • watch
Filed: 10:17, 18 December 2025 (UTC)

Rationale, discussion and results

[edit]

Reason: Passed duck test: uploading copyvios to update the same Wikipedia entries, with a paid-editing suspicion. Gyrostat (talk) 10:17, 18 December 2025 (UTC)[reply]

Confirmed The Squirrel Conspiracy (talk) 15:33, 18 December 2025 (UTC)[reply]


Thatgdperson

[edit]

Status: resolved • view • edit • history • watch
Filed: 14:16, 16 December 2025 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: a. recreated File:Msheireb-Station.webp as File:Msheireb Station.jpg. b. overwriting edits at special:history/Qatar University Station, special:history/Corniche station, special:history/Free Zone station and special:history/Msheireb station. 0x0a (talk) 14:16, 16 December 2025 (UTC)[reply]

Confirmed blocked and tagged. --Lymantria (talk) 17:29, 16 December 2025 (UTC)[reply]

Sahilsambyal

[edit]

Status: resolved • view • edit • history • watch
Filed: 12:44, 14 December 2025 (UTC)

[edit]

Rationale, discussion and results​

[edit]

Suspected sockpuppet of Sahilsambyal Official Potrait (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log) and Journalist Of Bharat uploaded the same file:Kunal Jaiswal in 2024.jpg. Taivo (talk) 12:19, 14 December 2025 (UTC)[reply]

Results: Confirmed to each other and Likely to this case:

Blocked and tagged. --Lymantria (talk) 13:46, 14 December 2025 (UTC)[reply]

Worvandae

[edit]

Status: resolved • view • edit • history • watch
Filed: 09:12, 14 December 2025 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason:The next sock of Worvandae, Đăng Đàn Cung, want to change Category:Xiangqi to Category:General chess. This is a game from China, but they called it by a name translated from Vietnamese, and they need to discuss this beforehand. — Preceding unsigned comment added by Henrydat (talk • contribs)

Results: Confirmed together with a couple of socks, all blocked and tagged and to be found added to Category:Sockpuppets of Đăng Đàn Cung. --Lymantria (talk) 12:40, 14 December 2025 (UTC)[reply]

Global lock requested. --Lymantria (talk) 13:01, 14 December 2025 (UTC)[reply]

DaduSreep

[edit]

Status: resolved • view • edit • history • watch
Filed: 10:03, 13 December 2025 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: Creating pages in non-existent language (vi-th/vi-thu). Already CU-confirmed on Meta. Please check for sleepers. NguoiDungKhongDinhDanh 10:03, 13 December 2025 (UTC)[reply]

Confirmed no sleepers found, all were already locked, tagging. Moving case under JoinKepper as the oldest account. --Lymantria (talk) 13:56, 13 December 2025 (UTC)[reply]

~2025-38330-64

[edit]

Status: open • view • edit • history • watch
Filed: 08:54, 12 December 2025 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: Reported to Commons:Administrators' noticeboard/Blocks and protections by Tvpuppy Suspicious behaviour, warrants a closer look Gbawden (talk) 08:54, 12 December 2025 (UTC)[reply]

✓ Request completed - From looking at the IP address behind the temporary account, and from digging through the edit histories of categories related to the issue (both of which any admin could do), I've identified that this person has been active for years, always within the same IPv6 range. I've placed a block on that range. There is no abuse of multiple accounts - I don't see any evidence that they're deliberately trying to avoid scrutiny (and neither ~2025-38330-45 nor ~2025-38330-15 has edits on this project, so I have no idea what you meant in the suspected related users section); the issue is the bad categories, which you can address with them should they ever create an account. The Squirrel Conspiracy (talk) 08:48, 13 December 2025 (UTC)[reply]

Erika Dauði

[edit]

Status:  to be archived • view • edit • history • watch
Filed: 11:46, 11 December 2025 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: This new user's behavior is too similar to another user's sockpuppet. More information in this discussion:
Commons_talk:Featured_picture_candidates#Fake_edits_and_FPC_voting_rules
--George Chernilevsky talk 11:46, 11 December 2025 (UTC)[reply]

Unrelated As best as I can tell, Livioandronico2013 hasn't been active since 2024, and therefore there's no current data to match them on. Erika Dauði is not, however, a match for their historic data. That said, even if they're not a sock of Livioandronico2013, if you feel that their gaming of the FPC voting requirements is block-worthy, you can act accordingly, of course. The Squirrel Conspiracy (talk) 05:04, 12 December 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=1133400606"