Chapter 3 - The Login That Wasn’t Mine

The suspended-access notice felt like a verdict even though Caroline insisted it was only a precaution.
Without access to Bellamy’s accounting system, I could not perform my job. I returned to my desk under the eyes of the entire department, closed my laptop, and placed my employee badge beside it.
Elena approached cautiously.
“Are they sending you home?”
“Temporarily.”
“Did Brooke do this?”
“I don’t know.”
It was the only responsible answer, but uncertainty made me feel powerless.
Mason met me in the lobby. Caroline had already asked IT security to investigate, but because he was personally involved, he was prohibited from touching the case. That was appropriate. It was also frustrating.
“I can prove you were home,” he said as we walked toward the parking garage. “Our apartment building has entry logs. We ordered dinner. We watched a movie.”
“Being home doesn’t prove someone else used my account.”
“The company can trace the device.”
“What if they can’t?”
He stopped beside the car.
“Jenna, look at me.”
I did.
“You did not access that folder.”
“I know.”
“Then evidence exists. We just have to find it.”
Facts first.
I repeated the words silently, but fear kept adding questions.
What if my account had been used from my laptop? What if someone had planted files? What if Bellamy decided a junior employee was easier to dismiss than defend?
At home, I changed out of my work clothes but could not relax. I reviewed every moment of the previous week. On Friday afternoon, Brooke had borrowed my desk phone. On Monday, I had left my laptop locked while attending HR. Nothing explained how anyone could know my password.
Then I remembered the conference room.
During my first month, Brooke had taught me a keyboard shortcut for opening a reconciliation report. She had stood beside me while I logged in. I always shielded the keyboard, but perhaps not carefully enough.
The thought made me feel foolish.
Mason rejected it.
“Even if she saw your password once, Bellamy requires multifactor authentication.”
“The approval notification goes to my work phone.”
“Where was it last night?”
I looked toward my purse.
My company phone was inside.
I checked the notification history. At 11:47, there had been no authentication request.
Mason’s expression changed.
“That matters.”
“How?”
“If your account opened a restricted folder without triggering authentication, the event may not be a real login. Someone could have manipulated the log or used an active token copied from another device.”
I folded my arms. “Explain that in normal language.”
“It might have been made to look like you accessed the folder.”
The next morning, Bellamy assigned the investigation to Priya Nanduri, a cybersecurity specialist from an outside firm. She interviewed me by video call and asked precise questions about my devices, passwords, and work habits.
I told her everything, including my fear that Brooke may have seen me type my password.
Priya did not react.
“Did anyone ask you to open an attachment recently?”
I searched my memory.
“Brooke sent me a spreadsheet last Thursday. She said one of the formulas was broken.”
“Did you open it?”
“Yes.”
“Did it request that you enable macros or grant additional permissions?”
“No.”
“Do you still have the message?”
“It’s on my suspended account.”
“We’ll retrieve it.”
Hours passed.
At noon, Victor called.
“I want you to know we have not made any employment decision,” he said. “The investigation is active.”
“Do you believe I accessed the folder?”
“I believe the evidence is incomplete.”
It was a careful answer, but not a comforting one.
“Did Brooke make the accusation?”
“I can’t discuss another employee’s involvement.”
After the call, my mother phoned. I had not told her anything, but she heard the strain in my voice before I finished saying hello.
“What happened?”
I explained the complaint, the rumor, and the suspicious login.
She listened without interrupting.
When I finished, she said, “Do you remember what you told me after your twentieth job rejection?”
“No.”
“You said you didn’t need everyone to believe in you. You needed one employer willing to look at what you could do.”
“That employer may fire me.”
“Then make them look at the facts.”
My mother had never worked in an office. She managed a small bakery in Duluth and solved most crises with common sense and strong coffee. Her advice was simple because truth, to her, was not something to decorate.
That evening, Priya called.
“The login report attached to the anonymous email was altered,” she said.
Relief arrived so suddenly that I nearly laughed.
“So I’m cleared?”
“Not entirely. A genuine access event occurred, but the original user identification was replaced with yours in the exported report.”
“Whose account opened the folder?”
“We’re still determining that.”
She had found another important detail. The spreadsheet Brooke sent me contained a hidden link to a file stored on a shared department drive. Opening it had created a record of my system token, but there was no evidence the token had been successfully stolen.
“Could Brooke have manipulated the report?” I asked.
“Anyone with access to the exported file could have changed the displayed name. We need more evidence before attributing it.”
The following morning, Caroline restored my access and asked me to return.
When I entered accounting, Victor addressed the entire department.
“An allegation involving unauthorized system access was found to rely on an altered document,” he said. “The employee named in that allegation has been cleared of accessing restricted information. Speculation and gossip must stop immediately.”
He did not say my name.
He did not need to.
Elena smiled at me. Several coworkers looked ashamed. Brooke stared at her desk.
At ten-thirty, Caroline called Brooke into HR.
She did not return before lunch.
I tried to focus on the backlog of work waiting for me, but something in the vendor ledger caught my attention. A freight payment I had flagged weeks earlier had reappeared under a slightly different vendor code. The amount was $18,460.
I compared the invoice numbers.
They were nearly identical.
Then I found another duplicate for $23,900.
Both had been approved during the hours when my account was supposedly accessing payroll data.
I brought the records to Victor.
He studied the screen.
“Who created these vendor codes?”
“The audit trail says I did.”
His face became still.
“I didn’t,” I said.
Before he could answer, Caroline appeared in the doorway with Priya beside her.
Priya placed a laptop on Victor’s desk and turned the screen toward us.
“We identified the account that genuinely accessed the restricted folder,” she said.
The username belonged to Brooke.
May you like
But the device used to alter the report and create the duplicate vendor codes did not.
It belonged to Victor Hale.