Wiki.RIP

Wikipedia:Sockpuppet investigations

From Wikipedia, the free encyclopedia

Administrator instructions

If you suspect sock puppetry by an administrator, or if you need to submit off-wiki evidence for some other reason, you must email the CheckUser team to open an investigation. Private information, emails, logs, and other sensitive evidence must not be posted on Wikipedia. All evidence related to a sockpuppet investigation must otherwise be posted on the designated page.
What is a sockpuppet?

This page is for requesting that we investigate whether two or more Wikipedia accounts are being abusively operated by the same person.

Before opening an investigation, you need good reason to suspect sock puppetry.

  1. Evidence is required. When you open the investigation, you must immediately provide evidence that the suspected sock puppets are connected. The evidence will need to include diffs of edits that suggest the accounts are connected. (This requirement is waived if the edits in question are deleted; in this case just provide the names of the pages that the accounts have been editing.)
  2. You must provide this evidence in a clear way. Vaguely worded submissions will not be investigated. You need to actually show why your suspicion that the accounts are connected is reasonable.

Investigations are conducted by a clerk, who will compare the accounts' behaviour and determine whether they are probably connected; this is a behavioural evidence investigation. Upon request, investigations can also be conducted by a CheckUser, who can look at the physical location of the accounts (and other technical data) in order to determine how likely it is they are connected; this is a technical evidence investigation.

Due to Wikipedia's CheckUser policy, CheckUsers will conduct a technical investigation only if clear, behavioural evidence of sock puppetry is also submitted; if you ask for technical evidence to be looked at but do not provide behavioural evidence, the investigation may not be allowed to proceed. Additionally, CheckUsers will not publicly connect an account with an IP address per the privacy policy except in extremely rare circumstances.

How to open an investigation:

