Commons:Requests for checkuser

From Wikimedia Commons, the free media repository
Jump to navigation Jump to search

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
Artículo bueno.svg Confirmed Symbol confirmed.svg Technically indistinguishable
Likely Symbol version generic.svg Possilikely
Symbol possible vote.svg Possible Symbol unlikely.svg Unlikely
Symbol unsupport vote.svg Inconclusive Symbol unrelated.svg Unrelated
Symbol no support vote.svg No action Time2wait.svg Stale
Request declined
Declined Checkuser is not for fishing
Checkuser is not magic pixie dust. 8ball The CheckUser Magic 8-Ball says
Cyberduck icon.png It looks like a duck to me Checkuser is not a crystal ball.
Information
Additional information needed Deferred to
 Doing… Pictogram voting info.svg 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‎ (2 P)
Commons:Requests for checkuser/Case/Fisherman1149
Commons:Requests for checkuser/Case/Vivekkumaryadav98011

Requests[edit]

Fisherman1149[edit]

view • edit • history • watch
Filed: 16:19, 7 March 2023 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: The same pattern of uploading unfree photos to the Commons of famous Ukrainian persons. Also, parts of the nicks are matching. Renvoy (talk) 16:19, 7 March 2023 (UTC)Reply[reply]

Artículo bueno.svg Confirmed, also Editor1149112 (talk • contribs • Luxo's • SUL • deleted contribs • logs • block user • block log ) and Editor1098765 (talk • contribs • Luxo's • SUL • deleted contribs • logs • block user • block log ). --Krd 05:00, 8 March 2023 (UTC)Reply[reply]

Sick Rino[edit]

view • edit • history • watch
Filed: 22:14, 6 March 2023 (UTC)

Suspected related users[edit]

another bunch of exactly the same pattern (some are stale, I know):

Rationale, discussion and results[edit]

Reason: Since a few weeks we have a new influx of spam I stumbled upon today. I can't see whether it is a new spambot engine or a single spammer or a group. Always the same pattern: One file is uploaded followed by two (occasionally three) consecutive edits. The file desc carries the spam link, which often points to a betting site. The images are randomly selected, depicting a football or a stadium or graphics. If it cannot be handled by IP blocks it becomes nasty as it is nearly impossible to build a matching spam filter. There might be more accounts I didn't find yet. --Achim55 (talk) 22:14, 6 March 2023 (UTC)Reply[reply]

Puxunito[edit]

view • edit • history • watch
Filed: 12:35, 6 March 2023 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: The user Javierrrrr66668 reacted on the deletion request of File:Craqdi.jpg: Commons:Deletion requests/File:Craqdi.jpg, and continued writing on the page via IP, after having been banned. I added the account which uploaded the picture as well. I add Purisa89, as this requester wanted to confront me. CoffeeEngineer (talk) 12:35, 6 March 2023 (UTC) I also add the user Priss45, who sudently appeared to comment only on my deletion requests.--CoffeeEngineer (talk) 01:05, 7 March 2023 (UTC). And I add Aeosbot who came to vandalise the deletion request. --CoffeeEngineer (talk) 14:16, 7 March 2023 (UTC) And the mysterious and new Valdimars as well.--CoffeeEngineer (talk) 14:18, 7 March 2023 (UTC)Reply[reply]

[[Get lost, and continue uploading porn somewhere else. CoffeeEngineer (talk) 12:35, 6 March 2023 (UTC)]] Denigrating comments made towards me by the user who claims to be vilified CoffeeEngineer
These articles are good, and this user name CoffeeEngineer is constantly dedicated to attacking me and other users. — Preceding unsigned comment added by Priss45 (talk • contribs) 02:41, 7 March 2023 (UTC)Reply[reply]
And others... CoffeeEngineer (talk) 16:26, 7 March 2023 (UTC)Reply[reply]
  • I blocked Mariu44 on behaviour, and the IP for 3 days. Yann (talk) 19:46, 7 March 2023 (UTC)Reply[reply]

Vivekkumaryadav98011[edit]

