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 (1 P)
Commons:Requests for checkuser/Case/Lsfqueen1

Requests

[edit]

Lsfqueen1

[edit]

Status: open • view • edit • history • watch
Filed: 08:47, 9 February 2025 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: Same pattern of uploading screenshots of members of K-pop girl group Le Sserafim as own works. Chiyako92 (talk) 08:47, 9 February 2025 (UTC)[reply]

 Comment I deleted all files as copyright violations. Yann (talk) 10:06, 9 February 2025 (UTC)[reply]

Sileudneseo

[edit]

Status: open • view • edit • history • watch

[edit]

Rationale, discussion and results

[edit]

Reason: Same user behavior pattern as the previous request. --Chiyako92 (talk) 08:46, 9 February 2025 (UTC)[reply]

Carry YUj is not registered on Commons. Yann (talk) 10:09, 9 February 2025 (UTC)[reply]


Trantrongnam~conmonswiki

[edit]

Status: open • view • edit • history • watch
Filed: 17:23, 7 February 2025 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: the same modus operandi as the sockmaster, from the obsession with flags to the reintroduction of factual errors such as here. M.Bitton (talk) 17:23, 7 February 2025 (UTC)[reply]

Sweetieje

[edit]

Status: resolved • view • edit • history • watch
Filed: 10:48, 7 February 2025 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: I came across this user and discovered several associated accounts. The first thing that stood out to me was the identical editing style across all accounts. Additionally, the metadata remains consistent, particularly in how the user uploads pictures. Hiyyihjaleh727 ㋡ Noran 노란색 ✎ ㋛ 10:48, 7 February 2025 (UTC)[reply]

Confirmed Sweetieje = Sophia099 = around 40 other accounts, all blocked and nuked.
Cereine is Possible. --Krd 11:25, 7 February 2025 (UTC)[reply]

爪丹了

[edit]

Status: resolved • view • edit • history • watch
Filed: 02:00, 7 February 2025 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: It's very obvious that this isn't Pierre Dolnick's first account - they come in, get some stuff listed for deletion - and immediately point to Commons hosting pornographic images to argue about the project scope. I don't know LTAs well enough to know who this is, but I indeffed them as a DUCK sock. However, I suspect that 爪丹了 is the same user, considering that their first edit since 2019 was finding this DR 90 minutes after it was created and arguing to keep the files. Looking for both confirmation about 爪丹了 before a block and for sleepers/Pierre Dolnick's original account. The Squirrel Conspiracy (talk) 02:00, 7 February 2025 (UTC)[reply]

Confirmed --Krd 08:05, 7 February 2025 (UTC)[reply]

Hakemsizlikti

[edit]

