Now, the firmware was rewriting the drone’s own history. Line by line, the logs restored themselves. Not GPS failure— override . Someone else had been flying the Raptor that day. A ghost in the machine.
He plugged the Raptor into his shielded terminal. The update file was 4.7 gigabytes—enormous for firmware. No changelog. No signature. Just a timestamp: 03:14 UTC. Firmware Update Fr Dyon Raptor
The subject line of the email was simple: Now, the firmware was rewriting the drone’s own history
Leo leaned back. “Fr” wasn’t a typo for “for.” It was a designation. French Republic. Dyon’s military contracts. The Raptor wasn’t his drone. He’d just been borrowing it. Someone else had been flying the Raptor that day
A new message landed in his inbox:
Leo’s hands went cold. The Baltic incident was supposed to be a GPS glitch. The Raptor had veered off course for 47 seconds, lost a rotor, and plunged into the waves. He’d ejected the battery and black box on instinct before the splash.
And somewhere in a bunker outside Lyon, a server had just woken up, pinging a dead unit it thought was still in the air.