view • edit • history • watch
Filed: 10:51, 6 March 2023 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: Per global lock request, please check sleepers and block their using IP ranges if possible. Thanks. --SCP-2000 10:51, 6 March 2023 (UTC)Reply[reply]

Artículo bueno.svg Confirmed, + Viveksheelvant (talk • contribs • Luxo's • SUL • deleted contribs • logs • block user • block log ), more sleepers possible. --Krd 16:42, 6 March 2023 (UTC)Reply[reply]
Request global lock. Thanks. SCP-2000 17:03, 6 March 2023 (UTC)Reply[reply]

A3cb1[edit]

Suspected related users[edit]

view • edit • history • watch

Rationale[edit]

Results[edit]

I have blocked each of the accounts named above and also User:Rumulco96 and User:FrancescoNitti as socks of A1cb3. .     Jim . . . (Jameslwoodward) (talk to me) 14:39, 3 March 2023 (UTC)Reply[reply]



TylerKutschbach[edit]

view • edit • history • watch
Filed: 02:58, 1 March 2023 (UTC)

Suspected related users[edit]


Rationale, discussion and results[edit]

Reason: The user Jimboa Wales has made three edits on Commons, each of which were to revert specific U.S. election maps to their previous revisions. These include maps for the 2022 U.S. Pennsylvania Senate elections, as well as the 2020 Presidential Election in Florida and Georgia. This behavior matches the behavior of previously discovered socks of Tyler Kutschbach, such as 4334r3fg24t and Arizona432, who have each made reverts on these files to restored the sockmaster's preferred version. A sleeper check might be warranted, and tags should probably be applied to any discovered socks; this disruption may be cross-wiki in nature, so if there are sleepers found I would ask that the CU request global locks. — Red-tailed hawk (nest) 02:58, 1 March 2023 (UTC)Reply[reply]

First user is Time2wait.svg stale, nothing to check. Krd 16:44, 6 March 2023 (UTC)Reply[reply]
I blocked Jimboa Wales for COM:IU. Yann (talk) 19:51, 7 March 2023 (UTC)Reply[reply]

Hom Ling Zum[edit]

view • edit • history • watch
Filed: 16:27, 28 February 2023 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: Flag vandalism. Likely sleepers per the last set. (which are <noinclude>ed on this page.) See also Commons:Administrators' noticeboard/Vandalism/Archive 19#S020730zm and Commons:Requests for checkuser/Case/Han Mi Nyeo. —‍Mdaniels5757 (talk • contribs) 16:27, 28 February 2023 (UTC)Reply[reply]

I added Afdhafa Hijctydx to the request. See also Commons:Administrators'_noticeboard/Vandalism#Afdhafa_Hijctydx. TilmannR (talk) 22:31, 4 March 2023 (UTC)Reply[reply]
Artículo bueno.svg Confirmed Krd 16:54, 6 March 2023 (UTC)Reply[reply]

Elaha Qarlugh[edit]

view • edit • history • watch
Filed: 11:44, 28 February 2023 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: Came across these accounts while going through Sockpuppet investigations/Cyber.Eyes.2005, whose sockpuppets were adding the images to enwiki pages in tandem with when these accounts uploaded them. Most of the images these accounts uploaded (relating to Pakistan) have been deleted for false claims of ownership while they were blatant copyvios from webpages. A CU might be needed to further verify this and unearth other socks. Gotitbro (talk) 11:44, 28 February 2023 (UTC)Reply[reply]

Artículo bueno.svg Confirmed, also Likely:
--Krd 16:48, 6 March 2023 (UTC)Reply[reply]

Joycieeexxx[edit]

view • edit • history • watch
Filed: 12:52, 23 February 2023 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason:

Socks related to the user with their exact behaviours: keep uploading copyrighted and non-libre files after ignoring multiple warnings. Besides, an abuse filter is needed.

The Harvett Vault (user; talk) 12:52, 23 February 2023 (UTC); edited: 09:19, 24 February 2023 (UTC)Reply[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=738655880"