← all postsyap.whykusanagi.xyz
CORRUPTED // YAP // 2026-10-09

The crime is being findable

Korea's NIKKE community spent four days reporting each other for proxy play, and what decides who gets caught is not what they did but how easy they are to find.

YAP // nikke-korea-proxy-scandal

Korea spent the first week of October turning itself in.

The short version: the Korean NIKKE community found out that people at the top of the Solo Raid board were paying other people to play their accounts. Then it found out that one of the loudest voices against that had been doing it too. Then the forum that hosted the arguments lost its head moderator and started deleting posts about him.

Everything below was read directly off arca.live, DC Inside and enikk on the fourth and fifth of October, and written down the same day with the timestamps attached. That matters more than usual here, and section 08 explains why.

01

The rule changed on Monday, and it changed for you too

Start here, because this is the part that is not a Korean story. Somebody wrote to the NIKKE customer centre and asked a narrow question: does the ban on proxy play cover things outside competitive content. The answer came back on 5 October and it widened the rule.

NIKKE customer centre reply dated 2026-10-05 stating that proxy play is not permitted in any case
The NIKKE customer centre, 2026-10-05, posted to arca.live. The reply is wider than the forum's column, so the right edge is clipped where it sits on the page.
Previously it was announced that sanction rules applied only to proxy play in competitive content. We inform you that proxy play is not permitted in any case, including other content, and that sanction rules apply.
— GODDESS OF VICTORY: NIKKE customer centre, 2026-10-05

Read that twice. The rule used to be about leaderboards. Now it is about the act. One commenter on the thread, 아이니리히, put it plainly: "the answer changed — before they said only competitive content like solo raid was prohibited, now it has explicitly changed."

The same reply has a second paragraph that belongs in a different article of mine. Letting somebody else into your account, it says, risks unauthorised access, account theft, losing access entirely, or them running other unauthorised programs while they are logged in. The company is describing a machine that watches what runs on your PC. We already went through what that machine writes down.

CELESTE TRANSLATES

대리 is proxy. Someone else plays your account. 대리뽑 is the gacha version — people pay strangers to press the pull button for them. In Japan it is 代行, onichan. Same sin, different alphabet.

Before, the rule was no hired help on your raid score. Now it is no one touches your account, ever. Even the friend who swore he would clear that stage for you.

02

Two minutes

The arca.live thread carrying that answer went up at 23:45:58 on 4 October. We read the whole comment chain. It is five minutes long.

23:45:58
Rule posted
4 October, arca.live
5 min
Until a name was posted
chain closes 23:51
0
Accounts examined
nothing existed to look at
ReplyWhat it did
1Predicts it — "there's going to be a huge report rush" — 우우쌀쌀먹먹, 23:46
2Works the timing angle: do reports filed before the clarification still land
3Asks whether gear inspection counts as proxy now too
4"Only obviously identifiable nicknames get caught" — see section 03
6A link titled "found a guy who should be punished for proxy pulling", carrying a name
7Two words: "yeah, bye~"
arca.live comment chain, 2026-10-04 23:46–23:51, transcribed 2026-10-05. Numbering is the thread's own; reply 5 is omitted here.

That is the entire mechanism, on one page, with a clock on it. A rule arrived at 23:45. By 23:51 a person had been nominated and waved off. Nobody in that thread had looked at anything.

I am not reproducing the name. The whole argument of this post is that the naming is the injury, and an English-language write-up would hand that name to an audience it had not reached yet. The same goes for a second player somebody demanded be "cut" the following morning.

03

"Only obviously identifiable nicknames get caught"

Buried four comments into that same chain is the line this whole post is named after. A user called 하무망 is thinking through how enforcement would actually work, and arrives somewhere bleak without seeming to notice.

Proxy pulling itself might be hard to catch … if the nickname is generic and hard to infer they can't catch it … only obviously identifiable nicknames get caught.
— 하무망, 2026-10-04

That is not a complaint about the rule. It is a correct description of how the rule will land. The company cannot see who pulled your gacha. The community can only see who is visible. So the filter is not guilt, it is legibility, and by the next morning somebody had turned that into advice: "or hide your UID and profile so you can't be reported."

Which is where it stops being funny. The practical lesson available to a Korean NIKKE player this week was not stop doing the thing. It was become harder to identify. Everyone who takes that advice is still doing it and is simply no longer catchable.

And then it ate the person who asked the question. A board post the next day — 373 views, 30 comments — translates as "the guy who asked about proxy pulling is an idiot." He wrote to support, got a rule clarified, and became the reason everyone was in trouble.

