chapter 27
10 min read
Chapter 27
Ranking Korea's White-Hat Hackers
When the designated time arrived, signs of people began appearing beyond the fortress walls one by one.
"They're here."
The first were people wandering back and forth along the walls.
Bang! Bang!
Whenever they found something resembling a door, they kicked it without hesitation, then placed their hands on the wall and muttered.
"Admin... manager... admin page..."
Juhak narrowed his eyes.
'They're blindly guessing administrator addresses.'
/admin. /manager. /administrator.
It was an extremely basic reconnaissance method—trying common administrative paths at random.
"That won't work."
Juhak approached from behind and struck the back of the man's neck with the edge of his hand.
Thud.
First elimination.
A little farther away, another man was crouched in front of the fortress gate.
Clink— Clink—
Hundreds of keys hung from his waist. He was trying them in the lock one by one.
"This is... brute force."
A method of indiscriminately trying every possible combination of letters and numbers until the correct password appeared. Juhak watched for a moment.
Clink. Wrong.
Clink. Wrong again.
Clink.
"...No reason for me to wait for that."
Smack!
Second one unconscious. Two attackers went down back-to-back.
'This isn't bad.'
So far, he still had plenty of room. It was surprisingly fun too.
Before, Jeong Sejun had explained these attack methods to him, and he'd only understood them in his head. Now people were demonstrating them directly in front of him through their actions. Literally hands-on training. But then.
"...Huh?"
About ten minutes later, the number of people began increasing rapidly. Their attack methods grew stranger and stranger too.
"Intruder! Stop him!"
One man dressed as a guard ran toward another attacker as if trying to restrain him. Then he subtly passed Juhak and tried to stroll naturally inside the fortress.
"Where do you think you're going?" "Urgh!"
Elsewhere, someone was literally digging into the ground with a shovel.
Thud! Thud! Thud!
He had no interest in the main gate at all. Apparently he intended to tunnel beneath the fortress wall and come up inside. And that wasn't all.
Someone threw ropes. Someone searched for cracks in the wall. Someone stood far away and merely observed the inside through a telescope.
'...Looks like.'
Stopping everyone from getting in at all might be impossible.
'Change of tactics.'
Let whoever was going to enter, enter. Instead, he'd protect the flag inside the walls.
He subdued the attackers rushing him and quickly ran inward. Several followed. Juhak pulled the Execution Sword from behind his back and twisted his waist.
WHOOOSH!
The Execution Sword traced a huge circle and cut through three people at once. Then.
Fssss!
Their bodies transformed into blue particles and scattered into the air. But then.
"...?"
The particles suddenly changed direction.
Swoooosh...
They seeped into the blade of the Execution Sword as though being absorbed. The sword's blue glow deepened slightly, and he felt a faint vibration in his hand.
'What the hell?'
It was surprising, but he had no time to examine it. People were still pouring through different parts of the fortress wall.
'Someone might sneak in through a blind spot and steal only the flag...'
Juhak pulled the flag out from the pillar where it had been planted. The flag in his left hand. The man-sized Execution Sword in his right.
Then he swung the sword at the people swarming toward him like zombies.
BOOOOM!
* * *
At the same time. A study cafe somewhere in Seoul. Four employees responsible for penetration testing at the security team of a major corporation had their laptops open. They had spent years performing attack simulations professionally.
"I'll handle the first entry point." "If that gets blocked, we'll immediately move to the adjacent route."
At first, they were relaxed. They found a weakness in the API permission structure and pushed a request inward while making it appear legitimate.
[SESSION REVOKED]
"Blocked." "Within expectations. Next."
They immediately destabilized the intermediate cache layer. By creating a discrepancy between how external requests and internal services interpreted the same data.
"Okay. We're in."
One stage. Then two. The administrative area was almost within reach. But at that moment.
[ROUTE INVALIDATED] [CACHE POLICY UPDATED] [SESSION TERMINATED]
The entire connection was severed. Even stranger was what happened afterward. They tried the same route again, but the path they'd clearly used moments earlier had disappeared.
Which meant. The defender hadn't simply blocked a single request. They'd identified where the problem occurred and changed the defensive structure itself on the spot.
Silence fell briefly. Then the most experienced man on the team let out a hollow laugh.
"This... isn't automated defense." "...What?" "It's watching our attack pattern... and changing the defensive structure in real time."
A card shown once didn't work twice. The path they created moments earlier was immediately analyzed and closed.
"Insane..."
Eventually.
[GG. I'm giving up on the 100 million.]
That day, similar reviews began appearing all over security communities.
—Spent an hour on it and there's no way through; —Went in thinking it'd be easy and only got my pride hacked —Same attack doesn't work twice; looks like real-time response —Conclusion: This was clearly built with no intention of giving away the 100 million
The more people failed, the more excited everyone became.
—It's really that hard? —Now I suddenly want to try it —Joining after I finish overtime tonight —Let's see who gets it first lol
As the number of failures increased, the mood gradually shifted. At first, everyone had been interested in who would take the one hundred million. Now.
—Can anyone actually break this? —At this point don't we need someone at the absolute top of the industry? —Call Blue Fox lol └That guy specializes in web. He might actually do it —Wouldn't this end instantly if WithDay shows up? └Someone tag him lol └He's probably been watching this whole time. His pride won't let him ignore it
Nicknames of famous white-hat hackers in the community began appearing one after another. Who would be the first to break through? Who was skilled enough to face Counter?
Someone even posted a ranked list of likely candidates.
[TOP 5 Korean White-Hat Hackers Most Likely to Break Counter's Server]
After the post climbed into the real-time trending list. A new post appeared. The author was a famous white-hat hacker whose name had been mentioned repeatedly.
[Interesting. I'll finish this before dinner.]
The security community immediately exploded.
—He's here lolololol —He actually showed up —This guy might genuinely pull it off —Is he Guan Yu saying he'll bring back the enemy general's head before the wine cools? lol
Judging by the confidence, it really looked as though the whole thing would end within a few hours. But. One hour passed. Two. Three. No follow-up appeared. Then at some point. The post quietly disappeared.
—LOL deleted-and-ran ending —??? Where's the FLAG, sir? —Your dinner must be stone cold by now lol —Was this site actually made to publicly execute people one by one? Everyone just leaves with their pride shattered
Someone had been watching the entire sequence from the beginning. Choi Donghyeok, a reporter for Security Map, a major domestic cybersecurity publication. His scrolling grew faster and faster.
'...This is fucking entertaining.'
Recently, cybersecurity news had been nothing but grim stories like personal information leaks. But this was different. Nobody had ordered them to do it, yet white-hat hackers from across the country were voluntarily gathering to compete. It was practically a live hacking defense competition. And on top of that.
"Smart."
Black-hat hackers would have difficulty collecting the prize even if they won. To claim one hundred million won, they'd eventually have to reveal their identity.
In the end, the only people who could properly enter this battlefield were white-hat hackers willing to put their own names behind their actions. One prize attracted skilled people. And at the same time, Counter got to prove his own ability. It was an extremely clever form of promotion.
Choi Donghyeok opened a new document.
'I don't know who'll win yet, but...'
This was already enough to draft the headline.
Clack-clack-clack.
["Break In and Win 100 Million" — Mysterious White-Hat Hacker 'Counter' Challenges Korea's White-Hat Hackers]
* * *
A short while later. The time limit expired. The front page of Juhak's website, Counter Security, changed.
[CHALLENGE CLOSED] [ATTACK SESSIONS: 3,821] [FLAG CAPTURED: 0]
A total of 3,821 attack attempts. Zero successes. Not a single person had gained administrator privileges and registered the FLAG. The security communities immediately erupted.
—Holy shit, nobody got through all the way to the end —He took 3,821 attacks and blocked every one? —Kept his 100 million lololol
Then, as though waiting for the moment, an article appeared.
["Break In and Win 100 Million" — Mysterious White-Hat Hacker 'Counter' Challenges Korea's White-Hat Hackers]
It was written by Security Map reporter Choi Donghyeok.
「Major university cybersecurity clubs, security teams from large corporations, and even famous white-hat hackers participated in the challenge, but all failed.」 「According to participants, Counter appears not to rely solely on automated defensive solutions, instead identifying attack patterns in real time and responding immediately.」 「Once an attack route was discovered, it was rapidly patched, and additional countermeasures followed whenever new bypass routes appeared...」
The article ended with an especially provocative line.
「In effect, this challenge was closer to a public verification test against South Korea's white-hat hacker community.」 「In an era where data protection and service stability directly determine corporate trust, attention is now turning to whether a new game changer has emerged in the domestic security industry.」
The article rapidly spread throughout the cybersecurity industry. At first, people were simply curious. Then professionals who had personally participated in the challenge began adding their own comments.
[I tried it myself. His skill is real.] [It wasn't just automated defense running in the background. He responds as soon as an attack comes in.] [Once a route gets breached, it's closed almost immediately.]
From that point, the atmosphere changed.
Ding.
The first inquiry arrived.
[We would like to ask whether penetration testing services are available.]
Ding! Ding! Ding! Juhak's phone rang without pause.
[We would like to inquire about a company-wide security vulnerability assessment.] [We would like to request an emergency incident response contract.] [We would like to schedule a meeting regarding security consulting.]
What began as a handful of inquiries quickly passed dozens. It was the exact opposite of the situation only a few days earlier.
Before, when Juhak contacted companies first, they asked about competition awards or certifications. Now nobody asked. The results publicly witnessed by the entire country had already proven everything for him. Among the messages, one familiar company name caught his eye.
[Hello. We're contacting you again regarding the matter you previously inquired about.]
Only a few days earlier. They had asked about his experience and education, then left him on read.
[If possible, we would like to coordinate a meeting with our executive team.]
"..."
Juhak stared at the screen for a moment.
[How much are you prepared to spend?]
He wanted to type that. But even so, there was such a thing as professionalism. That might be a little much.
[Yes. That is possible.]
Then he added another line.
[However, I am currently receiving a large number of requests, so the quote may differ somewhat from what I previously mentioned.]
Send.
From now on, his market value would start rising on its own.
* * *
Meanwhile. Coinwand, a major domestic cryptocurrency exchange.
"It's showing up again."
The atmosphere inside the security operations center was heavy. Because the monitors kept detecting unusual patterns unlike anything normal.
The transactions themselves were normal. There were no problems with deposits or withdrawals. But.
"There's definitely something..."
The security team leader clenched his teeth. They had even brought in an outside security company and spent days combing through the logs. They checked for signs of intrusion and inspected every server and wallet system. But they couldn't find the cause.
"Could it be a false positive?" "No. If it were a false positive, there'd be no reason for the same pattern to keep repeating..."
They didn't know what was happening. Which meant they didn't know what they needed to block. Few situations were more dangerous for a cryptocurrency exchange.
"Haah..."
The CEO's gaze shifted toward a massive monitor showing the exchange's assets.
Trillions of won.
If something went wrong, this wouldn't end with a few numbers moving on a screen. Then the CEO remembered an article he'd recently read.
"Wasn't there that company that caused a stir recently? They offered one hundred million to anyone who could break in, and nobody managed it." "Ah... yes! That's right. Apparently they analyzed attack patterns in real time and responded immediately..." "Contact them."
The CEO bit his lip and continued.
"I don't care what price they name. Bring them here and solve this."