Firmware — Update Fr Dyon Raptor

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.

A new message landed in his inbox:

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. Firmware Update Fr Dyon Raptor

Leo, a former drone mechanic for a civilian surveillance firm, almost deleted it. He hadn’t flown his old Dyon Raptor in three years—not since the accident over the Baltic. The unit was supposed to be a paperweight, its memory core wiped by company lawyers. Leo leaned back

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. Dyon’s military contracts

He reached for his soldering iron. Not to fix the drone—to kill its transmitter. But the firmware had already finished.