Chapter 3: A Whispered Confession

Acting on Mr. Elias’s subtle lead, I spent the next few days in a relentless pursuit of internal system logs, pouring over digital footprints that seemed designed to be obscure. The festival’s online booking system, built by a small local firm, had surprisingly robust logging capabilities for internal administrative actions, a detail I had overlooked in my initial panic. I wasn’t an IT expert, but I was intelligent, determined, and had a clear directive: find a “signature.”

The technical jargon was overwhelming, but certain patterns began to emerge. There were indeed anomalies in the access logs, not just on the launch day, but weeks prior. Entries showing high-level administrative access outside of standard operating hours, followed by subtle modifications to core database schemas related to vendor registration and payment processing. These weren’t random glitches. These were deliberate changes.

My heart hammered against my ribs as I saw them. Specific timestamps, specific user IDs. One ID, in particular, kept appearing: `DChen_Admin`. Daniel Chen’s ID. Daniel, our earnest, unassuming IT specialist. It couldn’t be. Daniel was the last person I would suspect. He was meticulous, almost painfully so, about technical integrity.

I wrestled with the information for another day, cross-referencing everything I could. The changes were precise. The kind of precision that would require not just access, but a deep understanding of the system’s architecture and an intent to cause very specific damage. It wasn’t just deleting data. It was corrupting the underlying structure in a way that *looked* like a malfunction, but was actually a deliberate, layered attack.

Finally, unable to bear the weight of suspicion alone, I called Daniel. We met at a quiet coffee shop, far from the committee’s prying eyes. He arrived looking tired, his usual neat hair slightly disheveled.

“Daniel, thank you for meeting me,” I began, trying to keep my voice neutral.

He nodded, stirring his coffee nervously. “Of course, Sarah. Anything for the festival. Have you found anything?”

“I think so,” I said, placing a printed summary of the anomalous log entries on the table between us. I highlighted the `DChen_Admin` entries. “These are from weeks ago. Early mornings, late nights. They show high-level access, followed by changes to the vendor database structure.”

Daniel picked up the paper, his eyes scanning the lines. As he read, his face drained of color. He looked like he’d seen a ghost. His hand started to tremble, rattling the ceramic mug on the table.

“I… I don’t understand,” he stammered, his gaze darting around the coffee shop, as if expecting someone to overhear. “This isn’t possible. I didn’t make these changes. I would never.”

“I know you wouldn’t, Daniel,” I said, my voice softening. I believed him. His distress was too genuine. “But these logs show your administrative ID. The kind of access that can alter the very fabric of the system.”

He swallowed hard, running a hand through his hair. “It’s impossible. I only use my admin credentials for official updates, and I always log them. These aren’t mine.”

“Is there any way someone else could have used your credentials?” I asked, watching him closely. “Did you ever share your master password?”

He froze. His eyes widened, and a deep flush crept up his neck, staining his pale cheeks. He pushed his coffee cup away, shaking his head.

“No,” he mumbled, then hesitated. “Well, not… not intentionally.”

My stomach tightened. “Daniel, what happened?”

He finally looked at me, his eyes filled with a mix of shame and fear. He took a deep breath, and the words tumbled out, barely a whisper.

“A few months ago, when Mark Peterson joined the committee,” Daniel confessed, his voice barely audible, “he offered to conduct a ‘comprehensive security audit’ of the entire festival system. He said he wanted to ensure everything was locked down, especially with all the financial data we’d be handling.”

I remembered that. Mark had been very vocal about his “cybersecurity expertise” during an early committee meeting, though I’d always found it a bit odd for a real estate agent. He’d portrayed it as a civic duty, a way to leverage his “skills” for the community.

“He presented himself as being so helpful, so proactive,” Daniel continued, his voice laced with self-reproach. “He talked about potential vulnerabilities, data breaches, and how important it was to have someone with his background double-check everything.”

“And you believed him?” I asked, trying to keep the frustration out of my voice.

