Chapter 2 - THE WEBSITE FAILED AFTER I HAD ALREADY LEFT

I saved the video in four places.
Not because I wanted revenge.
Because people become imaginative when consequences arrive.
One copy went to encrypted cloud storage.
One to an external drive.
One to my attorney.
The fourth stayed in the camera archive.
Then I filed a police report.
I did not demand that a fifteen-year-old be dragged from his bed in handcuffs.
I reported intentional property destruction and provided the recording.
The officer who took the report watched the clip twice.
“Your sister told him to do it.”
“Yes.”
“And your father appears to hear.”
“Yes.”
“You want charges?”
“I want it documented.”
“That decision ultimately isn’t entirely yours.”
“I understand.”
Mason was a juvenile.
Marissa was an adult who instructed him.
Different questions.
I called my business insurer next.
Then my client.
The migration had completed successfully.
My project lead said:
“You sound weird.”
“My laptop got destroyed.”
“What?”
“Family issue.”
“Data breach?”
“No.”
“You sure?”
“Yes.”
Every active client secret had been stored in hardware-backed credential management.
The laptop drive was encrypted.
Remote-wipe queued anyway.
I had made my professional life resilient.
I just had not built the same resilience into my family.
At 8:30 the next morning, I bought a temporary replacement.
At 9:10, I sent one email to Dad and Marissa.
Effective immediately, Warren Outdoor Services needed to appoint an independent IT provider.
I would preserve existing systems for ten business days.
I would not make operational changes except security actions necessary to protect my own accounts and clients.
I would provide documentation to the new provider after receiving written authorization from the company owner.
No threats.
No shutdown.
No back billing.
No lecture.
At 9:22, Marissa called.
I let voicemail answer.
“Evan, are you serious? You’re going to punish eighteen employees because Mason broke a toy?”
Toy.
I saved the message.
At 9:37, Dad called.
I answered.
“What is this email?”
“Exactly what it says.”
“You’re quitting?”
“I was never employed.”
“Don’t play word games.”
“I’ve maintained Warren systems for free since 2016.”
“You’re my son.”
“That isn’t a job description.”
He exhaled hard.
“Just cool down.”
“I am calm.”
“That’s worse.”
I almost laughed.
“What do you need?”
“I need you not to do anything stupid.”
“I’m not.”
“Don’t turn off the website.”
“I won’t.”
“Phones.”
“I won’t.”
“Payments.”
“I won’t.”
He went quiet.
Then:
“Good.”
Something in the way he said it bothered me.
“Dad.”
“What?”
“Why did you ask Marissa whether Mason had the right laptop?”
Silence.
“I don’t know what you mean.”
“It’s on camera.”
Another pause.
“You record us?”
“The garage security system records the driveway.”
“That’s my house.”
“You asked me to install it.”
“You shouldn’t be listening to private conversations.”
I closed my eyes.
“My laptop was smashed in front of the camera.”
“That doesn’t answer me.”
“No.”
“It doesn’t.”
He hung up.
At 11:14, my phone started vibrating.
Three employees from Warren Outdoor Services.
Then a fourth.
I answered the office manager, Paula.
“Evan?”
“Hey.”
“The customer payment page isn’t working.”
My stomach tightened.
“What error?”
“Gateway authentication failed.”
I opened the monitoring dashboard.
The website was online.
Booking was online.
Email fine.
The payment API had been disabled.
I had not touched it.
“When did it stop?”
“Maybe twenty minutes ago.”
“Has Marissa changed anything?”
“I don’t know.”
“I’m no longer making changes directly. Dad needs to contact the new IT provider.”
“What new provider?”
“Ask him.”
“Evan, customers are calling.”
“I know.”
I hated saying it.
But touching the system now would make me responsible for a network someone else was changing behind me.
I logged into the cloud audit portal.
Payment connector.
Disabled at 10:53 a.m.
User:
EWARREN-ADMIN.
My account name.
My body went cold.
I checked sign-in location.
Warren Outdoor Services office.
Not my townhouse.
Not my new laptop.
Someone had used a legacy credential tied to my name.
I had created that admin identity years earlier before I understood how long “temporary” family arrangements last.
The credential should have been retired.
Apparently it wasn’t.
I called the independent MSP I had recommended to Dad, Riverbend Technology Group.
Their security director, Serena Cho, agreed to conduct an emergency read-only assessment if Dad authorized it.
He did within twenty minutes.
Because customers could not pay.
Serena called me at 2:40.
“Evan.”
“What did you find?”
“Your payment connector was disabled manually.”
“I know.”
“Using the legacy admin account.”
“Yes.”
“Did you log in today?”
“No.”
“Can you prove location?”
“Yes.”
“Good.”
She paused.
“There’s more.”
I sat straighter.
“What?”
“That same account has been used repeatedly for eighteen months.”
“For what?”
“Refund overrides.”
I frowned.
“I don’t process Warren refunds.”
“I figured.”
“How many?”
“We’re still counting.”
Then she said:
“Evan, someone has been doing financial activity under an administrator identity with your name attached to it.”
I stared at the damaged-laptop police report sitting beside me.
“From where?”
“Mostly the Warren office.”
“Which workstation?”
“We’re narrowing it.”
Then Serena’s voice changed.
“And last night there was an unsuccessful login attempt at 2:08 a.m.”
“After the laptop was destroyed.”
“Yes.”
“From where?”
May you like
She answered:
“Your father’s office.”
Related Stories