As he wiped the glass panels near the executive conference room, he noticed a strange pattern on a wall-mounted security monitor. The screen displayed a sequence of warning symbols that appeared, disappeared, and returned in precisely the same order. Thomas stopped his cart and studied the display. He recognized the pattern immediately. It resembled a diagnostic sequence from a security architecture he had helped design decades earlier.
He approached the monitor carefully. The system was showing repeated attempts to access a protected administrative channel. Whoever was behind the activity was not simply trying to enter the network. They appeared to be using an outdated authorization method to conceal their movements from the modern monitoring software.
Thomas felt a chill move through him.
He had warned the original engineering team about this weakness years ago. The vulnerability had been corrected in one version of the platform, but he had never been certain whether every older component had been replaced. If a malicious user had discovered the remaining weakness, they might be able to move through the network without triggering the usual alarms.
Suddenly, the lights in the corridor flickered.
A loud electronic chime sounded from the trading department, followed by several voices shouting in alarm. Thomas hurried toward the glass doors and saw employees gathered around their computer screens. Transactions were freezing, account balances were displaying inconsistent information, and the main financial dashboard had turned red.
Within minutes, the company’s emergency response team arrived. Engineers rushed between departments, security personnel restricted access to the server floors, and executives began calling one another from their cars.
Alexander Sterling returned to the building before nine o’clock. He found Victor Lang arguing with the technical director near the main operations room. The director explained that someone had interfered with the system’s authorization controls, but the source of the intrusion remained unknown.
Victor immediately blamed an external cyberattack. He demanded that the network be shut down and insisted that the company notify its banking partners before rumors began spreading.
Thomas stood quietly at the edge of the corridor, listening.
He knew that shutting down the entire system without isolating the compromised component could destroy evidence and make recovery far more difficult. He also recognized that the attack had been designed to resemble an external intrusion, even though several commands appeared to originate from a trusted internal account.
For the first time in twenty-five years, Thomas felt the old engineer inside him awaken.
He approached a young technician and asked whether anyone had examined the authorization logs from the older security module.
The technician barely looked at him.
“Sir, this is an emergency. Please return to your assigned area.”
Thomas stepped back, but he did not stop watching the screens.
The company was losing control of its systems, and the people responsible for saving it were looking in the wrong direction.
CHAPTER 4: THE JANITOR WHO KNEW TOO MUCH
By midnight, Sterling International had temporarily suspended several major operations. Clients were demanding explanations, financial partners were requesting verification reports, and the company’s board members were joining an emergency conference call. The technical team had isolated part of the network, but every attempted recovery produced another unexpected error.
Thomas continued working in the corridors, although his cleaning cart had remained untouched for nearly an hour. He watched the engineers enter and leave the operations room, carrying printouts and speaking in increasingly frustrated voices.
Eventually, he noticed a young engineer named Olivia Chen sitting alone near a service elevator. She was staring at a diagnostic report, her face pale with exhaustion. Olivia had joined the company only eight months earlier and had quickly become known for her exceptional technical ability. Now, however, she was being blamed for failing to identify the weakness before the attack.
Thomas approached her and asked whether the repeated authorization failures originated from the old compatibility layer.
Olivia looked up sharply.
“How do you know about that layer?”
Thomas hesitated. He knew that explaining his past would raise questions he was not prepared to answer. Instead, he asked to see the error sequence.
Olivia initially refused, but the strange accuracy of his question made her reconsider. She showed him a sanitized diagnostic screen without revealing any confidential credentials. Thomas studied the sequence for less than a minute before pointing toward three entries that the current monitoring software had classified as harmless system activity.
“These commands are not harmless,” he explained. “They are using the legacy authentication process to imitate a trusted maintenance routine. If you continue restarting the main service, the attacker may simply regain access through the same channel.”
Olivia stared at him.
The explanation matched a theory she had been unable to prove. She hurried back to the operations room and asked the senior engineers to review the flagged entries. They dismissed the suggestion at first, insisting that a janitor could not possibly understand the company’s internal architecture.
But Olivia presented the evidence, and one of the engineers finally recognized the pattern.
They isolated the vulnerable component and discovered that the suspicious commands had been repeated for several weeks before the major outage. Someone had been testing the system’s defenses long before the attack became visible.
When Olivia returned to thank Thomas, she found him pushing his cart toward the elevators.
“Please,” she said, “you need to explain how you recognized that sequence.”
Thomas looked at the security camera above the corridor, then back at her.
“I used to work with systems like this,” he replied quietly.
“Where?”
He paused for a moment.
“Here.”
Before Olivia could ask another question, the elevator doors closed between them.
For the first time that night, the technical team had a clear direction. Yet an even more disturbing discovery was waiting inside the recovered logs: the attack had been initiated through an account belonging to someone with senior administrative privileges.
The enemy was already inside the building.
And Thomas had a terrible feeling that he knew exactly why.
CHAPTER 5: A NAME BURIED IN THE PAST
The following morning, Alexander Sterling called an emergency meeting with the company’s senior executives. The outage had been contained, but the investigation suggested that confidential financial records might have been accessed. Several clients had temporarily suspended new transactions, and the company’s stock price had begun falling before the market opened.
Olivia presented the technical findings and explained how an outdated authentication component had been exploited. She also acknowledged that an unidentified employee outside the technical department had recognized the suspicious pattern before the engineering team did.
Alexander frowned.
“Who was it?”
Olivia glanced toward the door.
“Thomas Bennett. He’s a janitor on the executive floor.”