He reached for his soldering iron. Not to fix the drone—to kill its transmitter. But the firmware had already finished.
He ran it through a sandbox first. The code didn’t install. It unlocked .
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.
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 smiled grimly. “Firmware update,” he muttered. “Right.”
The Raptor’s rotors spun up on their own.
The final line of the update blinked onto his screen: He reached for his soldering iron
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.
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.
The subject line of the email was simple: He ran it through a sandbox first
A new message landed in his inbox:
But the black box had never been found.
But the sender’s address made him pause: no-reply@dyon.aero . The real Dyon aero-space domain. Not a scam.
And somewhere in a bunker outside Lyon, a server had just woken up, pinging a dead unit it thought was still in the air.