Wikipedia:Sockpuppet investigations/ThijsStoop

ThijsStoop

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

Populated account categories: confirmed · suspected

For archived investigations, see Wikipedia:Sockpuppet investigations/ThijsStoop/Archive.

06 August 2025

– A checkuser has completed a check on relevant users in this case, and it is now awaiting administration and close.

Suspected sockpuppets

185.14.97.191 (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

Probable WP:IPSOCK based on edit style, summaries, and content. Resumed as soon as Park Bo-gum article was unprotected today. RachelTensions (talk) 03:07, 6 August 2025 (UTC)[reply]

Comments by other users

49.151.162.233 (talk⁺ · tag · contribs · filter log · WHOIS · RBLs · proxy check · block user · spi block · block log · cross-wiki contribs · CheckUser (log))
Kuragehime000 (talk⁺ · tag · contribs · deleted contribs · logs · filter log · block user · spi block · block log · CA · CheckUser(log) · investigate · cuwiki)
2001:4455:902E:2300:ADF5:E2E1:A3AA:FD58 (talk⁺ · tag · contribs · filter log · WHOIS · RBLs · proxy check · block user · spi block · block log · cross-wiki contribs · CheckUser (log))
185.14.97.86 (talk⁺ · tag · contribs · filter log · WHOIS · RBLs · proxy check · block user · spi block · block log · cross-wiki contribs · CheckUser (log))
185.14.97.87 (talk⁺ · tag · contribs · filter log · WHOIS · RBLs · proxy check · block user · spi block · block log · cross-wiki contribs · CheckUser (log))
185.14.97.88 (talk⁺ · tag · contribs · filter log · WHOIS · RBLs · proxy check · block user · spi block · block log · cross-wiki contribs · CheckUser (log))
49.151.163.10 (talk⁺ · tag · contribs · filter log · WHOIS · RBLs · proxy check · block user · spi block · block log · cross-wiki contribs · CheckUser (log))
Swedishfisch (talk⁺ · tag · contribs · deleted contribs · logs · filter log · block user · spi block · block log · CA · CheckUser(log) · investigate · cuwiki)
SabeSabeSabe (talk⁺ · tag · contribs · deleted contribs · logs · filter log · block user · spi block · block log · CA · CheckUser(log) · investigate · cuwiki)

Adding those above just in-case. IPs are actively editing Park Bo-gum & its related pages after the protection was removed.

As for the user, its first edit was about Park Bo-gum back in 2017:[1] Then it was suddenly active after 30 July 2025.[2], mostly in page Korea Broadcasting Prizes. Diff: [3] --Preferwiki (talk) 05:10, 6 August 2025 (UTC)[reply]

Adding one more IP (49.151.163.10) with diff: [4][5][6]--Preferwiki (talk) 01:27, 8 August 2025 (UTC)[reply]

Adding Swedishfisch; randomly asking another editor to edit Park Bo-gum when prior contributions after account creation doesn't shows any interests of such topic,[7] and also at that point of time, Park Bo-gum's protection has already expired for nine days. — Paper9oll (🔔 • 📝) 11:13, 16 August 2025 (UTC)[reply]

Adding sabesabesabe, similar reason, asking help to edit PBG [8]--Preferwiki (talk) 13:19, 16 August 2025 (UTC)[reply]

@Izno Thanks for ur hardwork. This might help. On August 4th Kuragehime000 created the award page [9] [10]. Swedischfisch asked Apollogizing to link the winners to 52nd Korean Broadcasting Prize in their talkpage [11]. Appologizing politely refuse the request on August 4th due only a few winners were announced[12], but eventually add them on PBG's award page on the 5th [13]. An IP then made an edit for the award total sum coz pref user forgot to edit that [14][15]

Meanwhile between August 4th to 7th Kuragehime000 build the page so the winner of the award is more complete.[16][17]. Only after 7th august this user installed bot [18][19]. It mostly only doing copy editing beforehand. The timing is very convenient for a mere coincidence.

Question, how about edit made by the IPs? It makes the pages worse (puffery). After blocking them, is revert possible? Preferwiki (talk) 08:41, 17 August 2025 (UTC)[reply]

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

Clerk, CheckUser, and/or patrolling admin comments

I've blocked a couple IPs as proxies. The rest are stale at this point. I'll look at the users next. Izno (talk) 01:51, 17 August 2025 (UTC)[reply]
Likely to each other and priors
- Boranavi (talk⁺ · tag · contribs · deleted contribs · logs · filter log · block user · spi block · block log · CA · CheckUser(log) · investigate · cuwiki)
- Swedishfisch (talk⁺ · tag · contribs · deleted contribs · logs · filter log · block user · spi block · block log · CA · CheckUser(log) · investigate · cuwiki)
- 616bg616 (talk⁺ · tag · contribs · deleted contribs · logs · filter log · block user · spi block · block log · CA · CheckUser(log) · investigate · cuwiki)
- SabeSabeSabe (talk⁺ · tag · contribs · deleted contribs · logs · filter log · block user · spi block · block log · CA · CheckUser(log) · investigate · cuwiki)
- Extremely Radioactive (talk⁺ · tag · contribs · deleted contribs · logs · filter log · block user · spi block · block log · CA · CheckUser(log) · investigate · cuwiki)
Izno (talk) 01:58, 17 August 2025 (UTC)[reply]
As for Kuragehime, I cannot dismiss them out of hand. They have overlap for a particular user agent with priors and are in the general part of the world priors are in. But aside from that, they aren't on proxies in the same way the others have been. Put them at possible. Better behavioral evidence would assist in assessing this user. Izno (talk) 02:05, 17 August 2025 (UTC)[reply]

I would hazard to guess they're a returning editor, whether this one or another. Izno (talk) 02:08, 17 August 2025 (UTC)[reply]