Steward requests/Global

From Meta, a Wikimedia project coordination wiki
< Steward requests
This is an archived version of this page, as edited by Cromium (talk | contribs) at 11:27, 4 April 2018 (→‎Global lock for LTA Black magic specialist spammer (4): d). It may differ significantly from the current version.

Latest comment: 6 years ago by There'sNoTime in topic Requests for global (un)lock and (un)hiding
Shortcut:
SRG
This page hosts requests for global (un)blocks, (un)locks and hidings.

If you are here because you have been affected by a global block, please see Global blocks/FAQ for more information about global block and routes to appeal.

Note: (un)blocks apply to IP addresses; and (un)locks apply to global accounts.


Cross-wiki requests
Meta-Wiki requests


Requests for global (un)block

Latest comment: 6 years ago18 comments9 people in discussion
Please be sure to follow the instructions below:
Your request might be rejected if you don't follow the instructions.
Please also review Global blocking . Only IP addresses can be globally blocked at this moment. Please see #Requests for global (un)lock and (un)hiding if your request involves an account.
Global blocks don't affect Meta-Wiki, so if your IP address is blocked, you can still appeal here. IP addresses that cause disruption on Meta should be reported at Meta:Requests for help from a sysop or bureaucrat instead of here so that they can be blocked locally.
Please describe the kind of cross wiki abusive activity you see from the IP. Saying an IP is a long term abuser is not helpful, but saying "IP vandalizes at ban.wikipedia, no.wikipedia and vi.wikipedia" is. This is especially important for range blocks. If you do not provide enough details, your request might be declined.
Instructions for making a request

Before requesting, make sure that:

  1. You know the IP address(es) you wish to have globally blocked or unblocked.
  2. For blocks, the global blocking criteria are met.
  3. For unblocks, your request addresses the original reason for blocking the IP, if any.

To make a request for the address(es) to be blocked or unblocked

Copy the template below to the bottom of this section and explain why the address(es) should be blocked/unblocked.
=== Global block/unblock for [[Special:Contributions/Some IP address|Some IP address]] ===
{{Status}} <!-- Do not remove this template -->
* {{Luxotool|IP address}}
Description, evidence, diffs, etc. --~~~~
When requesting that your IP be unblocked, note that stewards need to know your IP address to even consider a request.
To find your IP, please visit https://www.whatismyip.com/
You are not required to disclose your IP in public - you may make requests privately to any steward on IRC or by email at: stewards@wikimedia.org

Global block 2600:8800:3000:0:0:0:0:0/36

Status:    In progress

Block evasion by globally locked user MisterAnthony. He has been occasionally active on Interlingua wikipedia as various IPs since the locking of his named account:

with a sudden recent flurry of activity:

His signature on iawiki is the creation of micro-stub articles for U.S. actors, each containing one sentence in Interlingua and another in Spanish, partly redundant with the first (ia:Special:Diff/592001). The wikidata item histories indicate he creates similar fill-in-the-blanks micro-stubs for the same actor in dozens of other small languages, together with messing around with wikidata itself.

I havve blocked the /36 on iawiki for 6 months and don't expect collateral problems, based on the size of iawiki and observation of the contributions in the range. There have been previous global blocks within the range:

The 3081 range above is probably stale. The 3080 and 3982 have received blocks as just mentioned. The 3981 is new. If /36 is excessive for a global block, may I suggest:

(Incidentally, a new named account has just appeared: AnthonyAW. Even with only 4 edits, it looks like a sock of this user. Will bear watching.)

--Tortoise0308 (talk) 19:25, 11 January 2018 (UTC)Reply

Global block for the boy band vvandal

Status:    In progress

Cross-wiki vandal (see also en:Wikipedia:Long-term_abuse/Boy_band_vandal) active for more than 10 days. --Horcrux92 (talk) 08:36, 31 January 2018 (UTC)Reply

Could somebody please action this? Also 2001:56a:f580::/41 would need to be blocked, per the last requests linked from the abuse report. Graham87 (talk) 07:16, 27 February 2018 (UTC)Reply
Also, account creation should be allowed, due to collateral damage. I've just found out that the strongest block will apply for IP addresses which have been both locally and globally blocked, so if account creation were disabled in the global block, that would undo the account-creation-enabling effect of the local one. Graham87 (talk) 16:15, 1 March 2018 (UTC)Reply
Graham87, that is not possible: "Global blocks should, wherever practicable and sensible, be placed with the anonymous only flag on. Remember that even in this case account creation from the blocked address(es) is prevented." @ Global blocks. Emphasis mine. — regards, Revi 10:39, 24 March 2018 (UTC)Reply
@Revi: Ah OK; thanks for letting me know. I'd only heard one report of collateral damage in a year, so ... meh. Graham87 (talk) 13:31, 24 March 2018 (UTC)Reply
Also add 2001:56a:f104:b300::/64 and 75.159.116.143 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye to the list. Graham87 (talk) 19:00, 1 April 2018 (UTC)Reply

