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.
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.
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.
5. Requests to run a check on yourself will be declined.

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‎ (1 P)

Commons:Requests for checkuser/Case/Mar252525

Requests

Mar252525

view • edit • history • watch
Filed: 00:04, 22 February 2023 (UTC)

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

Suspected related users

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

Rationale, discussion and results

Reason:

They seem a probable sock after ignoring multiple warnings of uploading copyrighted and non-libre files. Does this count?

The Harvett Vault (user; talk) 00:04, 22 February 2023 (UTC); edited: 01:57, 22 February 2023 (UTC)

User:Mar252525 and User:Eklektous Unrelated but User:Mar252525 is Confirmed to User:Maza787878 and User:Mar212121. - FitIndia ^{Talk ✉} 07:02, 23 February 2023 (UTC)

Antmant3

view • edit • history • watch
Filed: 16:19, 21 February 2023 (UTC)

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

Suspected related users

• Sandiagaucok67 (talk • contribs • Luxo's • SUL • deleted contribs • logs • block user • block log • checkuser)
• Manisclaudia70 (talk • contribs • Luxo's • SUL • deleted contribs • logs • block user • block log • checkuser)
• Kokoenonki2 (talk • contribs • Luxo's • SUL • deleted contribs • logs • block user • block log • checkuser)

Rationale, discussion and results

Reason: Over the past few days all four of these accounts have uploaded pdf files advertising free viewing of copyright films. The uploads have been remarkably similar and I would be amazed if there was not a connection. It would be good if there an underlying IP as it will save me quite a bit of work! Thanks. Herby ^{talk thyme} 16:19, 21 February 2023 (UTC)

• Confirmed, naturally, that Antmant3 and the already-blocked accounts are related. Will consider underlying IP measures. Эlcobbola _talk 16:40, 21 February 2023 (UTC)

Takiva

view • edit • history • watch
Filed: 02:13, 19 February 2023 (UTC)

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

Suspected related users

• ⵜⴰⴽⵉ (talk • contribs • Luxo's • SUL • deleted contribs • logs • block user • block log • checkuser)

Rationale, discussion and results

Reason: both users act on the same files (uploads, categorizations). They complement each other on files relating to the flags and maps of the Maghreb. While some of their actions have been canceled or their renaming requests have been refused (example: Takiva request, ⵜⴰⴽⵉ request).

In addition "ⵜⴰⴽⵉⵖⴰ" is a translation of "Takiva" name into Tifinagh alphabet. ""ⵜⴰⴽⵉ" is a shortname. Poudou99 (talk) 02:13, 19 February 2023 (UTC)

Confirmed & blocked. - FitIndia ^{Talk ✉} 08:04, 19 February 2023 (UTC)

EricGarcia2

view • edit • history • watch
Filed: 01:57, 19 February 2023 (UTC)

• EricGarcia2 (talk • contribs • Luxo's • SUL • deleted contribs • logs • block user • block log • checkuser) (and others linked at Commons:Administrators' noticeboard/User problems/Archive 103#Too many Eric Garcias)

Suspected related users

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

Rationale, discussion and results

Reason: Just blocked EricGarcia9167 as a continuation of the disruption reported at Commons:Administrators' noticeboard/User problems/Archive 103#Too many Eric Garcias. A block of the underlying IP/range, if any, would be helpful, otherwise we're just playing whack-a-mole. —‍Mdaniels5757 (talk • contribs) 01:57, 19 February 2023 (UTC)

• This has been  Done as far as possible. Эlcobbola _talk 16:32, 21 February 2023 (UTC)

---

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