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

nothing found

Requests[edit]

Cyberpunk2077JohnnySilverhand[edit]

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: Both users uploaded similar files (see their upload logs). One of them is already blocked and locked. Zaxxon0 (talk) 22:27, 10 August 2023 (UTC)Reply[reply]

  •  It looks like a duck to me - Please report users uploading these images directly to ANB. Эlcobbola talk 00:01, 11 August 2023 (UTC)Reply[reply]

Di La Kwai[edit]

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: Special:Undelete/File:SU18BT2020.jpg, Special:Undelete/File:Solaris Urbino 18 IV Bratislava.jpg, File:Solaris Urbino 18 IV Bratislava.jpg, but not certain this is the same person because the username is, as far as I can tell (i.e. Google Translate), appropriate. A check for other accounts I may have missed may be useful as well. —‍Mdaniels5757 (talk • contribs) 00:23, 10 August 2023 (UTC)Reply[reply]

Proxies are involved, but from behaviour obvious A and B are the same LTA vandal (long-term based on the history of sk:Solaris Urbino 18 containing usernames like "Idiot bude Drbať fajku", "Rozserem Papulu a žerem hamburger", "Sedím na Záchode a Kakám debila", "On bude honiť retarda debila", going back to at least 2020.) Эlcobbola talk 00:50, 10 August 2023 (UTC)Reply[reply]
OK, thanks. Blocked the unblocked one where I could, oversight got the rest. —‍Mdaniels5757 (talk • contribs) 21:45, 10 August 2023 (UTC)Reply[reply]

طاهور الدريبي[edit]

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: See 1 and 2. --Karim talk to me :)..! 14:46, 7 August 2023 (UTC)Reply[reply]

TheOleRazzleDazzle[edit]

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: After the sockmaster's various creations on Commons were deleted for copyright related reasons (File:Sfv-court.jpg, File:Santa-ana-court.jpg, File:Northern-court.jpg, File:Riverside-court.jpg, and File:Los-angeles-court.jpg), and after the user was blocked on a sister wiki, the user created a new account to re-upload their deleted contributions back onto Commons (File:Sfv-bk-court.jpg, File:Santa-ana-bk-court.jpg, File:Northern-bk-court.jpg, File:Riverside-bk-court.jpg, and File:Los-angele-bk-court.jpg) respectively). Additional evidence that the two are connected is their shared interest in creating an english Wikipedia article about the United States Bankruptcy Court for Central California (see this log from the Master and Draft:United States Bankruptcy Court - Central District of California from the sock), a particularly niche topic that is related to each accounts' uploads on Commons.

If the two accounts are connected and run by the same person, this would amount to evasion of scrutiny on Commons because they were re-uploading files previously deleted for copyright issues. As such, I am requesting a checkuser examine the accounts to evaluate the extent of technical connection between them. — Red-tailed hawk (nest) 01:24, 7 August 2023 (UTC)Reply[reply]

  •  Technically indistinguishable - The IP belongs to an institution, so there exists the possibility that these are merely like-minded employees, but I think the additional context of the behaviour supports either being the same person or acting in coordination. A perhaps bigger issue is that there are several other accounts here, also editing in the same or similar topic areas; I would suggest an en.wiki SPI, as COI/non-disclosure of paid editing issues are of greater concern there. Эlcobbola talk 13:38, 7 August 2023 (UTC)Reply[reply]
    Thank you for running the check. I've opened the SPI on EnWiki. Please feel free to contribute more there if you would like, as you have more technical insight into what's going on here. — Red-tailed hawk (nest) 02:26, 8 August 2023 (UTC)Reply[reply]