Global block for 187.45.179.164/31

Status:    In progress

A leaky hosting (hostdime.com). The former IP is blocked in zh.Wikipedia as a proxy. The latter IP is currently trolling on Commons. Incnis Mrsi (talk) 16:41, 21 March 2018 (UTC)Reply

Global block for 80.243.185.128/25

Status:    In progress

A leaky colocation hosting blocked in en and zh.wikipedias. 80.243.185.144 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye was recently used on Commons to make personal attacks (likely by a globally banned person). Incnis Mrsi (talk) 16:59, 21 March 2018 (UTC)Reply

Global block for 67.188.179.66

Status:    In progress

Edited in fr,en,zh,es,vi,ru wikis.I noticed he likes editing war, it does not matter now.

123
I care about these three links. These three links tell us that 67.188.179.66 said that the first and third links were wrong. But the first link was edited by 67.188.179.66. Only two possibilities, he was disturbing in ZH or he used 107.77.213.166 negating his own edit . --O1lI0 (talk) 05:04, 25 March 2018 (UTC)Reply

Global block for 2605:380:32:495:43F2:A1::/96

Status:    In progress

Please, hard-block for a year. It seems to me that the entire /96 IPv6 range, or at very least 2605:380:32:495:43F2:A1::/112 xwiki-contribs • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye—216 addresses—is allocated to a globally banned long-term abuser or somebody impersonating him. See c:Special:Contributions/2605:380:32:495:43F2:A1::/112 for details, note two distinct IPv6s. Incnis Mrsi (talk) 19:29, 26 March 2018 (UTC)Reply

From a theoretical point of view minimum prefix length to block should be 64 bits. --Vituzzu (talk) 19:32, 26 March 2018 (UTC)Reply
Blocked IPv6 prefixes both broader and narrower than /64 exist in Wikimedia. The former are up to /32 which is rather common in en.Wikipedia. The latter are usually point blocks (/128), but sometimes /96. From my layman’s understanding, IPv6 prefix specification may “theoretically” be any integer from /0 to /128 inclusively, although MediaWiki refuses to handle anything broader than /32 for security reasons. If one can mount a valid objection against blocking this /96—an insignificant portion of all IPv6 Internet—then formulate it clearer, please. I have difficulty comprehending an oracle’s remark above. Incnis Mrsi (talk) 21:02, 26 March 2018 (UTC)Reply

Global block for 106.187.0.0/16

Status:    In progress

Colocated webhosts with open proxies and active blocks on 10 wikis.   — Jeff G. ツ 12:56, 29 March 2018 (UTC)Reply

@Jeff G.: I see 106.187.0.0/18 xwiki-contribs • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye and 106.187.96.0/21 xwiki-contribs • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye blocked in en. in ru.wikipedias, but these ranges combined are more than three times smaller than /16. In which namely wikis such large range as /16 is blocked? In any case, a more solid substantiation should be presented for request to block 216 IPv4 addresses. Incnis Mrsi (talk) 06:22, 30 March 2018 (UTC)Reply
@Incnis Mrsi: Please see this block log (in Japanese) at Japanese Wiktionary.   — Jeff G. ツ 10:29, 30 March 2018 (UTC)Reply

Global blocks for spambot webhosts

Status:    In progress

Webhosts used by spambots. MER-C (talk) 12:18, 30 March 2018 (UTC)Reply

IPVanish VPN used for spamming. MER-C (talk) 13:59, 30 March 2018 (UTC)Reply

Requests for global (un)lock and (un)hiding

Latest comment: 6 years ago103 comments25 people in discussion
Note that global blocking currently only applies to IPs, due to a technical limitation. If you wish to request a named account for global [un]locking, please request a global [un]lock here instead. Be sure to follow the instructions below:
  • Your request might be rejected if it doesn't include the necessary information.
  • Warning! This page is publicly viewable. If the account name is grossly insulting or contains personal information please contact a steward privately in #wikimedia-stewardsconnect or email your request to the stewards VRT queue at stewards-oversight@wikimedia.org (direct wiki interface) but do not post it here. Thanks.
  • Warning! This is not the place to ask for locks based on your opinion that someone is disruptive. Global locks are used exclusively against vandalism and spam, not because of content disputes, not because you think that someone deserves to be globally blocked. In such cases, you should ask for local blocks at appropriate places.
  • If you are globally locked, you should appeal your lock to stewards-appeals@wikimedia.org.

