Wikipedia:Sockpuppet investigations/Yusaya 4531

Yusaya 4531

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

Populated account categories: suspected

For archived investigations, see Wikipedia:Sockpuppet investigations/Yusaya 4531/Archive.

This SPI case may involve cross-wiki abuse. Please consider reporting the results on Meta; checkusers can send an email to the interwiki checkuser mailing list if required.

08 April 2024[edit]

– This SPI case is closed and will be archived shortly by an SPI clerk or checkuser.

Suspected sockpuppets[edit]

126.254.100.60 (talk⁺ · tag · contribs · filter log · WHOIS · RBLs · proxy check · block user · spi block · block log · cross-wiki contribs · CheckUser (log))
2400:2200:6EB:5C77:F1D5:AF9:A46:91BE (talk⁺ · tag · contribs · filter log · WHOIS · RBLs · proxy check · block user · spi block · block log · cross-wiki contribs · CheckUser (log))
Tools: Editor interaction utility • Interaction Timeline • SPI Tools

Both the IPv4 and the IPv6 use the name: diff:ipv6, diff:ipv4. Both edited and are editing each other's talk pages, talk page edits of both (all edits) are mostly DUCK with what I remember from previous accounts and IPs. – 2804:F14:8090:C501:686B:E2D5:C69E:9592 (talk) 05:16, 8 April 2024 (UTC)[reply]

Hm, I hadn't noticed how few accounts there are in this SPI, actually - and no IPs. I previously saw this user before they started creating accounts and documented them on Alexf's talk page(for some reason). Looks like a lot of the previous IP's edits are now deleted. Hopefully it's still obvious. – 2804:F14:8090:C501:686B:E2D5:C69E:9592 (talk) 05:26, 8 April 2024 (UTC)[reply]

Comments by other users[edit]

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

(same user as the IP who reported) This is now stale, there have been no further DUCK edits from IPs in the /32(IPv6) and /16(IPv4) ranges since I made this report - it also seems like this was the first time they used these ranges for this, though I obviously cannot see deleted contributions.
I'd close this to help reduce the backlog, but I don't know how, and I suspect the filters wouldn't let me anyways. – 2804:F14:80AD:C201:A1F1:53F1:AD24:FA49 (talk) 10:01, 20 April 2024 (UTC)[reply]

(also the same user as the IP who commented above) Maybe I jinxed it - the IPv6's /32 is active again and another IPv4 not in the /16 range is as well (126.33.160.97)... oh well.

– 143.208.239.166 (talk) 01:31, 21 April 2024 (UTC)[reply]

I'll just note that the admin @Utcursch has been deleting most of the user talk pages and subpages that prompted me to make this report (they were tagged for speedy deletion), so if anyone handles this in the future they will have to look at the deleted contributions.

That said, I'm not really sure what an appropriate block would be anymore, since from the IPs on the 8th to the IPs today is a pretty big jump for blocks to seem reasonable, even if the IPs are from the same ISP. – 143.208.239.166 (talk) 03:19, 21 April 2024 (UTC)[reply]

Update: Been a bit, looking at this again a /36 range which covers all the IPv6 that still have user talk edits (and the initial IPv6) has been blocked for 61 days by @JBW for possibly unrelated reasons. There has been no further disruption from the 2 /16 IPv4 ranges contributions (if it wasn't all deleted) either - so I think this can be closed.

– 2804:F14:80EE:5A01:F151:38D2:AA6E:399F (talk) 21:15, 3 May 2024 (UTC)[reply]

Clerk, CheckUser, and/or patrolling admin comments[edit]

There's no doubt whatever that both of these were Yusaya 4531, but, as the IP editor above has said, there have been no recent related edits from the relevant IP ranges, and the IPv6 range is blocked, so there's nothing more to be done. Close. JBW (talk) 09:32, 7 May 2024 (UTC)[reply]