Page semi-protected

Wikipedia:Sockpuppet investigations

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search

Administrator instructions

If you suspect sockpuppetry 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 sockpuppetry.

  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.
  3. Concision is key. Evidence should be presented in a concise format. Because of the length of the backlog, cases with clear and concise explanations and evidence are handled the most quickly.

Investigations are conducted by a clerk or an administrator, 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 sockpuppetry 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)
Jujjavarapu mohith Endorsed 2022-02-16 11:12 Pikavoom 2022-02-17 06:36 Girth Summit 2022-02-16 17:11
Ojnist CU requested 2022-02-14 22:02 MarioGom 2022-02-17 16:45 Oshwah 2022-02-16 02:54
Shikagami03 CU requested 2022-02-15 14:37 Finngall 2022-02-17 17:27
MxonlightTea CU requested 2022-02-15 23:36 Yosemiter 2022-02-15 23:36
Antonian Sapphire CU requested 2022-02-16 23:22 Horse Eye's Back 2022-02-17 03:34
JesusJohnson7 CU requested 2022-02-17 04:13 Chipmunkdavis 2022-02-17 04:13
Cbijampan CU requested 2022-02-17 14:26 Mvqr 2022-02-17 14:27
Nediyakala Vasavan CU requested 2022-02-17 16:52 Sdrqaz 2022-02-17 16:52
Escoperloit CU requested 2022-02-17 17:22 Cordless Larry 2022-02-17 17:22
D4rkeRR9 CU requested 2022-02-17 18:35 M.Bitton 2022-02-17 18:51
Krystalgreat CU requested 2022-02-17 20:02 Celestina007 2022-02-18 01:37
Ojy Okpe CU requested 2022-02-17 22:58 Celestina007 2022-02-17 23:13
Ineedtostopforgetting CU requested 2022-02-18 01:33 Justanothersgwikieditor 2022-02-18 01:33
Pramit4isb CU requested 2022-02-18 01:44 AngusWOOF 2022-02-18 01:46
Swarup Kumar Solanki Awaiting admin 2022-02-04 12:55 Blablubbs 2022-02-14 16:28 Blablubbs 2022-02-14 16:28
Isuzu.tf Awaiting admin 2022-02-17 00:07 Spicy 2022-02-17 08:55 Spicy 2022-02-17 08:55
Khaliwarriors Awaiting admin 2022-02-17 08:42 Spicy 2022-02-17 09:04 Spicy 2022-02-17 09:04
Zessede Awaiting clerk 2022-02-10 12:52 RoySmith 2022-02-12 13:26 RoySmith 2022-02-12 13:26
Kontolpanjang Awaiting clerk 2022-02-13 09:38 Girth Summit 2022-02-13 15:35 Girth Summit 2022-02-13 15:35
KJ332 CU completed 2022-02-07 20:11 Dreamy Jazz 2022-02-11 22:03 Dreamy Jazz 2022-02-11 22:03
Jiboner&to CU completed 2022-02-11 00:24 RoySmith 2022-02-14 16:39 RoySmith 2022-02-14 16:39
Injamul Haque Molla CU completed 2022-02-13 01:50 RoySmith 2022-02-13 02:57 RoySmith 2022-02-13 02:57
Gounder parambarai CU completed 2022-02-14 22:54 RoySmith 2022-02-15 14:41 RoySmith 2022-02-15 14:41
WRRichter1 CU completed 2022-02-15 15:06 RoySmith 2022-02-15 16:59 RoySmith 2022-02-15 16:59
摂南太郎 CU completed 2022-02-15 20:30 Girth Summit 2022-02-15 20:58 Girth Summit 2022-02-15 20:58
Qwerty123uiopl CU completed 2022-02-16 18:50 Dreamy Jazz 2022-02-17 18:49 Dreamy Jazz 2022-02-17 18:49
Pitzzaboy CU completed 2022-02-16 23:24 192.76.8.77 2022-02-17 20:34 RoySmith 2022-02-17 19:53
Muhammadyeakubhasan111 CU completed 2022-02-17 03:04 Girth Summit 2022-02-17 11:30 Girth Summit 2022-02-17 11:30
ZemenfesKidus Open 2022-02-15 06:56 Magherbin 2022-02-15 06:56
Jagdeep singh bittu Open 2022-02-15 14:14 Ravensfire 2022-02-15 14:14
Hassanalburu Open 2022-02-15 15:12 EN-Jungwon 2022-02-15 15:12
Immirzakhan Open 2022-02-15 17:23 Praxidicae 2022-02-15 17:23
Sinwiki12 Open 2022-02-16 07:39 Estnot 2022-02-16 07:39
Rasheed Hasrat Open 2022-02-16 09:25 Curb Safe Charmer 2022-02-16 09:29
Sunderland Renaissance Open 2022-02-16 23:17 Bbb23 2022-02-17 14:07
Jellywings19 Open 2022-02-17 07:40 Rzxz0839 2022-02-17 07:40
2600:1700:E371:7640:197C:85D3:6F55:B6D6 Open 2022-02-17 17:25 Friedlemon 2022-02-17 17:34
Zessede Closed 2022-02-10 12:52 RoySmith 2022-02-12 13:26 RoySmith 2022-02-12 13:26
Rogeman123 Closed 2022-02-13 22:50 Spicy 2022-02-16 11:03 Spicy 2022-02-16 11:03
2001:16B8:A515:C800:A84A:B5D3:49CB:2288 Closed 2022-02-14 13:11 Spicy 2022-02-14 15:40 Spicy 2022-02-14 15:40
Manishrajput6395 Closed 2022-02-14 16:25 Spicy 2022-02-16 11:32 Spicy 2022-02-16 11:32
Prehistoricplanes Closed 2022-02-14 19:40 Jo-Jo Eumerus 2022-02-16 12:59 Spicy 2022-02-16 11:29
Fatima.Innovative Closed 2022-02-15 04:15 Girth Summit 2022-02-15 19:51 Girth Summit 2022-02-15 19:51
112qw34er Closed 2022-02-15 08:14 IJBall 2022-02-15 23:25 Spicy 2022-02-15 21:20
Robert Moore Closed 2022-02-15 10:02 RoySmith 2022-02-16 15:24 RoySmith 2022-02-16 15:24
Problemsmith Closed 2022-02-15 16:28 Spicy 2022-02-17 08:31 Spicy 2022-02-17 08:31
MikePlant1 Closed 2022-02-15 19:29 Blablubbs 2022-02-17 21:43 Blablubbs 2022-02-17 21:43
Vaibhav678 Closed 2022-02-15 20:34 Spicy 2022-02-16 16:59 Spicy 2022-02-16 16:59
Dusty8686 Closed 2022-02-16 00:54 Girth Summit 2022-02-17 11:08 Girth Summit 2022-02-17 11:08
Ylevental Closed 2022-02-16 03:51 Liz 2022-02-17 06:30 Spicy 2022-02-16 10:53
Wiki-expert-edit Closed 2022-02-17 00:06 Casualdejekyll 2022-02-17 13:35
PostcolonialLitNerd Closed 2022-02-17 07:07 Spicy 2022-02-17 18:26 Spicy 2022-02-17 18:26
Kevinpierrejean Closed 2022-02-17 07:46 Jack Frost 2022-02-17 19:05 Jack Frost 2022-02-17 19:05
Pri2000 Closed 2022-02-17 10:40 PhilKnight 2022-02-17 13:06 PhilKnight 2022-02-17 13:06
BarbieFilmLover Closed 2022-02-17 18:19 Blablubbs 2022-02-17 19:31 Blablubbs 2022-02-17 19:31
Pallikanti Closed 2022-02-17 21:15 Sir Sputnik 2022-02-17 22:45 Sir Sputnik 2022-02-17 22:45
Ilovetrevordaniel Closed 2022-02-17 23:14 TheresNoTime 2022-02-18 00:07 TheresNoTime 2022-02-18 00:07
Add a little bit of spice Closed 2022-02-17 23:25 Bbb23 2022-02-17 23:31


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