Wikipedia:Sockpuppet investigations/Modern Fire/Archive

Add links
Source: Wikipedia, the free encyclopedia.


Modern Fire

Modern Fire (talk+ · tag · contribs · deleted contribs · logs · filter log · block user · spi block · block log · CA · CheckUser(log) · investigate · cuwiki)

17 June 2017

Suspected sockpuppets


First of all, the suspected sockmaster has been indefinitely blocked for disruptive editing. The suspected sockpuppet has been editing a number of articles formerly edited by the suspected sockmaster, as in these two extremely suspicious coincident edits from the two different users [1] and [2]. Please also note that the suspected sockpuppet has been reverting the reversions made by YSSYguy. Jetstreamer Talk 21:25, 17 June 2017 (UTC)[reply]

You may also want to take a look at
Alliance Air destinations history.--Jetstreamer Talk 21:42, 17 June 2017 (UTC)[reply
]

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.


Clerk, CheckUser, and/or patrolling admin comments

12 September 2017

Suspected sockpuppets

WorbTuscan, Indian Airlines and 73.222.239.57 are confirmed socks on fr:wiki of Freightcar2. Indian Airlines is a confirmed sock on en:Wiki of Modern fire. I blocked Freightcar2 for harassment of IP editors, a behaviour which APCX repeated. Looking at the recent history of the Air India article, Ruiss Jones, Royard9 and Ace505 seem to be involved too. The above, with the exception of the IP, have all added unsourced content to the Air India article, which I had cause to lock recently due to an edit war with an IP not implicated in this case. Mjroots (talk) 06:37, 12 September 2017 (UTC)[reply]

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

This has been dealt with, see Wikipedia:Sockpuppet investigations/Ace505 YSSYguy (talk) 07:31, 12 September 2017 (UTC)[reply]

@
WP:DUCK, check contribs. Mjroots (talk) 16:25, 15 September 2017 (UTC)[reply
]
I've indeffed Emben12, posted a uw-van3 on my talk page, which was the final confirmation I needed. Mjroots (talk) 16:54, 15 September 2017 (UTC)[reply]

Clerk, CheckUser, and/or patrolling admin comments

  •  Clerk endorsed other than the IP. All of these accounts are already blocked but please check for sleepers, it's apparent the sockmaster is deploying many of them. Ivanvector (Talk/Edits) 17:48, 15 September 2017 (UTC)[reply]
  • There's nothing else there. KrakatoaKatie got them all. --Deskana (talk) 09:32, 16 September 2017 (UTC)[reply]
  • Actually, I was wrong about that. Hold on. --Deskana (talk) 09:35, 16 September 2017 (UTC)[reply]
  • I looked at the data through a different angle, and I think that John bf (talk+ · tag · contribs · deleted contribs · logs · filter log · block user · spi block · block log · CA · CheckUser(log) · investigate · cuwiki) is related based on the behavioural evidence. There are quite a few other accounts in there that match and I believe are false positives, but that one in particular stood out. --Deskana (talk) 09:41, 16 September 2017 (UTC)[reply]
  •  Blocked and tagged. GABgab 15:31, 16 September 2017 (UTC)[reply]

09 September 2017

Suspected sockpuppets

Opened under the

Duck Test; Ace505 nominated as the master because his/her first edit on 5 August this year was a week prior to Freightcar2's first edit. Ace made no further edits after his/her first until 25 minutes after Freightcar2 got him/herself indef. blocked for bad behavior, whereupon Ace took up exactly where Freightcar left off. Ace's first edit was immediately undone by Serjinh81 [3], Freightcar's first edit (as I said, a week later) was to Serjinh81's Talk page [4]. Both Users seem to be way too experienced to be newbies - which of course does not preclude a history of editing as an IP, but as the degree of familiarity with WP includes creating User pages with Userboxes and because of the overlapping nature of edits, the whole thing has a bit of a stench about it so I am requesting a Checkuser to poke around under the log to see what comes out. YSSYguy (talk) 03:21, 9 September 2017 (UTC)[reply
]

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments

This case is being reviewed by Sro23 as part of the clerk training process. Please allow them to process the entire case without interference, and pose any questions or concerns either on their Talk page or on this page if more appropriate.

  • I think that's all the sleepers, but it's a big range. All blocked.  Clerk assistance requested: This needs to be merged into the Modern Fire SPI and tagged accordingly. Since there's crosswiki abuse as well, it would be a good idea to inform one of the stewards. Katietalk 00:07, 12 September 2017 (UTC)[reply]
  • I have just reverted vandalism here made by 73.222.239.57 (talk+ · tag · contribs · deleted contribs · logs · filter log · block user · spi block · block log · CA · CheckUser(log) · investigate · cuwiki), and this same IP attempted to blank/speedy nominate the Modern Fire sockpuppet category.[7]. This IP is also listed on the Modern Fire SPI. I also noticed that this vandalism was made in a few hours after the previous block in the IP had expired. Thus, I have applied a new block on this IP, as it appears that he is the only one editing from it. Zzyzx11 (talk) 05:53, 18 September 2017 (UTC)[reply]
  • Case merge complete and accounts tagged. RadiX, would you please consider locking globally per the request above? Also, the IP is anon-blocked currently and needs to be hardblocked globally as well.
     — Berean Hunter (talk) 16:40, 19 September 2017 (UTC)[reply]
