chapter 14
10 min read
Chapter 14
This Looks Like Ransomware
"Move aside!"
Several employees came running from the end of the corridor. It was the hospital's IT team.
"How much is down?" "Charts, prescriptions, test results. Everything. They say even PACS, the medical imaging system, won't open in the operating rooms." "Even imaging?"
The IT employee's expression hardened. He immediately sat down at the nearest computer. After typing several commands and checking the server status, his hands stopped.
"...This looks like ransomware." "Ransomware?" "...Yes. All the files have been encrypted."
Ransomware. A portmanteau of "ransom" and "software." Malware that infiltrates a computer, encrypts its files, then threatens the victim to pay if they want to use them again.
It was also one of black-hat hackers' favorite ways of making money. If they stole information directly, they had to find buyers. If they wanted to extort someone, they had to stay in contact with the victim and negotiate. But ransomware was convenient. Spread the malware, lock the files, leave a message demanding money, and the victim came to you.
The more desperate the victim was, the higher the likelihood they'd pay. Which made hospitals, where people's lives were at stake, ideal prey.
"How the hell did this get in...?"
The IT team leader's face turned pale.
"Um..."
A trembling voice came from behind. An administrative employee was standing there with a pale face and one hand raised.
"We were hiring a few weeks ago, remember?" "And?" "We got an email from an applicant... There was a job application attached."
The employee's voice grew quieter.
"It was a word-processing document. I thought it was just a normal résumé and opened it. I think some strange window flashed for a moment back then..."
Everyone's eyes turned toward the employee at once.
"Why are you only saying that now?!" "I-I'm sorry. Nothing happened at the time..."
The IT team leader clenched his teeth.
"...Forget it. We can assign blame later. Right now, recovery comes first."
Systems throughout the hospital had already stopped. Medication was being postponed because prescriptions couldn't be confirmed, and operating rooms couldn't access medical images.
The IT team leader rebooted the infected PC. An unfamiliar text file had appeared on the desktop.
"A ransom note." "What's that?" "A warning file hackers leave for victims after ransomware encrypts their files."
[READ_ME_NOW.txt]
When he opened the ransom note, a short message appeared. A Bitcoin wallet address and payment instructions.
"Th-they want us to send money?" "..."
No one could answer easily. The IT team leader finally spoke weakly.
"...Let's follow the manual for now."
Then he looked toward the IT staff and gave instructions.
"Disconnect confirmed infected equipment from the network first, and check whether additional encryption is still occurring on the servers. Don't power anything off carelessly." "Yes." "Report the security incident to KISA immediately too."
A short while later. They connected to a KISA representative.
—What symptoms are you currently experiencing? "Files have been encrypted across multiple segments of the hospital's internal network. We can't access EMR or PACS either, and we've confirmed a ransom note."
The voice on the other end immediately became serious.
—First, we need to prevent further spread. Isolate the infected segments from the network. Do not delete logs, ransom notes, or suspicious files. Preserve everything as it is. "We're already doing that."
The IT team leader answered while gesturing toward an employee beside him.
"Has PACS been isolated?" "Yes. I think we've stopped further spread for now."
But that didn't solve the problem. The locked files remained locked.
—Preserve the malware sample in its original form and send it to us. We'll first identify what type of ransomware it is.
An IT employee transmitted one encrypted file and the ransom note. The wait felt unusually long. A few minutes later, an answer finally came through the phone.
—This differs somewhat from previously reported types. There's a possibility it's a variant.
A ransomware variant. In other words, there was no way to decrypt it using recovery tools currently available to the public. Despair appeared on everyone's faces.
"...Then can't we just pay? The hospital can pay first, and later..."
The answer came immediately from the other end.
—There is no guarantee that paying will get you the decryption key, the key required to return encrypted data to its original form. Many attackers cut off contact after receiving payment. Organizations that pay once may also be marked as targets for future attacks. "Don't pay. There's no recovery tool. Then what are we supposed to do?!"
A doctor who had come out of the operating room finally snatched the phone away.
"We can't even view CT scans right now! We can't confirm prescriptions, and patient charts won't open!" —We're searching for every possible recovery method as quickly as possible... "How quickly is 'as quickly as possible'?" —It's difficult to promise immediate restoration. For now, switch to emergency medical procedures, and consider transferring critical patients to nearby medical institutions... "Transfer them?"
The doctor let out a hollow laugh.
"Do you have any idea how many patients are hospitalized here? There are patients who need surgery right now. People are going to die!"
No one dared stop him. Even the IT employees simply stared at their monitors.
"Excuse me."
An unfamiliar voice cut in. Everyone turned toward one side.
"Can I take a look?"
The IT team leader stared at Juhak in confusion.
"What exactly is a student going to look at?" "The ransomware."
The answer was so confident that the IT team leader could only stare before asking.
"...What do you do?" "I work at White Securion."
Juhak thought for a moment, then added.
"I'm a white-hat hacker recognized by Representative Jeong Sejun."
* * *
Jeong Sejun's phone rang.
"Yes, this is Jeong Sejun." —Representative Jeong. This is KISA. I'm calling because there's something we need to confirm. "Go ahead." —Does someone named Seo Juhak work at White Securion? "Yes. He's an employee who works with me. What's going on?" —He's currently at a hospital suffering a ransomware incident, and he's saying he wants to respond to it himself.
"A hospital?"
At that moment. Jeong Sejun remembered what Juhak had told him a few days ago.
—My mother is having surgery.
Jeong Sejun shot to his feet.
"Is it Hanwon University Hospital?" —That's correct. "Then you can let him handle it."
The answer came immediately.
—Excuse me? "Seo Juhak has hands-on experience responding to security incidents and conducting penetration tests. I personally guarantee his skill."
Jeong Sejun quickly spoke while putting on his coat.
"And I'm heading to the hospital right now. Until I arrive, please allow Juhak to work with the hospital's IT team and examine the incident."
The KISA representative hesitated for a moment before finally answering.
—...Understood. We'll inform the hospital as well.
The moment the call ended, Jeong Sejun got into a taxi. Then immediately opened his laptop. His expression wasn't good.
Reverse-engineering encrypted data and recovering the key? It wasn't nearly as easy as it sounded. If the encryption had been designed properly, it would be practically impossible. And this wasn't a situation where they could spend days analyzing it in a laboratory. Patients' lives were at stake right now.
'...This is the worst possible situation.'
Some degree of damage was probably inevitable. In that case...
'Juhak only needs to stop it from becoming the absolute worst.'
He could only hope Juhak would hold things together until he arrived.
* * *
Once KISA had confirmed Juhak's identity, the IT team leader gave him access.
"This is the PC we suspect was initially infected, like I mentioned earlier." "You haven't powered it off, right?" "No. We've only disconnected it from the network."
The problematic computer remained powered on with only its network cable unplugged. Just like the other infected PCs, a ransom note was displayed on the screen.
Juhak quickly pulled over a chair and sat down. His mother was still inside the operating room. There was no time to waste.
Juhak placed both hands on the keyboard. At that moment.
FLASH!
Brilliant light poured from the monitor.
* * *
Thud!
The moment Juhak's feet touched the ground, he immediately looked around. It was a familiar place.
"...This is the hospital?"
The university hospital he'd just been in. But the atmosphere was completely different.
Bzzzt...
The fluorescent lights on the ceiling flickered irregularly. At the same time, a mechanical tone like tinnitus rang out endlessly.
Beeeeeeep—
The sound never stopped. Juhak frowned.
"...This feels disgusting."
Juhak slowly walked forward. With no one around, his footsteps echoed unusually loudly. After only a few steps, he noticed something strange. Pitch-black matter had spread across the walls and floor.
When he approached, he realized what it was. Black padlocks.
Patient room doors, examination rooms, testing rooms. Every door had a black padlock hanging from it. There were even black padlocks wedged into the gaps of filing cabinets. It looked as though the entire hospital had become a prison.
Clank!
Juhak grabbed a padlock hanging from a nearby door and pulled, but it didn't move at all. In that case... He raised his fist and struck it.
Tap!
Nothing happened. This time, he put real force behind it.
BANG!
A crack appeared in the padlock. But at the same time.
Crack!
The door holding the padlock began breaking as well. If he simply overwhelmed it with force, he could probably destroy the lock. But it felt like whatever was inside would be damaged along with it.
'...I can't do that.'
If the data were damaged. If there were even the slightest chance that data was connected to patients...
He had to be as careful as possible.
'Stay calm. If you get emotional, you lose.'
It was the same in the ring. If you got worked up and started throwing punches first, you inevitably created an opening.
Juhak slowly exhaled and looked around. Then he noticed something he hadn't seen before.
"...Threads?"
Thin black threads extended from every padlock. They all led in one direction toward the end of the corridor. Juhak immediately followed them. And then.
Squelch— Squelch—
Something walked out of the darkness. Juhak's gaze stopped on its face.
A guard covered from head to toe in black armor. Where its eyes should have been were only two dark, hollow pits. It had no nose at all, and its mouth was split all the way to beneath its ears. And inside that mouth...
Instead of teeth, dozens of tiny keys were packed tightly together.
Clatter— Clatter—
Every time it breathed, the keys struck against one another, producing an unpleasant sound.
"...What a fucked-up thing."
The moment Juhak took a step closer. The guard's head snapped toward him. Despite having no eyes, it stared directly at him.
Whoosh——!
The guard swung the iron club in its hand.
"...!"
Juhak instinctively leaned his upper body backward.
BOOOOM!
The club smashed into the wall and destroyed it completely.
'...It's ridiculously strong.'
But it wasn't fast. When Juhak widened the distance, it couldn't keep up. In that case...
Tap!
He slipped back inside. When the club came swinging, he stepped outside its path.
Slip. Weave. Movements he'd repeated thousands of times.
Whoosh! Whoosh!
The massive club cut only through empty air. And the moment the guard's side opened wide.
"Hup!"
Juhak fired a left jab followed by a right straight. The guard's torso rocked. At that instant, Juhak stepped in once more and drove an uppercut precisely into its jaw.
Clatter-clatter-clatter!
The guard's torn mouth opened wide, and the keys embedded inside shook violently. And finally.
Craaaack!
A crack beginning at its jaw spread down through its neck and across the entire suit of armor. The giant body exploded into pitch-black fragments.
Clatter.
All that remained were the iron club and a bundle of dozens of black keys lying on the floor. Juhak bent down and picked up the bundle.
At that moment. Hundreds of black threads simultaneously pulled taut.
* * *
Clack-clack-clack-clack!
Juhak's fingers began moving frantically across the keyboard. The IT staff stared blankly at the screen.
The PC suspected of being the initial infection point. The processes running inside it and its memory regions were scanned one after another. Countless strings and pieces of data filled the screen, disappeared, and then one particular value was isolated.
「KEY MATERIAL: EXTRACTED」
"...No way?"
The IT team leader unconsciously leaned forward. Traces used by the ransomware to encrypt the files. More precisely, data related to the key that had remained in memory during the encryption process.
'This is basically the same as stealing the key straight from the hacker's hand...!'
Juhak took his hands off the keyboard. Then he pulled the laptop he'd brought from his bag.
"You're not going to keep working on the infected PC?" "I found what I needed."
There was no reason to touch the infected machine any further. Carelessly messing with it could erase traces that still remained. Juhak transferred the recovered values to his analysis laptop.
Clack-clack-clack!
His fingers moved again. Using the discovered key material, he created a simple decryption program and immediately loaded a copy of one encrypted file.
「DECRYPTING...」
Progress appeared on the screen.
10%. 32%. 67%.
The IT team leader watched without breathing.
「SUCCESS」
"...!"
The file that had refused to open now opened normally. The file that had been an incomprehensible lump of data moments earlier had returned to its original form.
The IT team leader immediately compared it with another file. The header was normal. The contents were normal. There were no signs of corruption.
"It really... decrypted."
Short exclamations erupted around them. But Juhak had no time to celebrate and simply checked the screen.
"We should be able to decrypt everything with this. But,"
Juhak looked toward the operating rooms.
"Restore the systems needed for surgery first."