Please describe abusive activity of an account before reporting them here. Since stewards are often not active at projects the reported accounts are, things that seem obvious to you may not be equally obvious to the reviewing steward.

Instructions for making a request

Before requesting that a global account be (un)locked, please be sure that:

  1. You have evidence of cross-wiki disruption from the account(s).
  2. You can show that it is not feasible to use local-only blocks or other measures like page protection to combat the disruption.
  3. You have considered making the request in #wikimedia-stewardsconnect, especially for account names which will be hidden, or for urgent requests.
To make a request for an account to be locked or unlocked
Copy one of the codes below to the bottom of this section and explain why the account(s) should be locked/unlocked.
=== Global lock/unlock for Foo ===
{{status}} <!-- do not remove this template -->
* {{LockHide|username}}
* {{LockHide|username|hidename=1}} <!-- if you do not want the name to be visible on this page -->
*...
Reasons, etc. --~~~~

For many accounts: 

=== Global lock for spambots/vandals ===
{{status}} <!-- do not remove this template -->
{{MultiLock|username|username2|username3}}
{{MultiLock|username|username2|username3|hidename=1}} <!-- if you do not want the names to be visible on this page -->
*...
Reasons, etc, --~~~~

Global lock for LTA User:IPhonehurricane95 socks

Status:    In progress

Recent (within the last 3 years) unlocked IPhonehurricane95 socks. The accounts have pretty much been CU confirmed or given away by behavior. For the Stewards who remember, IPhonehurricane95 was a very severe vandal with massive article vandalism, personal attacks, profanity, 9/11 imagery vandalism, and serial socking. He also inspired the vandal (User:Lightning Sabre) behind the recent UnderArmourKid sock family. There has been evidence that he has continued IP socking within the last 2 years, possibly even as recently as yesterday (see the UnderArmourKid SPI Case for the possible IP sock). Since IPhonehurricane95 is known to log back into his older socks and vandalize across multiple Wikimedia Project sites, I'm requesting that all of these sock accounts are Locked. Also, it has been standard practice to Globally Lock all IPhonehurricane95 sock accounts. LightandDark2000 (talk) 12:43, 16 February 2018 (UTC)Reply

Here is IPhonehurricane95's SPI archive, for anyone who needs a refresher, and this is a CU check result on Commons. Most of the veteran users on Wikipedia's WikiProject Tropical Cyclones remember IPh95 (most of the senior editors and admins have been attacked by him as well), as well as a handful of Stewards and Ex-Stewards, especially during his vandalism spree in 2014. LightandDark2000 (talk) 01:33, 18 February 2018 (UTC)Reply

@LightandDark2000: (it has been standard practice to Globally Lock all IPhonehurricane95 sock accounts) How? IPhonehurricane95 account itself not locked! also did IPhonehurricane95 made any vandalism on wikis than enwiki? --Alaa :)..! 10:39, 21 March 2018 (UTC)Reply

@Rschen7754: what is you opinion here as you previously deal with this sock master? --Alaa :)..! 10:42, 21 March 2018 (UTC)Reply
I am reluctant to comment as I have not followed this in recent years (though I can say that it was crosswiki). Perhaps @Trijnstel: remembers? I think there is CUwiki stuff too. --Rschen7754 18:30, 21 March 2018 (UTC)Reply
Alaa: IPhonehurricane95's master account was not locked because the account was not global (only exists on the English Wikipedia), and maybe also to allow him to make unblock requests via WP:UTRS. I'm not really sure why; I wasn't a part of any Steward discussions regarding this sockmaster. By the way, the Stewards did have a policy of Globally Locking all of IPhonehurricane95's sock accounts back in 2014, because he had a history of logging back into blocked accounts to attack other users, and to use the accounts to vandalize other project sites across the Wikimedia sites. By the way, IPhonehurricane95 continued to vandalize in 2015 and 2016, and there is evidence that he continued IP socking in 2017 (and possibly in February 2018 as well). In addition, IPh95's long history of cross-wiki vandalism and personal attacks warrants a Global Lock on all of his socks. As Rschen7754 stated above, there are Stewards and CUs who remember this sockmaster, and if you were to ask any senior user or admin on WikiProject: Tropical cyclones on the English Wikipedia, they would all remember as well, because each of those users (including me) were attacked repeatedly by IPh95. LightandDark2000 (talk) 22:43, 22 March 2018 (UTC)Reply
@علاء and Rschen7754: I've left a note on the user talk page of you, Alaa, on the CU wiki. Please take a look. Trijnsteltalk 22:20, 23 March 2018 (UTC)Reply
Thanks @Trijnstel: I'll take a look --Alaa :)..! 13:56, 25 March 2018 (UTC)Reply