“He was so convincing, Sarah,” Daniel pleaded, his hands clasped tightly on the table. “He had all the right buzzwords, talked about risk assessments and penetration testing. He made it sound like he was doing us a huge favor, saving us from a potential disaster.”

“So, you gave him your master password?”

Daniel nodded miserably. “He said he needed full, unrestricted backend access to perform a thorough audit. He explained that a limited account wouldn’t reveal deeper vulnerabilities. He even said he’d create a temporary audit account for himself, but that my master password was essential to grant that level of privilege.”

“Did he ever give you a report from this ‘audit’?”

“He said he’d deliver it confidentially to you, as chairwoman,” Daniel admitted, looking away. “But… I never saw it.”

My blood ran cold. Mark Peterson. My charming, helpful neighbor. The man who sat across from me in committee meetings, offering solutions, deflecting blame. He had access. He had *my* IT specialist’s master password.

“He assured me it was a standard procedure for this kind of review,” Daniel added, his voice cracking. “I trusted him. He’s a respected member of the community. He said he’d be discreet, that he’d wipe any temporary accounts after his audit was complete.”

“Did you ever change your password after that?” I asked, though I already knew the answer from the logs.

He shook his head, a fresh wave of shame washing over him. “No. He said it was an ongoing process, that he might need to revisit things. I just… I left it as it was.”

The pieces clicked into place with a sickening thud. The high-level access. The targeted corruption. Mark Peterson’s calm assurance at the meeting, his quickness to blame external factors, his subtle push for damage control over investigation. It all made a terrifying kind of sense. He had gained the keys to the kingdom months ago, under the guise of helping.

“Daniel,” I said, trying to keep my voice steady, “this is serious. This means someone used your password to deliberately corrupt the system.”

“But why?” Daniel cried, tears welling in his eyes. “Why would Mark do something like that? He loves the festival! He’s always so involved.”

That was the question. The biggest, most disturbing question of all. Mark Peterson, the pillar of the community, the smooth-talking real estate agent, the man who always had a smile and a handshake. Why would he sabotage the very event he claimed to support?

“I don’t know, Daniel,” I admitted, rubbing my temples. “But we’re going to find out. I need you to confirm that you didn’t make these changes. Can you sign something to that effect?”

He nodded vehemently. “Yes! Anything. I swear on my professional reputation, I had nothing to do with this.”

“Okay,” I said, my mind already racing ahead. “For now, don’t tell anyone about this. Not the other committee members. Not your friends. Not anyone. We need to handle this very carefully.”

Daniel looked relieved, but also terrified. “You’re going to confront him, aren’t you?”

“I have to,” I replied, gathering the log printouts. “But I need to be smart about it. He’s clearly manipulative. If he’s capable of this, he’s capable of anything.”

Walking out of the coffee shop, the world seemed to have shifted on its axis. The air felt colder, the smiles of strangers less genuine. Mark Peterson. The betrayal was staggering. It wasn’t just the festival. It was the trust of the entire community. And the fact that he had weaponized Daniel’s eagerness to help, his innocent trust, made my blood boil.

I thought about Lily, about her innocent belief in the good in people, her openness. This kind of calculated deceit was exactly what I wanted to shield her from. But to do that, I had to face it head-on.

The internal investigation Mr. Elias had pointed me towards had borne fruit, but the fruit was bitter. It wasn’t a nameless hacker or a faulty server. It was a neighbor. A man who had looked me in the eye and offered his “help.” The realization brought a new wave of fear, but also a hardening resolve. I wouldn’t let him get away with it. Not after everything. Not after he had used Daniel, used the festival, used our community’s trust.

The next step was clear, though daunting: I had to confront Mark Peterson. But I knew this wouldn’t be a simple conversation. I was walking into a snake pit, and I needed to be prepared. My reputation might be fragile, but my resolve to protect my community, and ultimately, Lily, was ironclad.