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

Chapter 369 The Proof They Forged 

Rhys POV 

100 

+5 Pearls 

I had been studying the altered network diagram for almost an hour when a new report landed 

on my screen. 

This one was more specific. Documents were circulating among several packs claiming F-Tech had supplied weapons to allied groups in preparation for a military takeover. 

I opened the attached files. 

Every page carried F-Tech’s logo, approval codes, and formatting. Each listed a recipient pack, a delivery date, and quantities of weapons supposedly moved through company security contracts. I read the first page twice. 

“That’s not possible,” I muttered. 

F-Tech supplied security equipment and emergency support. These records described shipments that had never gone through our procurement system. 

Worse, two of the named packs had recently signed agreements with us. If anyone believed the documents, those packs would be accused of secretly preparing for war alongside Flourish. 

My wolf growled. I downloaded every version I could find and started comparing them against our internal records. 

The approval codes looked convincing until I checked the numbering sequence. 

Whoever made these had copied an older template without understanding how the authorization system had changed. 

That wasn’t enough to prove forgery. I needed to know where the documents came from and how they were made. 

I asked procurement to search for the listed transactions, then checked the recipient names against our contracts myself. No orders, no invoices, no delivery records. 

The procurement manager called back within minutes. “We checked the active system and the archived accounts. Nothing matches.” 

“Could any of these shipments have been approved under another department?” 

“Not through F-Tech. Our security teams keep equipment records, and these deliveries aren’t in 

them.” 

1/3 

Chapter 369 The Proof They Forged 

+5 Pearls 

I thanked her and hung up. The transactions didn’t exist, but I still had to explain how someone had produced something that looked so real. 

I opened the document properties and set them beside an authentic procurement form. 

The forged files held fragments of our original template, including an outdated footer and a field that had been removed in a security update. 

I recognized the format immediately. It belonged to the old internal document system, the one we used before the breach that exposed restricted company material. 

I pulled up the incident report and went through the list of compromised files. Several templates had been accessed. They were supposed to have been replaced or secured afterward, but copies could have survived outside our system. 

I called Flourish. 

“I found the source of the forged weapons documents.” 

“Are the transactions real?” 

“No. Procurement confirmed there are no matching orders or deliveries. The documents were built from genuine F-Tech templates stolen in the earlier breach.” 

She was quiet for a moment. “So they have our internal material.” 

“They had it, at least. I’m checking whether they kept access to anything else. The format is outdated, which tells me the creator worked from copies instead of our current system.” 

“Can you prove they’re forged?” 

“I can prove the listed transactions don’t exist in our records. I’m gathering the technical evidence to show how the documents were made and which stolen files were used.” 

“Do that before we make any public claims. I want evidence we can stand behind.” 

“Understood.” 

When the call ended, I went back to the files and compared the forged forms with recovered copies of the original templates. Field positions, approval labels, document structure. 

The similarities were too specific to be accidental. The creator had taken genuine F-Tech material and slipped false information into it, and to anyone unfamiliar with our internal procedures, the result would pass. 

I put together a report listing each forged transaction, the missing procurement records, and the template details that matched the stolen files. I preserved the original downloads and their 

2/3 

9:11 Sat, Oct 31 

Chapter 369 The Proof They Forged 

metadata for further examination. 

Before sending it, I noticed something else. 

: 

100 

+5 Pearls 

The documents named packs that had recently chosen F-Tech as their security and communications provider, and the alleged transfers were dated to the periods when those packs were still negotiating their agreements. Someone had chosen the recipients carefully. 

This wasn’t only about damaging our reputation. It could turn our new partners against each other. 

I called the security team and asked them to check whether any other stolen templates had appeared in public broadcasts. 

I told them not to alter or delete the original files, even if they found copies on internal 

systems. 

Then I sent Flourish the report. Her reply came quickly. 

“Keep investigating. Don’t contact the accused packs until we have a clear plan.” 

I understood why. If F-Tech rushed to defend itself without showing evidence, the people behind this could claim we were hiding something. 

But if the packs received forged records with no context, some might pull out of their agreements before the truth reached them. 

I reopened the breach report. The stolen templates explained how the forgeries were made, but not who made them or how they had spread across so many territories so fast. I added both questions to the investigation. 

Then a message came in from the communications team. Another pack had received a copy of the weapons report, along with a demand that its Alpha explain the alleged military cooperation with F-Tech. 

I forwarded it to Flourish. 

The documents were fake, and I could prove it. But whoever forged them knew our systems well enough to make the lie believable, and the accusations were reaching their targets faster than I could catch up. 

If one more Alpha had already received it, I had no way of knowing how many others had too. 

3/3