Global lock for Cavidan Isgender

Status:    In progress

Cross-wiki vandalism. In addition, this user is inciting violence on multiple Wikimedia sites (this user is calling for an Azerbaijani violence/revolution). This user needs to be Locked before he can cause any further damage. LightandDark2000 (talk) 12:26, 23 March 2018 (UTC)Reply

He is still calling for violence, this time on the Az Wikipedia. Someone needs to head there and revert his edits, and delete his created pages (the ones that are inciting violence), as necessary. LightandDark2000 (talk) 12:54, 23 March 2018 (UTC)Reply
@Cekli829 and Babək Akifoğlu: can you assess the user edits on azwiki? Also @-revi and Billinghurst: on commons please? --Alaa :)..! 14:00, 25 March 2018 (UTC)Reply
Portraits are definitely suspicious by their quality of images (smelling not-own) but not sure about the xwiki vandalism. — regards, Revi 14:07, 25 March 2018 (UTC)Reply
The user in question was calling for violence in Azerbaijan on the English Wikipedia (and setting up pages dedicated solely to his "calls to violence"). Given the context of the edits and page creations on the Az Wikipedia, I assume that he was doing the same thing there too. Calling for actual violence/killing is not something that we should allow, and since this issue appears to be cross-wiki, I think that a Global Lock would be appropriate here. LightandDark2000 (talk) 19:20, 25 March 2018 (UTC)Reply

Global unlock for JoeyPknowsalotaboutthat

Status:    In progress

User is very apologetic (see this) and persistently claims puppets were his friends who wanted to cause trouble (see this and this) unlike Joey himself, who wants to build an encyclopedia. It was his friends, not him, who wanted to abuse multiple accounts. User:Ilikechristians should remain locked for intentional cross-wiki abuse. --Daniel "Danny" Wilson (talk) 18:22, 24 March 2018 (UTC)Reply

I would ask any reviewing Steward to review the CheckUser data and the behavior/claims of the accounts before considering unlocking any of the accounts. Cross-wiki abuse is evident, and something doesn't look right here. LightandDark2000 (talk) 04:56, 24 March 2018 (UTC)Reply
@Ruslik0: --Alaa :)..! 14:07, 25 March 2018 (UTC)Reply
This is a variant of en:Wikipedia:My little brother did it. Ruslik (talk) 19:33, 26 March 2018 (UTC)Reply
@Ruslik0, don't just make assumptions based on the IP address. Maybe Joey's friends (not Joey himself) could be the ones abusing accounts! --Daniel "Danny" Wilson (talk) 03:16, 27 March 2018 (UTC)Reply

Global lock for Wan Yasser Gianov

Status:    In progress

New sock of Adam aflah which is globally locked. -ArdiPras95 (talk) 21:49, 26 March 2018 (UTC)Reply

@ArdiPras95: how you determine the relationship between this account and Adam aflah? --Alaa :)..! 11:52, 30 March 2018 (UTC)Reply

Global lock for 26 socks of Altman

Status:    In progress

Altman (talk · contribs) is a cross-wiki sockmaster deceiving en. and fr.wikipedias, as well as Wikimedia Commons. All socks are blocked in tagged in en.Wikipedia, and Daewoo Kim is also blocked on Commons. Sources for the list: w:Wikipedia:Sockpuppet investigations/Altman/Archive #17 February 2018 and w:Wikipedia:Sockpuppet investigations/Altman. Incnis Mrsi (talk) 09:12, 27 March 2018 (UTC)Reply

Global lock for LTA ROXELANA22 sockfarm

I've included all of the known sockpuppets from ROXELANA22's earlier sockfarm: Macallla (this account was Globally Locked and Hidden in 2008); I've excluded the socks that were already Locked. In this personal attack on my Commons talk page, ROXELANA22 pretty much confesses that his oldest account is User:Anibal1, which should be Locked as well (as the sockmaster). Given the fact that ROXELANA22 was able to re-activate User:Antiantps43 (his 3rd-oldest sock account) after 6 years of inactivity, and also given the personal attack on my talk page that I've linked earlier, it's quite likely that ROXELANA22 remembers these accounts, and also their passwords. As stated in the previous reports for ROXELANA22 that I've issued recently, the severity and duration of this LTA's cross-wiki vandalism, along with his pattern of using very old sleepers or moving locally-blocked socks to continue cross-wiki vandalism, merits a Global Lock on all of his accounts. LightandDark2000 (talk) 10:22, 27 March 2018 (UTC)Reply