Status: resolved • view • edit • history • watch
Filed: 17:31, 5 February 2025 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: All the above users have the same exact behavior of uploading one AI generated image (they at first look quite convincing until zooming in and it's obviously AI generated), putting in the description some short fantasy story that reads like something generated by AI, adding in the source a link to a company's webpage with the image not actually existing in the disclosed source link, and categorizing them in Category:Picture books. Likely self-promotion/spam, although I'm not too sure if they are considered spammy or out of scope enough to list them all in a mass deletion request. Atomicdragon136 (talk) 17:31, 5 February 2025 (UTC)[reply]

Confirmed --Krd 17:41, 5 February 2025 (UTC)[reply]
4 accounts aren't blocked. All the Best -- Chuck Talk 01:18, 6 February 2025 (UTC)[reply]
Thank you! Now done. Krd 07:26, 6 February 2025 (UTC)[reply]

Roratowiec

[edit]

Status: resolved • view • edit • history • watch
Filed: 16:33, 5 February 2025 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: All reuploading File:Tłuszczyk.jpg for vandalism/harassment. Already blocked, but please check for sleepers and block the range. Thanks, Yann (talk) 16:33, 5 February 2025 (UTC)[reply]

Likely. Krd 17:04, 5 February 2025 (UTC)[reply]
 Info: I've blocked 2A00:F41:5800::/42 but I didn't see other ranges. --Achim55 (talk) 17:19, 5 February 2025 (UTC)[reply]

NeoArchivist888

[edit]

Status: resolved • view • edit • history • watch
Filed: 16:40, 4 February 2025 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: Each user is uploading files with very similar promotional descriptions, with links to the same website. See Commons:Administrators'_noticeboard/Blocks_and_protections#DUCK_socks? Most have been blocked already, but the blocking admin recommended a checkuser request to look for sleepers and to block the range(s). Marbletan (talk) 16:40, 4 February 2025 (UTC)[reply]

Confirmed. --Krd 17:30, 5 February 2025 (UTC)[reply]

Lidia Iscano

[edit]

Status: resolved • view • edit • history • watch
Filed: 23:17, 2 February 2025 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: Honduras Kratts reuploaded File:Coat of Arms Unnitella.png (original: File:Coat of Arms of Unnitella.png), File:Javoco FC (Surinam).png, File:Flag of Blue Birdsc (1981-2015).png, and File:Flag of Blue Birdsc.png (original: File:Blue Birdsc Flag.png). Salvadoreña Km reuploaded File:Flag of Guayana.png. All of these are hoaxes and the master is banned.

Honduras Navels uploaded the same logo but slightly differently at exactly the same time in Category:Blue Birdsc. Magog the Ogre (talk) (contribs) 23:20, 2 February 2025 (UTC)[reply]

Several users with related activity (based on contributions) are:
Omphalographer (talk) 09:32, 4 February 2025 (UTC)[reply]
All mentioned socks Confirmed to each other. Likely related to the mentioned master. --Krd 15:25, 5 February 2025 (UTC)[reply]

Tbcamishagentyal

[edit]

Status: resolved • view • edit • history • watch
Filed: 04:59, 4 February 2025 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: The new account name is similar as the previously blocked socks account. Still uploading spam advertising images. Astrinko (talk) 04:59, 4 February 2025 (UTC)[reply]

Likely. Dozens of socks blocked. --Krd 15:19, 5 February 2025 (UTC)[reply]


Oirattas

[edit]

Status:  to be archived • view • edit • history • watch
Filed: 00:48, 28 January 2025 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: WP:DUCK almost identical account names, posting identical "requests" on the same users' pages. Even analogous to the previous sock of Oirattas, Moroike. See the interaction analysis between his 3 accounts [1], it's very clear Orattas is his new sockpuppet - just one example out of many: Moroike makes a "request" to erase Republic of Artsakh/Nagorno-Karabakh from a map [2], shortly after is blocked globally like the master, Orattas then makes an identical request on the same user page again about erasing Republic of Artsakh from maps [3]: he did the same "requests" on ALL of his accounts and on multiple same users' talk pages. Even all the users' page requests are identical i.e. erasure of Republic of Artsakh from various historical maps, and many experienced users unknowingly that this is a sock, take up to these requests. I had already posted once in the blocking admin's page about the previous sock [4], so if possible @EPIC: , please take a look and block this new sock and please revert all the "request" map changes that this user has submitted, alot of which have been enacted on the respective maps by experienced users unknowingly that they're doing a sock's bidding. On his page where he showcases all his "efforts", you can find all the affected maps he requested to be changed [5]. I think his IP should be blocked too and he should be checked for other sleeper socks; this is clearly an abusive user who takes advantage of the system every time he gets locked by socking with other accounts and making experienced users unknowingly push his POV erasure of historical entities like the Republic of Artsakh from many many commons maps.

@Laurel Lodged: I saw your comments arguing with this user, you might be interested that this is an abusive sockpuppet who has been globally blocked on all his previous accounts. KhndzorUtogh (talk) 00:48, 28 January 2025 (UTC)[reply]

@Enyavar Hello. I saw you questioning Orattas as well [6]. Not only you're right that these maps have clear upload dates and are in historical context that don't need to be updated like current event maps, but this user has been on POV agenda pushing for months now and they're a long time abusive sockpuppet that was blocked globally on several accounts. Their new account, Orattas, will be blocked soon most likely once admins see this report, and all of their requests/changes need to be reverted as I explained above. Orattas shows the list of all the changes they requested/did in their new sock's user page [7]: and several of those that aren't even ticked, have been modified as well, all of which should be reverted to their stable versions prior to this abusive sock's agenda of erasing Republic of Artsakh/Nagorno-Karabakh from literally every commons maps (no matter the context) using multiple sock accounts to make these "requests". KhndzorUtogh (talk) 12:47, 29 January 2025 (UTC)[reply]
They made a request at my user page like they did on many others, and I gave my reasons there why I'm not inclined to fulfill them. It occured to me right away that if they ask a random editor for overwrite favors, they'd also ask other random editors to do the same. I checked some other contributions by Orattas and found that they did, but at least most of the other requests they filed were not unreasonable: Sometimes "people on a mission" have a point. The one you linked above was an egregious exception, like the one they asked of me. --Enyavar (talk) 13:59, 29 January 2025 (UTC)[reply]
@Enyavar they did make some requests outside the Nagorno-Karabakh republic erasure from maps, but I'm not familiar with these topics so I can't attest to their validity. However, the vast majority of their requests are associated with the erasure of Nagorno-Karabakh republic from every possible commons' maps with disregard to context and historical purpose, which is a political POV push. But most importantly, they shouldn't edit ANY wiki projects to begin with as they're clearly the global lock evading abusive sockpuppet of Oirattas (aka Moroike), I'm certain of this. Once Checkuser confirms this and this new sock gets locked, their requests/edits concerning Nagorno-Karabakh republic erasure should be reverted, which they so proudly display in their user page [8] (even some unticked requests regarding NK republic erasure have been done by oblivious to the situation users). KhndzorUtogh (talk) 15:01, 29 January 2025 (UTC)[reply]
Many thanks. Very interesting. I'm not at all surprised. Laurel Lodged (talk) 21:53, 29 January 2025 (UTC)[reply]
@Krd Hello. I noticed that you're the main clerk for sock cases in commons. Could you please check this one? I pinged the admin, @EPIC, who globally locked the previous accounts of this likely sock, but EPIC still hasn't responded for some reason. (I even left a note on their user page on Swedish wiki but still no response). Orattas, the likely sock, now not only canvasses in commons for other users to do his tasks, but also canvasses in other wiki projects to enforce erasure of Nagorno-Karabakh republic from every map possible with complete disregard to context like Enyavar described here [9], [10]. If it is confirmed that this user has been the abusive globally locked sock all along (which I'm certain he is), could you revert all their Nagorno-Karabakh republic erasure requests/changes that they so proudly display on their page [11]? Even some unticked ones in regard to NK republic erasure have been done by oblivious users. KhndzorUtogh (talk) 11:35, 30 January 2025 (UTC)[reply]
@Krd @Laurel Lodged @Enyavar this isn't just commons/cross-wiki canvassing POV push anymore, this is now also a targeting campaign based on ethnic backgrounds: look at the subsequent comments they're leaving in this az-wiki admin's page [12], just unhinged behavior. This person needs to be checked for socking and locked globally if it's confirmed to be the global lock evading Oirattas (which they almost certainly are). Their "requests" need to be reverted too since they are canvassing sock's agenda and out of context POV, pretending as if there are no upload dates on these maps, historical purpose, etc. [13], [14]. Oirattas should also be checked for sleeper socks in case they made more accounts to sock with. KhndzorUtogh (talk) 14:48, 30 January 2025 (UTC)[reply]

Oirattas is stale, nothing to compare. Next time please comply with the procedure outlined at Commons:Requests for checkuser. --Krd 10:21, 31 January 2025 (UTC)[reply]

Moroike is technically Unrelated --Krd 13:37, 31 January 2025 (UTC)[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=996081101"