A new message landed in his inbox:
Leo smiled grimly. “Firmware update,” he muttered. “Right.”
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.
But the sender’s address made him pause: no-reply@dyon.aero . The real Dyon aero-space domain. Not a scam.
The final line of the update blinked onto his screen:
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.
A hidden partition appeared on the drone’s storage:
And somewhere in a bunker outside Lyon, a server had just woken up, pinging a dead unit it thought was still in the air.
The Raptor’s rotors spun up on their own.
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.
The subject line of the email was simple:
He ran it through a sandbox first. The code didn’t install. It unlocked .
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:
Leo smiled grimly. “Firmware update,” he muttered. “Right.”
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
But the sender’s address made him pause: no-reply@dyon.aero . The real Dyon aero-space domain. Not a scam.
The final line of the update blinked onto his screen:
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. A new message landed in his inbox: Leo smiled grimly
A hidden partition appeared on the drone’s storage:
And somewhere in a bunker outside Lyon, a server had just woken up, pinging a dead unit it thought was still in the air.
The Raptor’s rotors spun up on their own. Line by line, the logs restored themselves
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.
The subject line of the email was simple:
He ran it through a sandbox first. The code didn’t install. It unlocked .
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.