Air-ap2800-k9-me-8-5-182-0.tar -

She ran a packet capture. The source MAC address was correct for the AP. But the destination... it was multicasting to a range she’d never seen: ff-ff-ff-ff-ff-ff . Every packet carried a single payload: a binary translation of the TAR file’s own header.

She looked at the log one more time. The epoch login. The self-replicating packets.

“That’s impossible,” she whispered. The epoch. Someone—or something—had logged in from localhost before time itself began. Air-ap2800-k9-me-8-5-182-0.tar

The lights on the access point above her flickered. Then, the office went quiet. No, not quiet. Wrong. The normal 2.4 GHz hum of wireless traffic disappeared. Even the wired switch next to her gave a sharp clunk as its ports cycled.

It was trying to clone itself.

Last login: Thu Jan 1 00:00:01 1970 from 127.0.0.1

Her fingers flew across the keyboard. show version . The firmware read 8.5.182.0. But the serial number was all zeros. The uptime? Negative forty-seven thousand seconds. She ran a packet capture

She SSH’d into the primary controller AP. The prompt blinked back: AP2800# . She ran the archive download command and watched the percentage climb. 12%... 47%... 89%. When it hit 100%, she initiated the reboot.

“Why not?”

Then the wireless network on her laptop vanished. No SSIDs. No client associations. Just raw, screaming RF noise flooding the spectrum. She pulled up a spectrum analyzer on her tablet. The AP2800 wasn't broadcasting data—it was broadcasting patterns . Sine waves. Morse code. A heartbeat.