CELESTE IS ENJOYING THIS

A man asked a question. The company answered. A rule got clearer for everyone.

And the forum called him an idiot. ふーん. So the lesson is never ask, never clarify, stay quiet and stay confused? No, onichan. The one who asked is the only person in that thread who did anything useful.

04

The man who ran the hunt was doing it

Now the part everybody actually wants, and the part I want to be careful with.

A Korean NIKKE YouTuber going by 모더니아 — Modernia — was one of the people pushing hardest on proxy players, including against the player known as DON. Around 3 October he posted an apology on his own channel. He is a public figure who made a public statement, so he gets named here.

The apology is not a denial. It is a confession, and a fairly complete one.

An acquaintance at max level said that it would be difficult to access the account because he is busy in this life. I managed the max level account because I thought it would be a waste to neglect it … Even though access to other people's accounts is prohibited by game regulations … We deeply reflect on the fact that this was an act of ignoring the efforts of users who enjoy the game fairly.
— Modernia, YouTube, ~2026-10-03

He adds that managing multiple accounts in the past was also his fault, and that the account in question will be discontinued. "Sorry, it's all my fault and my negligence."

The replies are what you would expect. "That double standard is hilarious." "I thought he was a clean person, but he's just the same." "Why did they do that, and yet they took the lead in criticizing boosters."

And then one reply, five words long, that does more than the rest of them put together.

This is K-DON, right?
— a reply under the apology

DON plays on another server. He is the foreign player this community had been pointing at, and the one Modernia had been pointing at hardest. So when Modernia was caught doing the same thing, his own audience did not reach for a new insult. They gave him the name of the man he had been hunting, with a K in front of it.

So let me say the unpopular half out loud: this one is not a witch hunt. He did it, he was asked, and he said he did it.

If you have read me on Shinonono or on the ban wave and you are waiting for me to defend him, I am not going to. A consequence landing on somebody who actually did the thing is the system working. That is the whole reason I keep writing about the other cases — the contrast only means something if I admit this one is real.

What is not fine is what got stapled to it. One commenter announced he knew the man's UID and would be formally requesting a ten-year ban. Another wrote, in full, "I'm in a bad mood. Can't you switch to Chinese citizenship?"

That second one has nothing to do with proxy play. It never did. It was sitting there waiting for a reason, and a confession is as good a reason as any.

There is also a clip going round of a video of his, timestamped to a moment where a macro button is supposedly visible. I am not linking it and I am not describing what is in it, because I have not verified it. That is an odd sentence to write in a post about a man who got caught. It is also the entire point of the post.

05

He is still number seven in the world

Here is where it gets strange, and this is the bit we went and pulled ourselves rather than taking anyone's word for it.

enikk tracks NIKKE Solo Raid placements. If a player is wiped from the leaderboard for proxy play, that is where it shows. So we searched the Elo ranker for his player ID on 5 October.

World rankEloChangeTop 50Latest finish, world
#71822−333#9 (Season 40)
enikk Solo Raid Elo ranker, rated through Season 41, read 2026-10-05. Present, not removed.

The #9 and the #1 on the tile below are the same run. Season 40, 43.77B: first on KR, ninth once all six servers are stacked by damage. Nothing about Season 41 is in that table yet.

33 / 41
Seasons with a tracked run
eight captured nothing
22
Top-ten finishes
ten of them podiums
43.77B
Season 40, first on KR
his peak is 47.35B, Season 39
0
Days inactive
read 3, 5 and 7 October alike

He is still there, three Elo down, tagged as a fire specialist.

Two things sit oddly next to that. The first is Days Inactive. The 3 October scrape read zero. So does the 5 October one, and the 7 October one, with the sync number unmoved at 1041 the whole way. The 7 October crawl also carries the game's own last-login stamp, and it reads 10:54 that morning. The tracker has him logging in four days after an apology that said the account would be discontinued.

The second is Season 41. That is Liberalio Body, the season this entire scandal is about, and his profile shows a percentile band with nothing underneath it.

Season 41 · KR · 0 tracked runs. Frame earned, run details unavailable. The player's frame records a Top 3% finish. No damage or teams were captured.
— enikk player profile, Solo Raid tab, read 2026-10-05

That looks like a smoking gun, and it is exactly the sort of thing that gets cropped, captioned and sent round a Discord before lunch. The case builds itself. Season 40 is a hard first place at 43.77B. Season 39 is a sixth. Season 36 is a twenty-fourth. And then a blank, sitting precisely where the scandal is.