Can someone please Lock these accounts? The discussion here provides more reasons for why this LTA's socks need to be Locked. He recently began re-using years-old sock accounts to resume cross-wiki vandalism (such as User:ZiguratEnki). By the way, it's worth noting that ROXELANA22 was Banned at the English Wikipedia years ago, and given his recent cross-wiki vandalism and trolling, he's probably de-facto Globally Banned as well. LightandDark2000 (talk) 23:28, 31 March 2018 (UTC)Reply

Global lock for 影武者(Nipponese Dog Calvero)

Status:    Done

--Lanwi1(talk) 10:29, 2 April 2018 (UTC)Reply

Done --Alaa :)..! 20:03, 2 April 2018 (UTC)Reply

Global lock for Jesus-news

Status:    Done

WP0 abusers. --jdx Re: 01:51, 3 April 2018 (UTC)Reply

Done together with ten additional sleeper accounts. @Jdx: Cheers. —Green Giant (talk) 02:04, 3 April 2018 (UTC)Reply

Global lock for spam accounts

Status:    Done

Spambots. -★- PlyrStar93. →Message me. ← 03:36, 3 April 2018 (UTC)Reply

Done together with a bonus sleeper. @PlyrStar93: Cheers. —Green Giant (talk) 03:48, 3 April 2018 (UTC)Reply

Global lock for LTA sock

Status:    Done

ISECHIKA. See also commons:Category:Sockpuppets of いせちか国際空港. -★- PlyrStar93. →Message me. ← 03:50, 3 April 2018 (UTC)Reply

Done —Green Giant (talk) 03:53, 3 April 2018 (UTC)Reply

Global lock for cross-wiki abuse accounts

Status:    Done

Cross-wiki issues, not all accounts are related. The third one is Vandyrandy with other socks disrupting different projects recently. -★- PlyrStar93. →Message me. ← 04:14, 3 April 2018 (UTC)Reply

Done —Green Giant (talk) 04:27, 3 April 2018 (UTC)Reply

Global lock for Med elou

Status:    Done

WP0 abuse. -★- PlyrStar93. →Message me. ← 04:14, 3 April 2018 (UTC)Reply

Done —Green Giant (talk) 04:28, 3 April 2018 (UTC)Reply

Global lock for 影武者(Nipponese Dog Calvero)

Status:    Done

--Lanwi1(talk) 05:05, 3 April 2018 (UTC)Reply

Done together with two more accounts, although the checkuser showed an additional six accounts credited to ISECHIKA or an imitator. @Lanwi1: Cheers. —Green Giant (talk) 10:58, 3 April 2018 (UTC)Reply
@Green Giant:丁宜蘭's edit behavior conformity with Nipponese Dog Calvero. Nipponese Dog Calvero is using proxy IP? --Lanwi1(talk) 15:57, 3 April 2018 (UTC)Reply
@Lanwi1: Yes, it is very possible that NDC is mimicking but I’ve blocked the underlying IP as a precaution. Green Giant (talk) 16:01, 3 April 2018 (UTC)Reply
@Lanwi1: NDC has been using proxy IP's lately (unless someone else is really good at being his imposter). Can't think of this edit being made by anyone else. Also this is another proxy IP I reported at zhwiki. -★- PlyrStar93. →Message me. ← 17:12, 3 April 2018 (UTC)Reply

Global lock for socks of LTA Vandyrandy (3)

Status:    Done

More socks of the LTA cross-wiki vandal Vandyrandy. Cross-wiki abuse is obvious here. Vandyrandy is known for extremely degrading personal attacks and Neo-Nazi vandalism, in addition to cross-wiki vandalism. Similarly to his IPv6 range, his IPv4 range needs to be rangeblocked for at least 3-6 months, because this IP range also has an extensive history of abuse across multiple Wikimedia sites (including Meta), and also because this user is known to create sock account across multiple wiki sites. LightandDark2000 (talk) 05:12, 3 April 2018 (UTC)Reply

