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]

Baginda 480

[edit]

Status: resolved • view • edit • history • watch
Filed: 14:27, 7 August 2025 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: Tend to upload images that are related to Mahathir Mohammed. A1Cafel (talk) 14:27, 7 August 2025 (UTC)[reply]

Very Likely to Confirmed to Baginda 480:

Blocked and tagged. --Lymantria (talk) 18:25, 7 August 2025 (UTC)[reply]


Haro10DC

[edit]

Status: resolved • view • edit • history • watch
Filed: 17:00, 6 August 2025 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: All three accounts are constantly uploading copyrighted material related to Jidou Studios, including posters and screenshots. Several images have been deleted and received warnings. Gumball21 also created DR for anomalous reasons ("because Geom (a Spanish Wikipedia admin) deleted my images" in Spanish). The reason is that the Spanish Wikipedia administrator has been monitoring edits about Jidou Studio. Taichi (talk) 17:00, 6 August 2025 (UTC)[reply]

All three are Confirmed. Blocked and tagged. The Squirrel Conspiracy (talk) 17:12, 6 August 2025 (UTC)[reply]

Tatoriyo

[edit]

Status:  to be archived • view • edit • history • watch
Filed: 23:50, 4 August 2025 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: Suspected sock players engaging in copyvio uploads. Tatoriyu made an upload of File:Taro Sailor Taro.png, Anff9999 of File:(Taro ) Sailor Taro.png. IIRC, the latter is similar or outright identical to the former. Grand-Duc (talk) 23:50, 4 August 2025 (UTC)[reply]

Confirmed:
Blocked and tagged. The Squirrel Conspiracy (talk) 04:14, 5 August 2025 (UTC)[reply]

Jordanene7

[edit]

Status:  to be archived • view • edit • history • watch
Filed: 20:21, 3 August 2025 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: The suspected sockpuppeted user is again caused much trouble at Wikimedia. If anyone know, after 84 accounts related to Jordanene7 was blocked, the new account with similar behaviour as the sock was created again, hasn't learning much after the previous blocking. Similar to other confirmed socks, this user uploaded an images that may have wrong license and copyright violation, see the user's talk page. We need the attention regarding the new emergence of new sock. Yayan550 (talk) 20:21, 3 August 2025 (UTC)[reply]

Confirmed Blocked and tagged. The Squirrel Conspiracy (talk) 21:20, 3 August 2025 (UTC)[reply]


Miticr21

[edit]

Status:  to be archived • view • edit • history • watch
Filed: 11:05, 31 July 2025 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: similar interest in uploading internet photos of "SUNEL Arena" as previous socks (DONR21 and Nikoskoukkos21), and similar editing interest on enwiki. --0x0a (talk) 11:18, 31 July 2025 (UTC)[reply]

RefMark has been blocked by The Squirrel Conspiracy, but I cannot see if that was based on behavioural or technical data. --Lymantria (talk) 09:09, 4 August 2025 (UTC)[reply]
Whoops, sorry. This one is Confirmed. I got distracted forwarding the EnWiki admins this result, as there was abuse there, and forgot to close the local case. The Squirrel Conspiracy (talk) 09:10, 4 August 2025 (UTC)[reply]


Kiananjomani

[edit]

Status: resolved • view • edit • history • watch
Filed: 15:33, 2 August 2025 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: Strange uploads / licenses airplane related --Hedwig in Washington (mail?) 15:33, 2 August 2025 (UTC)[reply]

Confirmed --Krd 06:06, 3 August 2025 (UTC)[reply]
After a message at COM:ANU I Confirmed also:
--Lymantria (talk) 20:43, 8 August 2025 (UTC)[reply]

Kiananjomani

[edit]

Status: resolved • view • edit • history • watch
Filed: 10:40, 31 July 2025 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: Sure looks like them, air planes that crashed, (c) photos, and a VRT ticket. --Hedwig in Washington (mail?) 10:40, 31 July 2025 (UTC)[reply]

Sorry for the 3 earlier cu-requests, they didn't show up for some strange reason. ----Hedwig in Washington (mail?) 10:42, 31 July 2025 (UTC)[reply]

Kiananjomani

[edit]

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

[edit]

Rationale, discussion and results

[edit]

Reason: same MO, airplane pics --Hedwig in Washington (mail?) 03:26, 28 July 2025 (UTC)[reply]

 It looks like a duck to me --Krd 13:13, 1 August 2025 (UTC)[reply]

Kiananjomani

[edit]

Status: resolved • view • edit • history • watch
Filed: 17:30, 23 July 2025 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: passed the duck test. Uploaded copyright violation images from websites (1), and used wrong template license with copyvio images (2), removed copyvio tagged (3), used invalid VRT ticket permission (4). Gyrostat (talk) 17:30, 23 July 2025 (UTC)[reply]

Likely --Krd 08:00, 24 July 2025 (UTC)[reply]


Kiananjomani

[edit]

Status: resolved • view • edit • history • watch
Filed: 15:33, 2 August 2025 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: Strange uploads / licenses airplane related --Hedwig in Washington (mail?) 15:33, 2 August 2025 (UTC)[reply]

Confirmed --Krd 06:06, 3 August 2025 (UTC)[reply]
After a message at COM:ANU I Confirmed also:
--Lymantria (talk) 20:43, 8 August 2025 (UTC)[reply]

Kiananjomani

[edit]

Status: resolved • view • edit • history • watch
Filed: 10:40, 31 July 2025 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: Sure looks like them, air planes that crashed, (c) photos, and a VRT ticket. --Hedwig in Washington (mail?) 10:40, 31 July 2025 (UTC)[reply]

Sorry for the 3 earlier cu-requests, they didn't show up for some strange reason. ----Hedwig in Washington (mail?) 10:42, 31 July 2025 (UTC)[reply]

Kiananjomani

[edit]

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

[edit]

Rationale, discussion and results

[edit]

Reason: same MO, airplane pics --Hedwig in Washington (mail?) 03:26, 28 July 2025 (UTC)[reply]

 It looks like a duck to me --Krd 13:13, 1 August 2025 (UTC)[reply]

Kiananjomani

[edit]

Status: resolved • view • edit • history • watch
Filed: 17:30, 23 July 2025 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: passed the duck test. Uploaded copyright violation images from websites (1), and used wrong template license with copyvio images (2), removed copyvio tagged (3), used invalid VRT ticket permission (4). Gyrostat (talk) 17:30, 23 July 2025 (UTC)[reply]

Likely --Krd 08:00, 24 July 2025 (UTC)[reply]


Jordanene7

[edit]

Status:  to be archived • view • edit • history • watch
Filed: 20:21, 3 August 2025 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: The suspected sockpuppeted user is again caused much trouble at Wikimedia. If anyone know, after 84 accounts related to Jordanene7 was blocked, the new account with similar behaviour as the sock was created again, hasn't learning much after the previous blocking. Similar to other confirmed socks, this user uploaded an images that may have wrong license and copyright violation, see the user's talk page. We need the attention regarding the new emergence of new sock. Yayan550 (talk) 20:21, 3 August 2025 (UTC)[reply]

Confirmed Blocked and tagged. The Squirrel Conspiracy (talk) 21:20, 3 August 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=1069646028"