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
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]

Finsoja[edit]

Status: resolved • view • edit • history • watch
Filed: 14:59, 15 November 2023 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: Disruptive user engaged in sock-puppetry with insults, death threats. Finsoja3 and Finsoja4 are already blocked, but confirmation is needed for Thai-khmer learn, who uploaded again over File:HenryIIGospels.jpg. Yann (talk) 14:59, 15 November 2023 (UTC)Reply[reply]

  • Confirmed, among many others. This is a prolific LTA and the true initial account (master) is unclear. X-wiki tagging, if any, has been poor. I've used +L Oai iu aahhaahh as the oldest known confirmed account. Ro.wiki appears to use Blocau darius as the master--this account is not attached on the Commons. Эlcobbola talk 17:28, 15 November 2023 (UTC)Reply[reply]

N19Lu[edit]

Status: resolved • view • edit • history • watch
Filed: 04:03, 14 November 2023 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: Posting copyvio across multiple accounts.

Adeletron 3030 (talk) 04:03, 14 November 2023 (UTC)Reply[reply]

✓ Done All blocked. Yann (talk) 09:59, 16 November 2023 (UTC)Reply[reply]
@Yann: Thanks!   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 10:12, 16 November 2023 (UTC)Reply[reply]
 Comment "JJ 15 27" seems to be the oldest account, so I take it as master. Yann (talk) 10:18, 16 November 2023 (UTC)Reply[reply]

Geeksd37[edit]

Status: resolved • view • edit • history • watch
Filed: 13:54, 13 November 2023 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: Probable sockpuppet/meatpuppets. They're all single-purpose accounts involved with images of Mike Kenji Hirai, a blogger/YouTuber/artist of dubious notability.

  • Geeksd37 uploaded File:Mike Kenji Hirai.jpg on October 29, deleted on November 4 as a Reddit copyvio.
  • Blackcat49219 uploaded an image to the same namespace on November 9, sourcing a single-purpose Flickr account.
  • After I tagged the image for deletion, Dnn8892 and AllIsDogs removed the deletion tag from the image ([1] and [2]) and Jddi820108 subtly vandalized the template ([3]).
  • I'm including Racoon3293882, whose only edit is uploading File:Mike Kenji Hirai em 2021.jpg on November 9, another social media copyvio.

Based on the single-purpose nature of these accounts, it would surprise me if they weren't working together/one person. Adeletron 3030 (talk) 13:54, 13 November 2023 (UTC)Reply[reply]

TongoGod[edit]

Status: resolved • view • edit • history • watch
Filed: 19:41, 11 November 2023 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: These users are uploading material protected by copyright and then using it in the same Spanish Wikipedia articles, under the same editing summaries. LuchoCR (talk) 19:41, 11 November 2023 (UTC)Reply[reply]

@LuchoCR: These are all SUL accounts that you've CU-blocked on es.wiki; why are you requesting a redundant check on the Commons? Эlcobbola talk 21:49, 11 November 2023 (UTC)Reply[reply]
@LuchoCR: Such a request would have a better reception at COM:ANB.   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 04:11, 12 November 2023 (UTC)Reply[reply]
  •  Not done - No response to the query above. If SUL accounts are found by a CU to be related on one wiki, there is no need for a redundant check on a sister project. RFCU is "the place to request investigations of abuse of multiple accounts [...] that require use of checkuser privileges" (underline added); if local clean-up/handling of such accounts is needed, requests can, and should, be made at the appropriate admin noticeboard. Эlcobbola talk 16:01, 14 November 2023 (UTC)Reply[reply]

Эlcobbola talk 16:01, 14 November 2023 (UTC)Reply[reply]

To The Beauty Within[edit]

Status:  to be archived • view • edit • history • watch
Filed: 20:34, 10 November 2023 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: User:Tronoptimus keeps uploading copyrighted photo of en:Soumitrisha Kundu. I and other users tagged those for deletion many times (User Talk:Tronoptimus). Now, "User:Opgstud" strated doing same. Most likely so that we won't noticed and won't tagged for deletion. I think they are same user. Please check. আফতাবুজ্জামান (talk) 20:34, 10 November 2023 (UTC)Reply[reply]

Unxed[edit]

Status:  to be archived • view • edit • history • watch
Filed: 12:33, 8 November 2023 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: After the user was suspected in intentional license laundering (Commons:Deletion requests/Files uploaded by Unxed), two brand new accounts were created to support his uploads. Komarof (talk) 12:33, 8 November 2023 (UTC)Reply[reply]

  • Declined - RFCU is for investigations of abuse of multiple accounts, not mere use--verily, "alternative accounts are not forbidden, so long as they are not used in violation of the policies" (m:CheckUser policy). No evidence of abuse or violation of policy is offered ("When you request a check, you must include a rationale that demonstrates [...] what the disruption to the project is" (underline in original)) or apparent. For example: Unxed is not blocked (the alleged socks are not bypassing a sanction); the alleged socks have not uploaded any files (no continuation of copyvios/LL); and the alleged socks have not commented at the DR (no double voting), or even on the same file. Characterisation of "two brand new accounts were created to support his uploads" is also incorrect; Vitaliybovar was created more than two years ago on 6 August 2021. Эlcobbola talk 15:19, 8 November 2023 (UTC)Reply[reply]

