Shawwal ( talk ⁺ · tag · contribs · deleted contribs · logs · filter log · block user · spi block · block log · CA · CheckUser( log) · investigate · cuwiki)

10 April 2017

Suspected sockpuppets

• Samsparky ( talk ⁺ · tag · contribs · deleted contribs · logs · filter log · block user · spi block · block log · CA · CheckUser( log) · investigate · cuwiki)
• AbeEll ( talk ⁺ · tag · contribs · deleted contribs · logs · filter log · block user · spi block · block log · CA · CheckUser( log) · investigate · cuwiki)

• User compare report Auto-generated every hour.
• Editor interaction utility

As with Shawwal sock's, AbeEll, a user has notified me this account has similar behavior, especially at the one article's history they share. SwisterTwister talk 04:27, 10 April 2017 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.
Less than two weeks after the blocking of AbeEll, we have another one-purpose account suddenly showing up and only focusing on the Al-Ahbash article - the same exact single topic that AbeEll was blocked for. The article has been attacked by about a dozen sockpuppets over the past few years, all of them tendentiously editing to push the same exact POV. Considering the long history of successive chain sockpuppets on the Ahbash article, I find it hard to believe that, mere days after AbeEll gets blocked (see Wikipedia:Sockpuppet investigations/Followerofmuhammad/Archive), we now have another seemingly random editor show up and push the same exact POV that every single sockpuppet has been pushing on this article for the past few years. MezzoMezzo ( talk) 03:33, 11 April 2017 (UTC) reply

Samsparky's ID has been resurrected after 9/10 years of hiatus as soon as AbeEll got blocked following the same path and behavior of KevinAbdulqader. Samsparky's edits show that after its resurrection, it started doing its edits on Al-Ahbash (Mostly doing Mobile edits, Mobile web edits apart from the very first few regular edits) whereas AbeEll started with Abdullah_al-Harari (later on to Al-Ahbash), however, following the similar path, behavior and even using the same links, both of them ended up concentrating on the very same contentious, disputed and controversial topic. In a nutshell, Samsparky picked up exactly where AbeEII left from which in my humble point of view is rather suspicious. @ Bbb23: and @ GeneralizationsAreBad: were able to see through this in the case of AbeEll. Thank you. McKhan ^{( talk)} 14:33, 12 April 2017 (UTC) reply

@ DoRD:, Since the master is stale, Would it be helpful to run a CU of Samsparky parallel to AbeEll along with the behavior investigation? I am only saying it because Samsparky's ID was resurrected after 9/10 years of hiatus after AbeEll got blocked. Thank you. McKhan ^{( talk)} 15:11, 12 April 2017 (UTC) reply

I must strongly concur with McKhan's suggestion. Although I didn't open the SPI, my own main suspicion would have been for AbeEll since that was the most recently blocked sockpuppet. Behavioral evidence primarily aligns with Shawwal's various sockpuppets; the actual puppetmaster account was short lived, and the socks have been the accounts causing all the problems. I don't know how CUs function or how an account becomes stale, but would it still be possible to check Samsparky against AbeEll rather than Shawall? The behavior, the timing, and the history of this article all scream "duck". MezzoMezzo ( talk) 03:26, 20 April 2017 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

•  Check declined by a checkuser - The master is  Stale, so CU would be of little or no use here. — DoRD ( talk) 12:15, 10 April 2017 (UTC) reply
• Samsparky is  Unrelated. Closing.-- Bbb23 ( talk) 17:06, 22 April 2017 (UTC) reply