The next morning, I arrived before sunrise.
The factory lights were still off in several sections when I walked through the main entrance.
I didn't tell the floor staff what I had found.
Not yet.
Fear spread faster than information.
If someone inside Horizon was helping an outside attacker, announcing the investigation could make the problem worse.
I went directly to the server room.
The IT manager, Samuel Ortiz, was already waiting.
“You asked for the network records.”
“I did.”
He handed me a drive.
“I pulled everything from the last ninety days.”
“Good.”
“There’s something you should know.”
I looked at him.
“What?”
“Richard's old account wasn't the only one touched.”
I stopped.
“What else?”
“An engineering service account.”
“Whose?”
“Yours.”
I stared at him.
“My account was terminated when I left.”
“It was.”
“Then why does the log show activity?”
Samuel opened the report.
My old employee account had been used six days after my termination.
Not to access Meridian.
To access the maintenance gateway.
I looked at the timestamp.
2:17 a.m.
I had been home.
My new company didn't yet have employees working overnight.
“Who had access to my credentials?”
Samuel shook his head.
“That’s what I don't know.”
I leaned closer.
The session had lasted four minutes.
Long enough to authenticate.
Not long enough to change anything significant.
“Maybe someone was testing whether my account still worked.”
Samuel nodded.
“That's what I think.”
“Then why use mine?”
He didn't answer.
I already knew.
Someone wanted the activity to look like it came from me.
The old employee who had suddenly become a contractor.
The engineer who had access to Meridian.
The man who had publicly exposed Richard's sabotage.
If something went wrong, I was the obvious person to blame.
I copied the records.
Then I called Eleanor.
She arrived with the company attorney.
We met in the same conference room where Richard's career had ended.
I placed the evidence on the table.
Eleanor studied it.
“They used your credentials.”
“Yes.”
“Could you have done it?”
The question was direct.
I respected that.
“No.”
“Can you prove it?”
“I can prove where I was.”
She shook her head.
“That's not enough.”
“I know.”
The attorney leaned forward.
“Then we need stronger evidence.”
I agreed.
The investigation changed after that.
We stopped looking for Richard.
We started looking for whoever was using his old access infrastructure.
Samuel traced the maintenance gateway to a backup server stored at a small Horizon warehouse.
The warehouse had been closed since Richard's departure.
Nobody had bothered to remove the equipment because it was considered obsolete.
Walter offered to come with us.
We drove there that afternoon.
The warehouse smelled of dust and old coolant.
Most of the equipment had been covered with plastic.
The backup server sat inside a locked metal cabinet.
Samuel opened it.
The machine was still running.
That surprised all of us.
“Who pays for this power?” Walter asked.
Samuel frowned.
“Horizon does.”
“Of course we do.”
I crouched beside the server.
There was a small USB adapter connected to the back.
I pointed.
“That wasn't part of the original installation.”
Samuel removed it carefully.
Inside was a wireless network adapter.
I looked at Walter.
“When was this warehouse last inspected?”
“Six months ago.”
“By whom?”
He thought.
“Richard.”
There it was again.
Richard's name.
But this time it wasn't enough.
We needed proof.
I checked the server logs.
Remote connections.
Repeated connections.
Some had occurred after Richard supposedly lost access.
Then I saw something familiar.
The same external address from Meridian.
I saved the logs.
Samuel whispered, “That's our connection.”
“Yes.”
Walter looked around the warehouse.
“Could someone still be coming here?”
I stood.
“Maybe.”
We searched the building.
Nothing.
Then Walter opened a storage cabinet.
Inside were several old maintenance binders.
He flipped through them.
“Ethan.”
I walked over.
He held up a folder.
Richard's handwriting was on the cover.
“Remote Maintenance Procedure.”
I opened it.
Inside were passwords, gateway configurations, emergency access codes, and handwritten notes.
Most were outdated.
One wasn't.
At the bottom of the final page was a note.
If access is lost, use secondary tunnel.
Beneath it was a sequence of numbers.
Samuel stared at it.
“That tunnel is still active.”
I looked at him.
“Can you shut it down?”
“Yes.”
“Do it.”
He reached for his phone.
Then stopped.
“Wait.”
“What?”
“The tunnel is currently active.”
We all looked at the server.
Someone was connected.
Right now.
I pulled out my laptop.
Samuel connected it to the server.
The remote session was live.
A user was browsing files.
Not machine controls.
Financial documents.
Contracts.
Invoices.
Customer records.
Someone wasn't trying to break Horizon's machines anymore.
They were looking for information.
“What are they downloading?” Eleanor asked.
I checked the transfer log.
“Everything.”
Samuel began blocking the connection.
The remote user disappeared.
Then a message appeared on the screen.
YOU SHOULD HAVE LEFT WELL ENOUGH ALONE.
Walter read it over my shoulder.
His face hardened.
“That's a threat.”
“Yes.”
Eleanor looked at me.
“Now we know.”
“What?”
“This isn't about Horizon.”
She pointed at the screen.
“It's about you.”
I shook my head.
“No.”
I looked at the access logs.
The remote user had searched for one particular file before disconnecting.
A contract.
Parker Precision Services.
My contract with Horizon.
Someone wanted the agreement.
And they had searched for the original pricing schedule.
That was the first time I realized what Richard might actually be trying to accomplish.
He wasn't trying to destroy Horizon.
He was trying to destroy the company I had built after leaving it.
Click here to continue reading: PART 7: The Contract Richard Wanted Was Worth Millions, but the File He Couldn’t Find Contained Something That Could Finally Expose Him
At 11:07 My Eleven-Year Career Ended, but Five Minutes Later the Machine They Blamed Me For Suddenly Became Their Biggest Problem
Part 6 of 20
