Ch. I Refuse to Be Your Luna 328 I Refuse to Be Your Luna 328

Chapter 328 F-tech Goes Dark 

Aha Damian POV 

The more Rhys examined the archive breach, the less I liked what he found. 

36 

Finished 

The intruder had asked questions about maintenance schedules, staff routines, and overnight security before entering the restricted archive. 

Daniel had remembered the stranger’s questions, but he had not recognized him, and the scent left behind was too heavily masked to identify a pack. 

Someone had studied F-Tech before making a move. 

I stood beside the main security console while Rhys explained the risk to Flourish and Cheryl. 

“Our internal systems are contained,” he said. “The problem is the communication links between F-Tech and the packs we serve. If the intruder used a compromised device to reach our archive, we can’t assume those connections are safe.” 

“How many systems are exposed?” Flourish asked. 

“Potentially several. We haven’t found evidence of another breach, but some of the connections share authentication routes.” 

I looked at the network map. Stonehedge appeared among the active connections, along with Dartwood and several smaller packs. 

Other links supported emergency transport, medical coordination, security alerts, and encrypted messages between allied territories. 

The bloodline network used some of the same infrastructure, although its protected channels were 

separate. 

“How long to verify every connection?” I asked. 

Rhys rubbed his forehead. “If we keep everything running, several hours at best. Longer if the attacker left anything behind.” 

“And if we disconnect?” 

“F-Tech loses access to several pack communication systems immediately. Some clients will lose live monitoring. Emergency messages will need alternative routes, and we may not know which links are safe ‘until the checks are complete.” 

Flourish studied the map. 

“How many packs would be affected?” 

“Enough to cause problems,” Cheryl answered. “We have security contracts with several territories, and some use our channels for urgent alerts. Their local systems would still work, but they wouldn’t have the same connection to us.” 

10:15 Mon, Oct 12 

Chapter 328 F-tech Goes Dark 

Finished 

I knew what that meant. A pack could still call its own warriors, patrol its borders, and contact neighboring territories through ordinary means. 

But if an unfamiliar wolf crossed a protected boundary, the alert might not reach F-Tech or another allied pack in time. 

The network was useful because it connected people who could not always see danger coming. 

It was also a possible route into everything we were trying to protect. 

“Disconnect the affected links,” I ordered. 

Flourish turned toward me. 

“Damian, we haven’t confirmed that those connections were compromised.” 

“We haven’t confirmed that they’re safe either.” 

“If we shut down too much, we could leave clients without support.” 

“And if we leave a compromised connection open, we could expose every pack attached to it.” 

Her mouth tightened. 

I understood why she objected: F-Tech was her company, and she had spent years building the trust that kept clients from looking elsewhere. 

Cutting off services without warning could cost contracts and damage relationships that had taken years to 

establish. 

But the archive breach had changed the risk. 

“Rhys,” I said, “disconnect the shared authentication routes first. Keep the isolated internal systems running. Anything that cannot be verified stays offline.” 

He nodded and began issuing instructions. 

Within minutes, alerts appeared across the console. Several pack connections changed from active to restricted. The main communications board filled with warnings as the technical team shut down access points and began checking them one by one. 

Then the calls started. 

A security director from a northern territory demanded to know why his monitoring feed had stopped. 

A medical coordinator reported that an emergency transport request had failed to reach its intended recipient. 

Two allied packs wanted to know whether F-Tech had been attacked and whether their information was at 

risk. 

Cheryl answered what she could, refusing to speculate about the breach. 

I took a call from Dartwood. 

10:15 Mon, Oct 12 

Chapter 328 F-tech Goes Dark 

Ragnar appeared on the screen, his expression hard. 

“Our border alerts have stopped updating.” 

“Your local sensors should still be working.” 

“They are. But the reports aren’t reaching our central board.” 

Finished 

“Switch to the internal patrol channel. Have your teams report directly to the border station until F-Tech clears the connection.” 

Ragnar nodded. “How long?”. 

“I don’t know yet.” 

He didn’t like the answer, but he accepted the order. 

When the call ended, Flourish was speaking with a representative from another allied pack. 

She explained that F-Tech was isolating its systems because of a security threat and that local operations should continue through established backup procedures. 

She was calm with the representative, but when she ended the call, she turned on me. 

“You made that decision without discussing the scope with me.” 

“I made the security decision: 

“And I run F-Tech.” 

“I know that.” 

“Then stop treating my company like a Dartwood outpost.” 

Her voice carried across the room. Several employees looked up before returning to their work. 

I lowered mine. 

“This isn’t about ownership. It’s about preventing another breach.” 

“And it’s my responsibility to keep the company functioning while we investigate. You can’t protect the network by shutting down every route people depend on.” 

“I’m not shutting down every route.” 

“You’re shutting down enough to cause serious problems.” 

She pointed at the communication board. Three more connections had just gone offline. 

“Those packs trust us. Some of them came to F-Tech because they had nowhere else to turn. If we cut them off whenever we suspect a threat, what are we offering them?” 

I had no quick answer. 

36 

Chapter 328 F-tech Goes Dark 

Finished 

My wolf wanted the entire building sealed until every trace of the intruder had been found. It wanted Nourish away from the archive, away from the bloodline records, and away from anything that might put hein danger again. 

But I couldn’t let that instinct înake decisions for an entire network of packs. 

I looked at Rhys. 

“Can we separate the bloodline channels from the affected authentication routes?” 

“We’re checking now,” he said. “The protected channels have different safeguards, but I want to verify the gateways before I promise they’re safe.” 

Flourish moved beside him. 

“Show me the dependencies.” 

Rhys brought up a second map. She studied it, asking about backup relays, local servers, and the systems used for emergency medical requests. 

I watched her work. She wasn’t trying to prove me wrong anymore. She was looking for a way to keep the company useful without giving the intruder another opening. 

After several minutes, she tapped one section of the map. 

“These emergency services can use the independent relay system. We don’t need to reconnect the shared authentication routes to keep those messages moving.” 

Rhys checked the configuration. 

“She’s right. We can restore a limited service through the verified relays, but the full client connections need to remain restricted.” 

“Do it,” Flourish said. “Prioritize medical emergencies and direct security alerts. Everything else waits until the checks are complete.” 

I nodded. 

“That works.” 

She gave me a brief look, still unhappy with how the decision had started, but she returned to the console and helped Cheryl contact the affected clients. 

The technical team restored the limited services while the wider network remained disconnected. 

Calls continued to come in, and some pack leaders demanded faster answers. Others understood the risk and agreed to use local channels until F-Tech was ready. 

We had protected the company from further access through the suspected routes, but the cost was already 

clear. 

Allies were struggling to communicate, clients were questioning our reliability, and the bloodline network could not safely expand while the investigation remained open. 

4/5 

10:15 Mon, Oct 12 M 

Chapter 328 F-tech Goes Dark 

36 

Finished 

Flourish stood over the revised network map, checking each restored service herself. 

keep the emergency channels running,” she said. “We protect the bloodline network, but we don’t abandon the packs that depend on us.” 

I looked at the connections still marked offline. For now, we had no choice but to leave them that way. 

304 

W 

10:15 Mon, Oct 12 M 

I Refuse To Be Your Luna