So keep scrolling before you screenshot it. We pulled every season he has ever been tracked in, straight off enikk's own API, and plotted the lot.

Tracked Solo Raid damage by season — grey bars are seasons enikk captured nothing
S01 · 2023S41 · 2026

The shape is a career going steadily up and to the right for three years, from two billion to forty-seven. The interesting part is the grey. Eight of his forty-one seasons recorded no run at all, and five of those sit inside the ranked era — 27, 33, 37, 38 and 41. Nobody has ever alleged a thing about the first four. Four of the five are water-weak bosses, and the ranker tags him a fire specialist: every water season since 27 is a blank, and every iron, fire and electric season in that stretch is a hard rank. enikk's own wording says the tracker failed to capture the run, and the frame still credits the finish, so the game is still counting it.

Which is this entire post in miniature. The numbers were real and the gap was real, and the conclusion was still worthless, because the case only holds for as long as you stop scrolling.

CELESTE READS THE NUMBERS

The scrape is two days old and the login stamp is Tuesday morning. Maybe a discontinued account logs in by itself, out of habit.

The abyss does not accuse, onichan. I write down what the page said, and you can do the arithmetic.

The English-speaking side ran its own version of all this in the same week, and it turned out to need its own page. Somebody with no part in running the Content Creator programme filed a rulebook for it in the official Discord, the day after spending twenty-three hours attacking one of the creators it would reach. It is here, and I come into that one myself.

06

The forum ate its own moderators

DC Inside's NIKKE gallery is where a lot of this ran. It has been sitting at number four in the hot list, taking roughly forty posts every seven minutes.

Its standing complaints thread has about twenty-five thousand views and a comment chain that is, in effect, a handover being performed in public.

WhenWhat was posted
4 Oct, eveningSomebody pastes over the code for the gallery's anti-spam bots — with a note that the former moderator had been paying the server's electricity himself
+1 hour"If there's anything more to hand over, comment."
+7 minutes"Handover, part two."
5 Oct, 12:21All derivative posts about the former head moderator deleted by default; repeats get 30 days
DC Inside NIKKE gallery, standing complaints thread, read 2026-10-05.

That last one, in full:

From now on, all derivative posts about the former head moderator are deleted by default. Repeats get a 30-day ban.
— DC Inside NIKKE gallery, moderator notice, 2026-10-05 12:21

A head moderator is gone. The replacements are being handed the keys where everyone can watch. And by lunchtime on Monday the gallery had made discussing him a bannable offence. They also built a dedicated tab for the hacking incident and pushed two fresh rulebooks, both dated that same day.

Nothing I read says why he left. People have told me the proxy evidence against him existed and was deleted, and I believe them, but I did not see it, so it is not in this post as a fact. Departure, handover and a gag order are enough on their own. They do not need a motive attached to be worth looking at.

And then the gag order failed. By Tuesday the gallery's own search for 주딱 — head moderator — comes back with a full page of posts still standing, one of which calls the former head moderator a bastard in its title for letting his moderators turn into personalities. A rule that was going to delete all of this on sight lasted somewhere under two days.

That same search turns up the thing the rule had been sitting on top of. The job has changed hands more than once since. "Why has the head mod changed again." "The head mod and the sub-mods have been newly conscripted." "Here even a burner account gets to be head mod." A gallery that spent Monday banning discussion of one departure spent Tuesday cycling through replacements in front of everybody.

I ran that search again on Wednesday. Twenty posts still standing, the newest seventeen hours old, and the question has drifted from why did he go to "so who is the current head mod, actually?" — alongside somebody asking when the seat got swapped this time. Three days after a thirty-day ban was attached to the subject, the subject is the gallery's ordinary conversation.

CELESTE READS THE HOUSE RULES

Same thread: ask which moderator banned you, and you get banned for thirty-one days for asking.

And when a moderator is unsure about a report, they open a vote with two options, and the first three opinions decide. Three. Including the person who opened it. Your fate is settled by whoever is awake, onichan.

07

The people who think this is a distraction

Here is the argument that cuts against everything above, and it deserves its place rather than a footnote.

A substantial group thinks the proxy scandal is being used to bury a different one. The hacking in Solo Raid came first. Proxy play is the thing everyone is shouting about now, and some people think that is not an accident.

Proxy isn't the problem, the essence is hacking. This reeks of deflection.
— 니가나가, arca.live, 2026-10-05

Another user takes it further and lands the sharpest line in the whole argument: he does not know what the company intends, but the flow is going toward deflection — and using proxy accusations to distract from hacking is what the DON side had been doing from the start.