WPK~commonswiki[edit]

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: Already banned on Finnish Wikipedia for being WPK sockpuppet. Reverting and overwriting files with unsourced edits. --Fenn-O-maniC (talk) 06:58, 5 August 2023 (UTC)Reply[reply]

  • Unless @Krd: has data from the previous check, the master (last edit 3 February 2013) and most recent listed sock (last edit 10 October 2022) would be Stale; there would be nothing to which to compare Posirom. (It's unclear whether there had been a CU on fi.wiki, but note for the future that, if there had been, CU results are valid across projects for SUL accounts.) Эlcobbola talk 14:05, 7 August 2023 (UTC)Reply[reply]

BlackLust[edit]

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: A die-hard Rossa fan who continuously uploading unfree images of the singer to Wikimedia Commons. Bluesatellite (talk) 11:54, 1 August 2023 (UTC)Reply[reply]

TheBellaTwins1445[edit]

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: Images only used to illustrate Spanish Wikipedia articles initiated by TheBellaTwins1445. Madamebiblio (talk) 00:43, 31 July 2023 (UTC)Reply[reply]

Antonio the Ant[edit]

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: Special:Undelete/File:Ethel Cain - Nylon Magazine 2022.webp vs Special:Undelete/File:Nylon Magazine % 281% 29.webp, both editing w:en:Ethel Cain too. —‍Mdaniels5757 (talk • contribs) 15:58, 30 July 2023 (UTC)Reply[reply]

  • Itsirlpidge is actually the older account (30 June 2023 v 20 July 2023). Despite being created later, Antonio the Ant made its single edit (upload) 20 July 2023 before Itsirlpidge ever edited the Commons (29 July 2023). Even if they are indeed related, which by behaviour certainly seems likely, I don't see that there is sufficient evidence of abuse of multiple accounts--the timeline and very minimal disruption (each account has effectively a single edit) looks more like confusion/inexperience than an attempt to deceive (skirt the scrutiny of the DR notice--which is, one notes, not even really a warning). As "Checkuser is a last resort for difficult cases" and one should "pursue other options first", why would warning each about misuse of multiple accounts not be a better approach at this stage? Эlcobbola talk 15:14, 31 July 2023 (UTC)Reply[reply]
OK, thank you for your consideration. —‍Mdaniels5757 (talk • contribs) 15:09, 2 August 2023 (UTC)Reply[reply]

Lucyspears[edit]

Suspected related users[edit]

Rationale, discussion and results[edit]

Singeronlyonetp was recently confirmed. One of the uploaded files was File:Vuongthuphuong2011.jpg. Now we have Minhanh44 who re-used this file name. It is not the former image but this was always the tactic in this case to retry it with different copyvios. The other uploads are likewise copyvios of the same model. --AFBorchert (talk) 16:03, 29 July 2023 (UTC)Reply[reply]

  • Confirmed to Lamgiakhang21, Singeronlyonetp, and Anhvuhp90. Some were incorrectly tagged with a master of Minhquoc12390, others were blocked for disruption other than sockpuppetry. I've now tagged all with Dungnguyen80 as the master. However, Dungnguyen80 itself is tagged as a sock of Lucyspears, as are other socks from older RFCUs. I've not investigated why this page is Dungnguyen80, or when/why a shift, if any, occurred. Someone may wish to sort this out. Эlcobbola talk 17:06, 29 July 2023 (UTC)Reply[reply]
    @Elcobbola: Thanks! Regarding your remark: This case was initially named Dungnguyen80 because this was the oldest sock when this was opened. We learned later on thanks to the investigations in other projects that the zoo is actually much larger and extends more into the past. Lucyspears is one of the more prominent older socks. However, as this case page has now been named after Dungnguyen80 it appears appropriate to link the new sockets to that account. --AFBorchert (talk) 17:25, 29 July 2023 (UTC)Reply[reply]
    @Elcobbola: Is also Lamgiakhang212 (talk contribs Luxo's SUL deleted contribs logs block user block log ) connected to this case? File:Lehangkcbdd1996.jpg was uploaded by Lamgiakhang212 and then subsequently edited by Lamgiakhang21 who removed the {{No permission since}} tag. --AFBorchert (talk) 17:34, 29 July 2023 (UTC)Reply[reply]
    Unfortunately, they are Stale; the last edit was 25 April 2023, just outside of the 90-day window. Эlcobbola talk 17:45, 29 July 2023 (UTC)Reply[reply]
  • I've now renamed this case after the assumed master account Lucyspears. All {{Sock}} templates have been updated accordingly and all known sockpuppets are now to be found in Category:Sockpuppets of Lucyspears. --AFBorchert (talk) 13:52, 30 July 2023 (UTC)Reply[reply]

Matteo sportelli[edit]

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: All these accounts share an interest in tall buildings leading to uploads of pictures where the height and the number of floors is marked in a very crudely fashion. All accounts have been blocked for disruptive editing in multiple projects including en:wp and it:wp. Cccccc4444 has been blocked by User:M7 at it:wp with the rationale Evasione del blocco. Hence it appears that this is a case of long-term abuse as indicated by HakanIST in their lock rationale. As these accounts claim their uploads to be their own works which they aren't, it would be helpful to see if there are more socks behind this. If the most recent account Ttttyyy 535 is indeed connected to this, that account should be locked like the other ones. --AFBorchert (talk) 15:26, 29 July 2023 (UTC)Reply[reply]

See also File:Central park tower.jpg where Retto654 and Usertttty 345 uploaded one of these pictures was re-uploaded by Ttttyyy 535 as File:Central park tower 472m.jpg. --AFBorchert (talk) 15:31, 29 July 2023 (UTC)Reply[reply]
That A = B = C is likewise confirmed. The global lock of User Bot 086 56 identifies Matteo sportelli as the master, so I have tagged accordingly. Matteo 270608 is Stale, but also globally locked as a Matteo sportelli sock. Эlcobbola talk 17:36, 29 July 2023 (UTC)Reply[reply]
This user has been blocked on it.wiki and will be blocked on sight as soon as his behaviour is recognized. Thank you for your effort. --M7 (talk) 20:00, 29 July 2023 (UTC)Reply[reply]

It didn't take long to see the next incarnation in this zoo: Tower 923 (talk contribs Luxo's SUL deleted contribs logs block user block log ). --AFBorchert (talk) 20:00, 30 July 2023 (UTC)Reply[reply]

  • Confirmed, of course, and no new sleepers. Given the distinctive behaviour, these can/should be blocked as ducks without a CU going forward. Эlcobbola talk 15:34, 31 July 2023 (UTC)Reply[reply]

Janitoalevic[edit]

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: Both accounts have worked collaboratively in the creation and uploading of material of non notable individual Gonzalo Townsend Pinochet, whom one of the accounts pretends to be. See contributions on the Spanish Wikipedia for reference. Bedivere (talk) 03:29, 28 July 2023 (UTC)Reply[reply]

Technically Unrelated. --Krd 06:37, 28 July 2023 (UTC)Reply[reply]

Anup Rajbanshi[edit]

Suspected related users[edit]

Rationale, discussion and results[edit]

Reason: 12gokinmk and 1govnvl are CU-confirmed on enwiki to this master (the SPI is w:en:Wikipedia:Sockpuppet investigations/Anup Rajbanshi). 2mere reuploaded one of their files (File:Narayan khadka.jpg vs Special:Undelete/File:Narayan Khadka.jpg) and has the same focus on Nepalese politicians. If confirmed, I can request the global lock(s). —‍Mdaniels5757 (talk • contribs) 02:42, 26 July 2023 (UTC)Reply[reply]

  • 2mere is Confirmed to 2merecljl (which, although not directly referenced in the en.wiki spi, is globally locked and blocked on en.wiki with a {{checkuserblock-account}} rationale as Anup Rajbanshi as the master). Эlcobbola talk 16:02, 27 July 2023 (UTC)Reply[reply]
    Blocked and requested lock. —‍Mdaniels5757 (talk • contribs) 22:51, 27 July 2023 (UTC)Reply[reply]

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