After sifting through the range contributions, it appears that this IP range has been abused extensively since October 2017, concurrently with Vandyrandy's 2600:1000:B100:0:0:0:0:0/42 IPv6 range. By the way, given the history of abuse and mass socking, I strongly recommend Stewards to Check the IP range (and the listed accounts) for more Sleepers. LightandDark2000 (talk) 05:13, 3 April 2018 (UTC)Reply
Done together with several bonus accounts. I’ve not blocked the IP range because there appear to be many unrelated accounts. Cheers. Green Giant (talk) 10:40, 3 April 2018 (UTC)Reply
@Green Giant: I was actually thinking of an "anon-only" Global Rangeblock (IPs only + account creation), so that the unrelated users can still log into their account and edit. Perhaps this can be done? LightandDark2000 (talk) 06:44, 4 April 2018 (UTC)Reply
Actually, see the 4th report on this LTA, some reports below. LightandDark2000 (talk) 09:47, 4 April 2018 (UTC)Reply

Global lock for Joice Nado

Status:    Done

WP0 abuse. --Crt 07:23, 3 April 2018 (UTC)Reply

Done - TNT❤ 09:01, 3 April 2018 (UTC)Reply
Lock conflicted, done by Vituzzu ._. - TNT❤ 09:01, 3 April 2018 (UTC)Reply

Global lock for spambot

Status:    Done

Obvious spambot account. The edits of this account also suggest that its operator could be a scammer as well. LightandDark2000 (talk) 07:44, 3 April 2018 (UTC)Reply

Done --Alaa :)..! 10:03, 3 April 2018 (UTC)Reply

Global lock for socks of Black Magic spammer LTA

Status:    Done

These are all socks of the "Black Magic" spammer LTA. This spammer is known for cross-wiki abuse and spamming, and the user has been socking and spamming for over 6 months now. I'm starting to grow tired of dealing with this. Given the recent socking spree, I strongly suggest Stewards to Check the underlying IP range and the listed sock accounts. By the way, the IP range listed needs to be Globally Rangeblocked for at least 6 months (3 months is the absolute minimum, though 6 months would be more suitable for stopping the abuse), because this person has been spamming multiple Wikimedia sites at least since September 2017. A Global Rangeblock is necessary because this user has circumvented each of their previous (Global) IP blocks. Anonymous editors should be referred to ACC or to the Stewards for account creation if they want to edit on any of the projects (Collateral damage on the range is rather small anyway, given the sparse editing activity). LightandDark2000 (talk) 07:55, 3 April 2018 (UTC)Reply

Done together with numerous additional accounts (not all Black Magic though). @LightandDark2000: Cheers. —Green Giant (talk) 09:45, 3 April 2018 (UTC)Reply

Global lock for Manda 1993

Status:    Done

Long-term abuse. --Ilzhabimantara (talk) 10:14, 3 April 2018 (UTC)Reply

Done by Green Giant --Alaa :)..! 11:01, 3 April 2018 (UTC)Reply

Global lock for Leoonell Messi

Status:    Done

WP0 abusers. --jdx Re: 12:13, 3 April 2018 (UTC)Reply

Done --Alaa :)..! 12:29, 3 April 2018 (UTC)Reply

Global lock for Emanuel da Silva Marquese

Status:    Done

WP0 abuser. --jdx Re: 12:30, 3 April 2018 (UTC)Reply

Done --Alaa :)..! 12:33, 3 April 2018 (UTC)Reply

Global lock for spambots

Status:    Done

Spambots. Wiki13 talk 12:55, 3 April 2018 (UTC)Reply

Done together with more than sixty additional accounts revealed by checkuser. @Wiki13: Cheers. Green Giant (talk) 13:57, 3 April 2018 (UTC)Reply

Global lock for Gibson Sky

Status:    Done

WP0 abuser. --jdx Re: 15:29, 3 April 2018 (UTC)Reply

Done together with three additional accounts. -Green Giant (talk) 15:48, 3 April 2018 (UTC)Reply

Global lock for socks of Avoided (or an impostor)

Status:    Done