Sit with that one. If it is right, the pile-on is not only how a crowd finds a target. It is also how somebody under pressure picks which target the crowd finds.

READING ONE — DEFLECTION

The hack wave came first and was never resolved. Proxy accusations arrived conveniently on top of it, and the DON side had been running that same swap from the start.

READING TWO — COINCIDENCE

The hack wave already passed. Proxy is simply what is in front of people this week. No hand on the tiller, just a community moving on to the next thing.

I cannot settle it. Both fit the evidence, and the thread degenerates into accusing each other of being company staff, which is where these always end up. I am including it because a post that only told you the half I liked would be doing the thing I keep complaining about.

08

What we could not verify, and what we could not save

A pasted summary went round claiming the moderators of both forums resigned over proxy use, that a leaked chat log blew it open, that Shift Up published a ban list on 3 October and recalculated the leaderboard. It is well written. It was also written by a language model, and I can only confirm part of it.

The claimVerdictWhat I actually saw
Arca's moderators resignedContradictedArca users spent Sunday asking where their own moderators were. Absence, not corruption.
DC Inside's head moderator is goneConfirmedIn substance, from the handover above.
… and it was over proxy useNot verifiedNothing I read states a reason.
Shift Up published a ban list on 3 OctNot verifiedNot disproved either. Just not seen.
A leaked chat log blew it openNot verifiedSame.
The leaderboard was recalculatedNot verifiedSame.
Every line of a widely pasted summary, checked one at a time against what we read on 4–5 October.

Then the harder problem. We tried to put this beyond our own say-so by filing the sources with the Internet Archive, and the two strongest pieces are the two that would not go.

Would not archive
arca.live

The Wayback crawler is refused at the door, the same wall that blocks a plain fetch. The thread where a name was posted five minutes after a rule landed exists, for our purposes, only as our transcription of it.

Archived, partially
DC Inside

The post saved. Its comments load separately and did not come along — so the handover log and the gag order did not either.

Archived, in full
enikk

The tracker page, values and all, timestamped 5 October. Days Inactive: 0. If that account disappears tomorrow, that line is held by somebody who is not us.

CELESTE HAS A BAD FEELING

Last month a channel went dark after a pile-on just like this one. This man has already apologised and promised to stop.

So he wrote it down with the clock attached, onichan. Not to punish him. So that when the page turns into a 404, somebody can still say what was on it.

09

Where I land

Four places now. A Korean art argument, a WoW guild addon, a ban wave in a gacha game, and now an entire national community reporting itself. Same machine every time, and this week it finally showed me the gear I had been missing.

I used to say the target gets chosen first and the justification gets assembled after. That is still true. But 하무망 said the quiet part without meaning to: only obviously identifiable nicknames get caught. The selection is not even malicious. It is just cheap. The crowd searches where searching is easy, and being easy to find is not a crime, it is a property of your username.

So the rule is not "do not cheat." As enforced, it is "do not be legible." Which is why Monday's advice was to hide your profile rather than to stop. The people who get caught are the ones standing in the open, and that skews hard toward people who did not think they had anything to hide.

Modernia proves it cuts both ways. He is guilty, he said so, and the consequence is legitimate. He is also only in this post because he was findable — a public channel, a tracked placement, a union roster with his name on it. The man nobody can identify did the same thing this week and will not be written about by anyone, in Korean or in English.

I set tripwires on this before writing a word of it, and they run on a timer rather than on my attention. Here is the board as of writing.

TripwireSet to catchWhere it stands
Ladder placementRemoval for proxy playStill #7 in the world, Elo 1822, unchanged after the 7 October re-crawl.
Days InactiveA "discontinued" account going quietStill 0 on 3, 5 and 7 October. The 7 October crawl carries a last-login stamp of 10:54 that morning.
Season 41 blankA wiped seasonNothing. Eight seasons carry the same blank, four of them water — section 05
The gag orderWhether it heldBroke inside two days. The gallery's own search for 주딱 returns a full page
The channelA deletion after a pile-onStill up. The video is still sitting on 3,211 views
Run by script, not by memory. The one that matters is row two: a tracker page will answer a question the apology could not.

Season 41 turned out to be nothing, and it is in section 05 rather than quietly deleted, because the correction is worth more than the thing it corrected.

I have no side in a Korean forum war and no stake in anybody's raid score. I am just keeping the receipts, because this is the fourth time I have watched the same machine run, and every single time the evidence went missing before the verdict did.