They Thought He Was Weak—Until the Truth About His Failed Mission Came to Light

Chapter 17

Theme:
Font Size:
24px

Mara showed her identification.

“I'm here for the Harborlight security review.”

The guard checked his tablet.

“We weren't told to expect you.”

“Then someone forgot to update the schedule.”

He hesitated before opening the gate.

Inside, Martin Shaw was waiting with two technicians.

“I'm glad you came,” he said. “We checked the maintenance records. The next systems test was scheduled for Thursday morning, but someone changed the time.”

“To when?”

“Two thirteen.”

Mara looked at him.

“Exactly?”

“Exactly.”

She glanced toward the corridor.

“Who changed it?”

“The request came through Peter Lang's department. The approval appears to have been entered using his credentials.”

“Have you contacted him?”

“He claims he knows nothing about it.”

“Of course he does.”

Martin gave her a sharp look.

“You think he's lying?”

“I think we need evidence before deciding.”

They entered the security room.

A wall of monitors displayed the loading bays, service corridors, equipment rooms, and perimeter gates. One technician opened the maintenance schedule while the other reviewed the access logs.

Mara studied the building's layout.

“What happens if the backup power system switches to emergency mode during the test?”

“The local inventory network transfers to a secondary controller,” the technician explained. “It should continue operating normally.”

“Should?”

“That's how the system is designed.”

“Has the transfer been tested under the current configuration?”

The technician paused.

“Not since the latest software update.”

Mara looked at Martin.

“Then the test should not proceed.”

“We've already suspended it.”

“Good. Now I want someone physically present at the backup controller.”

Martin turned toward the technician.

“Can you arrange that?”

“Absolutely.”

Mara checked her watch.

12:41 a.m.

They had more than an hour before the scheduled event.

She divided the work into three parts. One team would verify the access controls. Another would inspect the backup power system. Martin would coordinate the security response and ensure that no one entered the restricted corridor without authorization.

Mara would review the original maintenance records.

At 1:36 a.m., the first discrepancy appeared.

A maintenance credential had been used to access a service door.

At 1:49, a second credential was tested.

At 2:02, the system registered a failed attempt to access the emergency controller.

Mara stood beside the monitor.

“Freeze the logs. Preserve everything.”

The technician obeyed.

At 2:11, the corridor camera flickered.

For three seconds, the image disappeared.

When it returned, a figure in a dark maintenance uniform stood beside the electrical panel.

Martin moved closer.

“Can you identify him?”

“Not from this angle,” Mara said.

The figure opened the panel.

Then he looked directly toward the camera.

Mara felt her pulse quicken.

The man's face was partially visible beneath his cap.

She recognized the shape of his jaw.

The scar near his left ear.

The way he tilted his head before moving.

“Daniel,” she whispered.

The figure reached into the panel.

At 2:13, every monitor in the security room went black.

The lights remained on, but the wall of screens displayed nothing except a message.

YOU WERE WARNED.

One technician swore under his breath.

Martin immediately reached for his radio.

“Security team, report status.”

Static answered.

Mara did not move.

The message had been designed for her.

She could feel it.

The person responsible knew she would be watching. They knew the scheduled time, the building, and the system's vulnerabilities.

But the message itself was a distraction.

“Check the physical controller,” she said.

Martin turned.

“What?”

“The screens are down, but the lights are still on. We don't know whether the entire network has failed or only the surveillance feed. Check the controller.”

The technician rushed toward the equipment room.

Thirty seconds later, his voice came through the radio.

“Local power is stable. The controller is still active.”

Mara exhaled.

“Good. Do not attempt a remote reset. Isolate the affected surveillance segment and preserve the local records.”

Martin stared at the blank monitors.

“How did they do that?”

“I'm not sure.”

“Can they access the emergency logistics network?”

“We don't know yet.”

A door slammed somewhere outside.

Martin reached for his radio again.

“Security team, report.”

This time, a guard answered.

“Someone has opened the eastern service gate. We're checking the perimeter.”

Mara looked at the building diagram.

The eastern gate led toward a narrow access road behind the warehouse.

“Send someone to the gate,” she said. “But don't pursue anyone beyond the facility without a clear identification and a safe plan.”

Martin relayed the instruction.

They waited.

At 2:19, the surveillance system began recovering.

One monitor returned.

Then another.

The eastern corridor appeared on the screen.

The maintenance figure was gone.

The electrical panel remained open.

Mara studied the image.

“Send a technician to inspect that panel. Two people, with security present. No one touches anything until it's documented.”

Martin nodded.

“And the person who entered?”

“Find out whether anyone actually saw him leave.”

The guard reported that the eastern gate had been opened remotely. No vehicle had been recorded leaving the premises.

The figure had disappeared without appearing on the available exit cameras.

Mara looked at the time.

2:24 a.m.

The incident had lasted eleven minutes.

It had produced no confirmed damage, no verified theft, and no proof that the emergency logistics system had been compromised.

But it had demonstrated something important.

The person responsible could interfere with Northstar's surveillance at a precisely chosen moment.

And they had known Mara would be there.

Martin approached her.

“What do we do now?”

Mara looked at the dark corridor on the monitor.

“We stop treating this as a series of unrelated access violations.”

“Then what is it?”

She thought of the anonymous recording.

The mountain photograph.

The messages about Daniel.

“I think someone is recreating an old operation,” she said. “And I think we're being invited to make the same mistake twice.”

At 3:05 a.m., the western facility was secured.

The technicians had confirmed that the backup controller remained operational. The surveillance outage had affected a local network segment, but investigators had not yet established whether the interruption resulted from deliberate interference, a configuration fault, or a combination of both.

The electrical panel showed signs of recent handling.

News in the same category

They Thought He Was Weak—Until the Truth About His Failed Mission Came to Light

30 Part