Jump to content

Commons:Requests for checkuser

From Wikimedia Commons, the free media repository

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]

Synthxd

[edit]

Status: open • view • edit • history • watch
Filed: 19:20, 10 February 2025 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: Blatant self-promotion. They created c:Whake c:Category:Whake d:Q124213948 bm:Whake ca:Whake ceb:Whake co:Whake de:Whake en:Whake en:Draft:Whake es:Whake fr:Whake fy:Whake ht:Whake id:Whake is:Whake jv:Whake ln:Whake ln:Ciano Whake nl:Whake pt:Whake simple:Whake so:Whake xh:Whake yo:Whake which are deleted, some of them twice or 3 times. Yann suspected Synthxd to be Special:Contributions/Bombo but I don't think so because Bombo is probably from Switzerland and all of the IP edits on wikidata were from Brazil. --Achim55 (talk) 19:20, 10 February 2025 (UTC)[reply]

Lsfqueen1

[edit]

Status: resolved • 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]
Possible. Files tagged, range blocked. Krd 17:18, 10 February 2025 (UTC)[reply]

Sileudneseo

[edit]

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

[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]
Sorry, I mistyped. I've corrected it now. --Chiyako92 (talk) 08:42, 10 February 2025 (UTC)[reply]
Inconclusive or Unrelated. Krd 17:09, 10 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]


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=996817399"