@Trijnstel: (or whom it may concern: Please lock his socks, check the underlying IPs and block IPs and as well additional accounts, if found. If blocked locally, but not locked globally, it will be probably end like this. Regards --Schniggendiller (talk) 17:00, 3 April 2018 (UTC)Reply

Done with several extra accounts locked and IPs blocked. @Schniggendiller: Cheers. —Green Giant (talk) 18:12, 3 April 2018 (UTC)Reply

Global lock for Dini Pg2

Status:    Done

WP0 abuser. --jdx Re: 17:04, 3 April 2018 (UTC)Reply

Done with four extra accounts. -Green Giant (talk) 18:16, 3 April 2018 (UTC)Reply

Global lock for Lama News

Status:    Done

WP0 abusers. --jdx Re: 20:54, 3 April 2018 (UTC)Reply

Done with a bonus account. —Green Giant (talk) 21:09, 3 April 2018 (UTC)Reply

Global lock for 影武者 (Nipponese Dog Calvero)

Status:    Done

--Artix Kreiger (Message Wall) 22:30, 3 April 2018 (UTC)Reply

Done together with four bonus accounts and two IPs blocked. @Artix Kreiger: cheers. —Green Giant (talk) 00:00, 4 April 2018 (UTC)Reply
Well, apparently Nipponese Dog Calvero has been abusing proxy IP's. Anyone would like to take a look if 简单时刻 acts behaviorally consistent with NDC at zhwiki? -★- PlyrStar93. →Message me. ← 00:11, 4 April 2018 (UTC)Reply
I saw Artix tagged 简单时刻 as a sock of 影武者 on zh.wp. But it looks like a sockpuppet of someone else (discuss about establishing Arbitration Committee since first edit). @Lanwi1: Could you confirm it? Thanks. --E8xE8 (talk) 00:25, 4 April 2018 (UTC)Reply
@E8xE8:简单时刻 isn’t sock of NDC, because edit behavior inconformity. --Lanwi1(talk) 00:51, 4 April 2018 (UTC)Reply
@Artix Kreiger: You have make the mistaken, User:简单时刻 is not a sockpuppet of NDC (影武者). @Green Giant: Please consider to do something on this user account, thanks. SA 13 Bro (talk) 00:57, 4 April 2018 (UTC)Reply


I had requested a lock on Frankie Kao because Favonian blocked it. Then green giant used Checkuser. However, it is still suspicious because of reason provided by E8xE8 --Artix Kreiger (Message Wall) 00:59, 4 April 2018 (UTC)Reply

The CU data would match probably because multiple unrelated people were using the same proxy IP around the same time. A lot of users at zhwiki rely on proxy/VPN due to obvious reasons. -★- PlyrStar93. →Message me. ← 01:06, 4 April 2018 (UTC)Reply

PlyrStar93, please enlighten me on my talk page. What are the obvious reasons? --Artix Kreiger (Message Wall) 01:08, 4 April 2018 (UTC)Reply

A reason that 简单时刻 might not be a sockpuppet of 影武者 is, he used simplified Chinese but not traditional Chinese which was used by 影武者. Other than the topic (establishing ArbCOM), it seems that 简单时刻 has different philosophy ideas than 影武者 according to his/her comments. However, it is highly probable that 简单时刻 is someone else's unrevealing puppet since he knows Wikipedia so well. --PhiLiP (talk) 01:17, 4 April 2018 (UTC)Reply
I will defer to Lanwi1 and PhiLiP's assessment and have unlocked the account. For clarity, it wasn’t Artix who requested the lock for that account. From the CU data, those three accounts (Frankie Kao, Eric McClintock, and 简单时刻) were the only ones on that IP, and it appeared they might be the same user. Green Giant (talk) 01:34, 4 April 2018 (UTC)Reply

Global lock for LTA

Status:    Done

Long-term abuse. SA 13 Bro (talk) 23:22, 3 April 2018 (UTC)Reply

Global lock for Bos primigenius rex

Status:    Done

New sock puppet of Yahadzija. Эlcobbola talk 23:33, 3 April 2018 (UTC)Reply

Done with two bonus accounts and one IP blocked. @Elcobbola: cheers. —Green Giant (talk) 00:07, 4 April 2018 (UTC)Reply

Global lock for Nipponese Dog Calvero

Status:    Done

Newly active sock account. -★- PlyrStar93. →Message me. ← 00:44, 4 April 2018 (UTC)Reply


Not surprised at the "chinaman" comment. --Artix Kreiger (Message Wall) 00:48, 4 April 2018 (UTC)Reply

Done — Defender (talk) 00:56, 4 April 2018 (UTC)Reply

Global lock for Alvi Z. sock

Status:    Done

Long-term abuse. –theinstantmatrix (talk) 01:04, 4 April 2018 (UTC)Reply

Done —Green Giant (talk) 01:38, 4 April 2018 (UTC)Reply

Global lock for Nipponese Dog Calvero

Status:    Done

These ones indef'ed at enwiki earlier on. -★- PlyrStar93. →Message me. ← 03:04, 4 April 2018 (UTC)Reply

Done —Green Giant (talk) 03:36, 4 April 2018 (UTC)Reply

Global lock for Black Magic spambot LTA (2)

Status:    Done

Obvious sockpuppet/spambot of the "Black Magic" spambot LTA. The account needs to be Locked. Given the very persistent history of cross-wiki spamming and socking (stretching back at least since September 2017), the underlying IP range(s) of the newest socks need to be Globally Rangeblocked as well. The current rangeblock should probably be expanded to a year-long Global Rangeblock on 117.119.0.0/16 (assuming that the newer IPs are on the same range), because this spammer has evaded their last, smaller rangeblock, and due to the duration of the abuse coming from the network. I noticed that a lot of IPs on this network have been reported to Blacklisting sites for spam/abuse, so these are more reasons to expand the Global Rangeblock. LightandDark2000 (talk) 07:45, 4 April 2018 (UTC)Reply

Given the history of mass socking/spambot creation by the operator of the IPs, a Steward should check the entire IP range and the listed account for more Sleepers. Given the extent of the abuse and the multitude of IPs involved in the spamming, I suspect that the company behind the network may be responsible for the spambots, or at the very least, whoever is using that IP network. You can also see the extensive abuse in the last report for more reasons why the IPs need an expanded Global Rangeblock. The IP range can be an "anon-only" block to avoid blocking unrelated users, but the IPs should still be Globally Rangeblocked for at least a year to stop the cross-wiki abuse. LightandDark2000 (talk) 07:50, 4 April 2018 (UTC)Reply
Done + some sleepers. Range blocked (anon. only) 1 week initially - TNT❤ 08:04, 4 April 2018 (UTC)Reply
@There'sNoTime and Green Giant: You don't have to do anything more right now, but FYI, the abuse from this IP range was much more extensive than I had imagined (especially given the numerous local re-blocks). LightandDark2000 (talk) 08:15, 4 April 2018 (UTC)Reply

Global lock for Black Magic spambot LTA sockmaster

Status:    Done

The first named account is probably the sockmaster (or a sock account) of the "Black Magic specialist" spammer LTA, due the the username pattern. Pretty much every other account I know of with "Black Magic specialist" in its name is a sock/spam account of this LTA. In any case, this account still needs to be Globally Locked, because the username alone already implies that the user is not here to contribute positively, and because the username is a violation of Wikimedia's policies on advertising / spam accounts. As for the second account, it's an obvious sock. LightandDark2000 (talk) 08:39, 4 April 2018 (UTC)Reply

Done —Green Giant (talk) 10:01, 4 April 2018 (UTC)Reply

Global lock for socks of LTA Vandyrandy (4)

Status:    Done

Obvious socks of the cross-wiki LTA Vandyrandy. This LTA is known for Neo-Nazi vandalism, and severe personal attacks across various wiki sites. Given the recent socking activity of this sockmaster, I strongly suggest a Sleeper Check. The listed IP range should also be Globally Rangeblocked for 3+ months, as an "anon-only" rangeblock to allow unrelated users to log in and continue editing. The rangeblocks need to be multi-month blocks, given the abuse shown in the report here, and another one below it (3). Any other IP ranges involved (if any) should also receive a 3-6+ month-long Global Rangeblock set at "anon-only." LightandDark2000 (talk) 08:53, 4 April 2018 (UTC)Reply

Done with one definite sleeper. IP anon-blocked for 3 months. -Green Giant (talk) 10:16, 4 April 2018 (UTC)Reply

Global lock for User:Qwrgq

Status:    In progress

Obvious vandalism-only account. This user was also recently active at other Wikimedia sites, so a Global Lock is needed here. LightandDark2000 (talk) 09:44, 4 April 2018 (UTC)Reply

Global lock for LTA Black magic specialist spammer (4)

Status:    Done

—

Found even more socks of the cross-wiki LTA "Black magic specialist", after digging around in Wikipedia's Account Creation Logs. These accounts need to be Globally Locked, and the recent ones (within the past year) need to be Checked for Sleepers. For the "sockfarms" listed that mostly don't have any edits, the naming pattern pretty much gives it away. The few accounts in those sockchains that did have edits (whether or not they were blocked) all appeared to be adding "black magic" spam, or creating pages with related content. From what I can tell, this spammer has been spamming and socking since 2011 (ad possibly as early as 2009). LightandDark2000 (talk) 10:25, 4 April 2018 (UTC)Reply

The last named account is unrelated, but needs to be Locked because of the offensive/obscene username. LightandDark2000 (talk) 10:25, 4 April 2018 (UTC)Reply
Done with three already locked. Checkuser has not revealed any additional accounts. —Green Giant (talk) 11:27, 4 April 2018 (UTC)Reply

Global lock for Count Commons Pg

Status:    Done

WP0 abuser. --jdx Re: 10:57, 4 April 2018 (UTC)Reply

Done - TNT❤ 11:27, 4 April 2018 (UTC)Reply

See also

Cooperation requests for: comments (local) (global) · translation

Retrieved from "https://meta.wikimedia.org/w/index.php?title=Steward_requests/Global&oldid=17899967"