To open an investigation (or case), enter the user name (or if there isn't one, IP address) of the oldest-created account (the "sockmaster"), or the previous case name, in the box below, then click "Submit". Note: Do not include "User:" or any other commentary.

For example, if the case name is about User:John Doe or a prior case was at Wikipedia:Sockpuppet investigations/John Doe, you should enter John Doe in the box below.

You will then be taken to another page containing a form you must complete to open the investigation. The process for opening a subsequent investigation on the same user is the same as for creating a new case. Again, do not include "User:" in any of the sock or ip fields.

If you also wish a CheckUser to investigate, change |checkuser=no to |checkuser=yes in the edit box on the next page and explain why you are requesting it.

Note: You can also open an investigation using Twinkle if you are autoconfirmed. After installing Twinkle, an "ARV" option will appear in the "TW" tab on any user, user talk, or user contributions page. Clicking on this option and selecting either "Sockpuppeteer" or "Sockpuppet" will allow you to fill in a few simple fields to file a report. The report will be automatically formatted for you.

If you are an anonymous (IP address) editor, and the case page is protected or does not exist, please click "show" to the right and use the box below

Cases currently listed at SPI

Investigation Status Filed at (UTC) Last user edit Last clerk/CU edit
User Time (UTC) User Time (UTC)
SyntheticAnomaly CU completed 2020-01-26 04:18 Berean Hunter 2020-03-01 03:03 Berean Hunter 2020-03-01 03:03
FixerFixerFixer CU completed 2020-01-30 01:31 Newslinger 2020-03-05 12:26 Bbb23 2020-03-03 14:25
Sidtever CU completed 2020-02-07 21:12 Cabayi 2020-02-19 12:08 Cabayi 2020-02-19 12:08
Veilderst CU completed 2020-02-10 03:33 Bbb23 2020-02-14 03:12 Bbb23 2020-02-14 03:12
Masterabhit CU completed 2020-02-22 04:08 DeltaQuad 2020-02-22 04:27 DeltaQuad 2020-02-22 04:27
Moksha88 CU completed 2020-03-13 19:36 KartikeyaS343 2020-03-25 14:24 DeltaQuad 2020-03-14 22:21
Gaudi9223 CU completed 2020-03-14 14:26 Bbb23 2020-03-14 18:34 Bbb23 2020-03-14 18:34
DoshNomad CU completed 2020-03-22 20:05 ST47 2020-04-03 01:19 ST47 2020-04-03 01:19
Ram sasankan CU completed 2020-03-27 04:41 Mz7 2020-03-30 21:30 Mz7 2020-03-30 21:30
Mhdsuhail111 CU completed 2020-03-31 18:36 ST47 2020-04-04 02:06 ST47 2020-04-04 02:06
Moditwenty CU completed 2020-04-06 11:14 ST47 2020-04-06 12:40 ST47 2020-04-06 12:40
Honest Yusuf Cricket CU completed 2020-04-07 07:04 SchroCat 2020-04-07 09:05 DeltaQuad 2020-04-07 08:52
AmlanDas Open 2020-03-01 18:21 GSS 2020-03-01 18:21
Kirston.ds Open 2020-03-04 00:54 Creffett 2020-03-04 00:54
Tabuhart Open 2020-03-05 15:22 Praxidicae 2020-03-05 15:22
NC-2017 Open 2020-03-09 22:46 Creffett 2020-03-09 22:47
Gonzal17 Open 2020-03-10 21:37 Epinoia 2020-03-10 21:37
Javaidrahi Open 2020-03-11 10:15 Daiyusha 2020-03-11 10:15
Buhedyar Open 2020-03-15 06:56 Materialscientist 2020-04-07 09:28 Materialscientist 2020-04-07 09:28
Bardrick Open 2020-03-20 21:23 FDW777 2020-03-20 21:23
Otto4711 Open 2020-03-26 00:25 SuperMarioMan 2020-03-26 00:25
Anupamacr Open 2020-03-30 09:45 GSS 2020-03-30 09:45
Brancojuan Open 2020-04-02 05:13 D.Lazard 2020-04-02 10:23
Juanafavour Open 2020-04-03 10:58 Newslinger 2020-04-03 10:58
Davefelmer Open 2020-04-05 05:31 KyleJoan 2020-04-07 08:41
Googleuser Open 2020-04-06 19:01 Bonadea 2020-04-07 07:11
Georgie 20 Open 2020-04-06 19:35 Ytoyoda 2020-04-06 19:35
Roayalrocky Open 2020-04-06 19:42 SemiHypercube 2020-04-06 19:42
Ritvik12 Open 2020-04-07 04:55 Aoi 2020-04-07 04:55
Craft37by More info req. 2020-03-16 10:55 Cabayi 2020-04-06 10:16 Cabayi 2020-04-06 10:16
REPARADOR Declined (CU) 2020-03-11 01:11 ST47 2020-03-11 01:23 ST47 2020-03-11 01:23
Jamesmiko Declined (CU) 2020-03-24 21:14 Mz7 2020-03-24 21:39 Mz7 2020-03-24 21:39
Tasase5 Declined (CU) 2020-04-06 21:25 Bradv 2020-04-07 05:17 Bradv 2020-04-07 05:17
Jan Zu Closed 2020-03-20 22:20 Cabayi 2020-04-06 10:04 Cabayi 2020-04-06 10:04

Quick CheckUser requests

Use this section to request checkuser information relating to a situation that does not involve sock puppetry. You could use this section to request, for example:
  • Underlying IPs of an account, where the autoblock has expired or been ineffective.
  • Collateral damage checks for the informed hardblocking of IPs or ranges.
  • IP block exemption checks before granting IPBE (or to verify it is being used constructively).

For threats of harm (to self or others) you must email emergency@wikimedia.org (see the threats of harm page) and not use this page. Requests to investigate and confirm sockpuppetry should be listed in the sockpuppet section above, and not here (such requests will be summarily removed).

To make a request here, copy the following template and paste it to the end of this section (quick link to edit) – replacing "header" with an informative title, and adding underneath the template any relevant information – then sign using "~~~~", preview, and click "save".

==== HEADER ====
{{SPIquick}}
* {{Checkuser|
username}}

Navboxes

What is Wiki.RIP There is a free information resource on the Internet. It is open to any user. Wiki is a library that is public and multilingual.

The basis of this page is on Wikipedia. Text licensed under CC BY-SA 3.0 Unported License..

Wikipedia® is a registered trademark of Wikimedia Foundation, Inc. wiki.rip is an independent company that is not affiliated with the Wikimedia Foundation (Wikimedia Foundation).

E-mail: wiki@wiki.rip
WIKI OPPORTUNITIES
Privacy Policy      Terms of Use      Disclaimer