Surprise

Chapter 5

I stared at the payment record until the numbers stopped looking real.

Four hundred and fifty thousand dollars.

Transferred to Nia Whitmore through a consulting company connected to Victor Lang.

The payment had been made less than twenty-four hours before the server failure.

I looked at Simone.

“Could this be a legitimate consulting payment?”

“Possibly,” she said. “We need the contracts, account records, and an explanation of the services.”

Daniel leaned back in his chair.

“That's one expensive consultation.”

Simone gave him a warning look.

“Let's focus on what we can prove.”

I respected her for that.

After nearly losing my job because someone refused to investigate the facts, the last thing I wanted was to watch another person get condemned without evidence.

Still, the timing was difficult to ignore.

Nia had met Victor at midnight.

A storage device had been connected to an executive workstation.

Confidential merger documents had been accessed.

Then our systems had been attacked.

And the next morning, Nia had tried to fire the engineer who preserved the evidence.

Me.

Simone turned toward me.

“Malik, I want to review your incident report again.”

I opened the original file.

Every action I took during the recovery had been logged.

I showed her how I isolated the compromised administrative account, restored the monitoring service, and blocked the unauthorized export.

Then I explained one decision that had seemed minor at the time.

“When I noticed the configuration changes, I created a read-only snapshot before restoring the affected systems.”

Simone looked up.

“You preserved the original state?”

“Yes.”

“Without notifying executive operations?”

“I notified the emergency response channel. But I didn't allow anyone to modify the snapshot.”

She smiled faintly.

“That may be the most important decision you made.”

We spent the next two hours comparing the preserved logs with the workstation records.

The storage device had introduced a configuration package disguised as a routine maintenance update.

The package contained instructions to disable monitoring and create a temporary access route into the client database.

It also contained a scheduled command designed to erase selected event logs.

I had interrupted the command before it completed.

Daniel whistled softly.

“Somebody planned this.”

I nodded.

“Yes.”

Simone looked at the screen.

“And whoever planned it expected the evidence to disappear.”

The investigators began tracing the configuration package.

By evening, they had identified a development certificate associated with a private technology contractor.

That contractor had previously worked for Vanguard Digital Holdings.

The connection was becoming difficult to dismiss.

But the most painful discovery came when Simone showed me a draft internal communication recovered from the same workstation.

It had never been sent.

The subject line read:

OPERATIONAL FAILURE — TECHNICAL RESPONSIBILITY.

The document blamed the server outage on negligence by the internal engineering team.

It specifically named me.

I read the paragraph twice.

Malik Johnson failed to maintain critical security controls, resulting in unauthorized system access and significant operational disruption.

My stomach twisted.

The statement was false.

The preserved logs showed the opposite.

I had been the person who stopped the incident.

But whoever wrote that draft had intended to make me responsible.

I turned toward Simone.

“Was this prepared before the server failure?”

She checked the metadata.

“Yes. The original draft was created the previous afternoon.”

I felt my hands go cold.

Before the attack.

Before the recovery.

Before I fell asleep at my desk.

Someone had already planned to blame me.

I thought about Nia slamming the red termination folder beside my head.

Her anger.

Her refusal to hear my explanation.

Her determination to get me out of the building.

Maybe it hadn't been an impulsive decision.

Maybe I had been selected as the person who would take the fall.

I didn't say that aloud.

Not yet.

Simone was already documenting the discovery.

An hour later, Arthur arrived.

He read the draft statement in silence.

Then he looked at me.

“Malik, I'm sorry.”

I shook my head.

“I don't need another apology right now.”

He accepted that.

“What do you need?”

“I need to know whether your daughter was involved.”

Arthur closed his eyes briefly.

“So do I.”

I watched him carefully.

For all his authority, he looked like a father watching his family and his company move toward a disaster he couldn't prevent.

He had spent decades building Whitmore Technologies.

Now the person most likely to inherit his leadership role was under investigation for possible misconduct.

I didn't envy him.

But sympathy didn't mean I would protect Nia.

Arthur sat down.

“The audit committee has asked Nia to explain the payment.”

“What did she say?”

“She claims it was an advance for a consulting role she planned to accept after my retirement.”

Simone looked up.

“Did she disclose that role during the merger negotiations?”

“No.”

“Was she required to?”

“Yes.”

Arthur's voice was heavy.

“That alone is a serious conflict of interest.”

I looked at him.

“Did she know Vanguard planned to take control?”

Arthur nodded.

“She supported the proposal.”

“Did she know they intended to reduce the workforce?”

He hesitated.

“The merger models included significant restructuring.”

“How significant?”

Arthur looked toward the floor.

“Approximately forty percent of our current positions.”

I stared at him.

Forty percent.

Hundreds of employees.

People with families, mortgages, medical bills, and children preparing for college.

People like me.

I imagined Daniel being told his job had disappeared after years of loyal service.

I imagined the junior engineers I had trained.

I imagined the employees who stayed late without being asked, believing their sacrifices mattered.

Then I imagined Nia receiving nearly half a million dollars while defending a deal that could destroy their livelihoods.

Something hot and bitter rose inside my chest.

“Did the employees know?”

“No.”

“Were they going to be told before the vote?”

Arthur didn't answer.

That was answer enough.

I stood.

“Then you have a bigger problem than Nia.”

Arthur looked at me.

“I know.”

“No, sir. I don't think you do.”

My voice shook.

“You built a company where people are told they're family. But your board has been negotiating a deal that could erase almost half their jobs, and nobody thought those people deserved to know.”

Simone remained silent.

Arthur lowered his eyes.

For a moment, I worried I had gone too far.

Then he said quietly, “You're right.”

I wasn't expecting that.

He looked up.

“I allowed the board to convince me that discussing the restructuring would create unnecessary panic. I told myself we would explain everything after the decision.”

He shook his head.

“That was wrong.”

I sat down again.

The room felt heavy.

Arthur continued.

“Malik, I want to ask you something. Not as your CEO, but as someone who has spent his life building this company.”

I waited.

“If you were responsible for protecting Whitmore Technologies, what would you do?”

I thought about my mother.

She had worked two jobs to help me finish college.

She had never owned a company.

She had never sat in an executive boardroom.

But she understood something powerful people often forgot.

A business wasn't only its buildings or financial statements.

It was the people who kept it alive.

“I would tell the truth,” I said.

Arthur nodded slowly.

“Then that's what we'll do.”

That evening, the board's audit committee issued an internal notice confirming that an independent investigation was underway.

The proposed merger vote was postponed.

Employees were informed that potential restructuring plans existed and that no final agreement had been approved.

Arthur also announced an emergency town hall.

For the first time, people were allowed to ask questions without going through Nia's department.

The response was immediate.

Some employees were angry.

Others were frightened.

Many demanded to know how long the company had been considering a deal that might cost them their jobs.

I understood every question.

I had some of the same ones.

Before leaving, Simone called me back into the investigation room.

“We found another version of the draft statement.”

I frowned.

“Another version?”

She nodded.

“This one was prepared as a formal termination recommendation. It included the allegation that you had fallen asleep while responsible for monitoring the servers.”

My stomach tightened.

“Who created it?”

Simone turned the screen toward me.

The document's author field showed an executive operations account.

The account belonged to Nia Whitmore.

May you like

And the file had been created at 7:52 a.m.

Twenty-five minutes before she slammed the red folder beside my head.

Related Stories

Other posts