All done. I've also globally blocked the IP ranges. The ranges are anon-blocked because there is high possibility of collateral damage. RadiX∞ 18:47, 19 September 2017 (UTC)[reply]
  • Thank you RadiX. I think we're done here now...closing.
     — Berean Hunter (talk) 00:42, 20 September 2017 (UTC)[reply]

21 September 2017

Suspected sockpuppets


The user is back editing airline articles without providing sources, particularly Alliance Air (India) [8] [9]. It's funny to see this sock reverting my edit and claiming I am a sock. Jetstreamer Talk 21:26, 21 September 2017 (UTC)[reply]

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.


Clerk, CheckUser, and/or patrolling admin comments

@Jetstreamer: I don't know what I'm supposed to see here. Please present evidence in the form of diffs that shows the sockmaster and suspected socks have made similar edits. NinjaRobotPirate (talk) 23:28, 21 September 2017 (UTC)[reply]

  • Nevermind, Oshwah blocked him after Leon blanked this page. Doesn't seem like there's anything left to do. NinjaRobotPirate (talk) 00:28, 22 September 2017 (UTC)[reply]


23 September 2017

Suspected sockpuppets

Pretty obvious sock, see attempted edit to userpage of another sock, plus these edits to articles subject to previous socking. Home Lander (talk) 18:42, 23 September 2017 (UTC)[reply]

Adding another sock that has popped up today. Home Lander (talk) 23:38, 25 September 2017 (UTC)[reply]
Adding a third sock that is already blocked. Home Lander (talk) 14:24, 26 September 2017 (UTC)[reply]

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.


Clerk, CheckUser, and/or patrolling admin comments

  • CU confirms B-787, Leon Shih, Mbox17. Drmies (talk) 23:41, 25 September 2017 (UTC)[reply]
    • Tagged and closing. GABgab 02:47, 26 September 2017 (UTC)[reply]

27 September 2017

Suspected sockpuppets

Same as before. Reverting everything that's already been undone. Home Lander (talk) 23:08, 27 September 2017 (UTC)[reply]

Added a second account, believe this is also a sock. See userpage constructed similarly to previous socks (including unusual redirect) combined with initial edit to previously targeted article. Home Lander (talk) 23:02, 29 September 2017 (UTC)[reply]
Adding a third, extremely obvious (even puts on user page about not being a Modern Fire sock). Home Lander (talk) 02:33, 1 October 2017 (UTC)[reply]
And another. Home Lander (talk) 03:00, 1 October 2017 (UTC)[reply]

The above accounts have now been blocked and/or globally locked, but by the time a CU is run, there could be other accounts created, so I'm leaving the CU request open for now. Home Lander (talk) 16:36, 1 October 2017 (UTC)[reply]

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.


Clerk, CheckUser, and/or patrolling admin comments

  •  Clerk endorsed - Has prior history of sleepers. QEDK (愛 • 海) 18:57, 5 October 2017 (UTC)[reply]

15 February 2018

Suspected sockpuppets

It appears they're back again. IP is editing same article areas and exhibiting same patterns as previous Modern Fire socks. See [10], where the only change is a space, but they warn about being blocked due to unsourced content. Geolocation comes back to a Comcast connection in Silicon Valley, same as blocked 73.222.239.57. A checkuser block is in their history; I'm assuming it's related to this case. Home Lander (talk) 00:36, 15 February 2018 (UTC)[reply]

...and requesting CU to check for sleepers after C.Fred blocked PlanespotterDreamliner. Home Lander (talk) 00:57, 15 February 2018 (UTC)[reply]
See [11] for a self-admission. Also, note, interestingly, that User:71.198.2.72 was recently created by Gotech8, who has been around since April 2014. Home Lander (talk) 01:35, 15 February 2018 (UTC)[reply]

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.


Clerk, CheckUser, and/or patrolling admin comments

 Confirmed and retagged. No other accounts seen. Closing.--Bbb23 (talk) 14:50, 16 February 2018 (UTC)[reply]

Retrieved from "https://en.wikipedia.org/w/index.php?title=Wikipedia:Sockpuppet_investigations/Modern_Fire/Archive&oldid=826191559"