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:

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

Adamvase

Status: open • view • edit • history • watch
Filed: 12:27, 9 April 2024 (UTC)

• Adamvase (talk • contribs • Luxo's • SUL • deleted contribs • logs • block user • block log • checkuser)

Suspected related users

• Gapingprolapse (talk • contribs • Luxo's • SUL • deleted contribs • logs • block user • block log • checkuser)

Rationale, discussion and results

Reason: LTA, similar vandalism. Both accounts are blocked (see here and here), but maybe there's an IP range to block? Trijnstel_talk 12:27, 9 April 2024 (UTC)

• Confirmed - Sorry, Trijnstel, I did look into this yesterday when you pinged at ANV but forget to note the same. For reference, this also the LTA that's been posting with lewd user names (and comments) to User talk:GorillaWarfare. Эlcobbola _talk 13:58, 9 April 2024 (UTC)
  • @Elcobbola: Alright, thanks. And is there an IP address or range to block? (Because I didn't see a block.) Plus, I assume Bigveinydick4Molly (talk · contribs) isn't related? This account isn't blocked btw, so you might wish to block it anyway, related or not. ;-) Trijnstel_talk 14:17, 9 April 2024 (UTC)
    • That account is related, as is Spawtew, etc. It was globally blocked yesterday, which is why I did not block it locally, but it looks like a steward action (hiding/oversighting/deleting due to the name) caused the local account to decouple. I've now blocked it locally. I don't want to comment on IP issues for privacy reasons, but it will be handled. Эlcobbola _talk 14:27, 9 April 2024 (UTC)

Babysuccess

Status:  to be archived • view • edit • history • watch
Filed: 19:44, 27 March 2024 (UTC)

• Babysuccess (talk • contribs • Luxo's • SUL • deleted contribs • logs • block user • block log • checkuser)

Suspected related users

• Warrideybigo (talk • contribs • Luxo's • SUL • deleted contribs • logs • block user • block log • checkuser)

Rationale, discussion and results

Reason: Babysuccess and Agilityman are both globally locked accounts that have uploaded multiple images here, with all of Agilityman's images deleted and I've got a pending request on all of Babysuccess's images. The uploads are consistent in that they appear to be screenshots, have focus issues and use the same odd license {{3dpatent}} and often mention the same wordpress site as the author. On other wiki's, they've created promotional articles on often borderline (at best) people where they add the images they've uploaded here. Warrideybigo was created a few days ago and uploaded several images, including one for Isaiah Ogedegbe who has been a common element in the articles they've created. The images use the same licensing and have the same screenshot / poor focus appearance. Warrideybigo has only edited here, so this is realistically the best CU option. Ravensfire (talk) 19:44, 27 March 2024 (UTC)

Likely Krd 06:51, 30 March 2024 (UTC)

---

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