Porsche with no brakes 69[edit]

Status:  to be archived • view • edit • history • watch
Filed: 05:12, 5 November 2023 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: English Wikipedia vandal who was using VPN IPs to cover their tracks. I think it’s worth checking whether they used a VPN to create and use this account, which uploaded the images of erect penises used in the en-wp vandalism. Cheers, RadioactiveBoulevardier (talk) 05:12, 5 November 2023 (UTC)Reply[reply]

  • Declined - Notwithstanding that this is not a valid reason to run a check, these accounts 1) are ducks, 2) already blocked well before this request, and 3) the preceeding by a CU (!!!). Эlcobbola talk 12:00, 5 November 2023 (UTC)Reply[reply]

Ярмамедов Тимур[edit]

Status:  to be archived • view • edit • history • watch
Filed: 15:10, 1 November 2023 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: First three accounts banned as VOA (uploading hand-drawn fictional flags/coats of arms, which were soon added to articles in Russian WP by that IP). Last one registered today and doing same thing as and looks same. ДолбоЯщер (talk) 15:10, 1 November 2023 (UTC)Reply[reply]

Abayomi01[edit]

Status: resolved • view • edit • history • watch
Filed: 03:25, 28 August 2023 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: The sockmaster has uploaded a good number of images, though some (such as File:Adrian Perez Ramirez.jpg, File:WhatsA Image 202f3-08-25 at 3.23.08 AM (2).jpg, File:Filmfinity.jpg, File:WhatsApp Imag 2023-08-25 at 3.16.53 AM.jpg, etc.) have been deleted for a number of reasons, including copyright and use of commons to advertise. The master was given a warning for uploading out-of scope files the morning (UTC) of 27 August, and was given another warning for advertising at 16:37 that same afternoon. After receiving these warnings, the sockpuppet account was created at 23:15 on 27 August and proceeded to re-upload photos that had previously been uploaded by the master and had been deleted for scope or copyright reasons (i.e. File:Adrian Perez Ramirez (2).jpg, File:Adrian Perez Ramirez (3).jpg, File:WhatsApp Imae 2023-08-25 at 3.23.08 AM.jpg). As such, I suspect that the two accounts are connected in some way.

If these accounts are run by the same individual, this would appear to be a case of evasion of scrutiny on one's own uploads after having received multiple warnings, which would amount to disruption of Commons via the abuse of multiple accounts. As such, I am requesting a checkuser examine these accounts to evaluate the extent of technical connection between them. — Red-tailed hawk (nest) 03:25, 28 August 2023 (UTC)Reply[reply]

These two are likely the same person. However this conclusion is subject to the same caveat as 서울출장 below -- they are two of at least a dozen accounts (including those listed under 서울출장 below) that are likely students at the same institution. While these two quack like the same duck, I doubt that all of them are the same person. I have blocked Gajifast.     Jim . . . (Jameslwoodward) (talk to me) 13:35, 28 August 2023 (UTC)Reply[reply]

Also noting Abayomi43, who was blocked by Mdaniels5757 and was confirmed to master at an EnWiki SPI. I'm indefing the master. — Red-tailed hawk (nest) 03:47, 30 August 2023 (UTC)Reply[reply]
And also Sulitake01, who in their first three uploads re-uploaded an image previously uploaded by master. — Red-tailed hawk (nest) 03:54, 30 August 2023 (UTC)Reply[reply]
Noting that Mariaman81, who joined Commons this morning, is also uploading similar WhatsApp/garbled filenames and another photo of Adrian Perez Ramirez (File:Adrian Perez Ramirez (3).jpg). Belbury (talk) 10:56, 1 September 2023 (UTC)Reply[reply]
I've also blocked Walikomu for doing the same sort of thing as described above.
@Jameslwoodward: Would it be possible for a rangeblock to work here, or would there be too much collateral?
— Red-tailed hawk (nest) 14:08, 1 September 2023 (UTC)Reply[reply]
For posterity sake, I'm going to also make note of Ticket:2023083110009876. — Red-tailed hawk (nest) 14:26, 1 September 2023 (UTC)Reply[reply]
Another new sock account at Obaraka2, a few minutes ago. Belbury (talk) 15:16, 4 September 2023 (UTC)Reply[reply]

Matlin[edit]

Status: open • view • edit • history • watch
Filed: 10:29, 19 November 2023 (UTC)

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: Uploading lots of Flickr files without categorization. Matlin was blocked multiple times in 2021-2022 for mass-upload without proper categorization, Kukurydziarz seems created to avoid scrutiny and evade the blocks on using the F2C tool. Account was blocked on Wikidata as socks of Matlin, but there is not obvious enough to be directly blocked. Therefore, a check is required. A1Cafel (talk) 10:29, 19 November 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=823280410"