Page 5 of Code Name: Tank
The black SUVthat had been waiting for us on the tarmac pulled up to Titan Defense’s El Segundo facility at fourteen hundred hours. The afternoon sun reflected off the glass-and-steel structure that housed some of America’s most critical weapons manufacturing. As we parked, I took note of the security cameras, access points, and potential vulnerabilities.
“Impressive setup,” Tank observed, studying the building. “Looks like they take physical security seriously.”
“Physical security is only as strong as financial security,” I replied, noting how the observation platforms and restricted parking indicated typical government-contractor protocols. “If someone’s compromised their funding, no number of guards or cameras will matter.”
We approached the main entrance, where a security checkpoint required appropriate ID and escort clearance. The guard examined our credentials, then handed them back to us.
“You’re both expected. Dr. David Lopez, our director of operations, will meet you inside.”
The main lobby spoke of serious government contracting—polished but functional, with subtle displays showcasing the company’s defense capabilities without revealing classified details. Dr. Lopez—a man in his forties with the expression of someone managing a crisis beyond his experience—emerged from an elevator bank.
“Thank you both for coming on such short notice.” He shook hands with both of us. “Our production delays have reached critical levels, and we’re facing significant contract penalties if we can’t resolve this quickly.”
“Dr. Lopez, before we begin, can you walk us through exactly what happened?” Tank asked as we returned to the elevator and rode up to the third floor.
“Our CFO discovered the irregularities during a routine quarterly review,” said Dr. Lopez, pulling up account statements. “The authorizations looked legitimate, but we never initiated these transfers.”
I began examining the transaction records. The sequence struck me as odd—small amounts, each one under fifty thousand dollars, occurring every few days during normal business hours. Most theft attempts I’d seen happened at night or on weekends, when fewer people were monitoring the systems.
“These are interesting,” I said to Tank. “Not large enough to trigger immediate attention, but they add up quickly over time.”
Tank studied the information over my shoulder. “Methodical.”
“Very. And look at the timing—they knew precisely when to stop. The last transfer happened three days before your quarterly review.”
Dr. Lopez frowned. “How could they know our reporting schedule?”
“That’s what we need to find out,” I replied. “Can we speak with your CFO and whoever handles authorization protocols?”
“Of course. I’ll have them come up immediately.”
Over the next two hours, we interviewed the CFO, the head of accounting, and the compliance officer. Each conversation revealed the same troubling theme—the unauthorized transfers were executed with sophisticated timing. They knew which accounts held the largest contract funds, how much they could take without triggering immediate alerts, and when to stop before quarterly reviews.
But what bothered me most was something the CFO mentioned.
“The timing of these transfers is what’s really unusual,” the CFO said, pulling up additional records. “Look at this pattern—they happen in clusters, always during our busiest processing periods when staff are less likely to notice individual transactions.”
“You’re saying they knew your internal schedules?” I asked.
“More than that,” the CFO replied, scrolling through the data. “They knew exactly which accounts had the highest balances on specific days. That’s information we don’t even share with our primary banking partners.”
After we left the meeting, Tank voiced what we were both thinking. “This isn’t just about compromised authorization codes anymore.”
“No,” I agreed. “Someone’s been watching Titan from the inside for months.”
By sixteen thirty, we’d gathered what we could from the available personnel. Most of the accounting staff had left for the day, and Dr. Lopez was clearly eager to wrap up.
“Did you get everything you needed today?” Tank asked as we walked back to the SUV.
“Enough to get started,” I replied. “At this point, I don’t see any reason why we’d need to stay another day.”
“It’s late. I’ll arrange for lodging, and we’ll head back in the morning,” he said, starting the vehicle.
“Good idea. There’s a Grandview Inn about ten minutes from here.”
During the drive to the hotel, Tank was quiet for several minutes before asking, “What’s bothering you about this?”
I stared out the passenger window, trying to organize my thoughts. “The coordination is too perfect. Whoever did this didn’t just steal money—they understood Titan’s contract payment schedules and account structures. That suggestssomeone with access to high-level information about defense-contractor funding cycles.”
