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

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.

She was the sole network engineer for a regional healthcare system, and tonight, she was tasked with upgrading the AP2800s on the fourth floor. The file sat on her encrypted laptop: air-ap2800-k9-me-8-5-182-0.tar . It was just a bundle—a TAR file containing the Mobility Express (ME) firmware for the ruggedized access points. Version 8.5.182.0. A bug fix release, the patch notes said. Stability improvements. 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 SSH’d into the primary controller AP

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. When it hit 100%, she initiated the reboot

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

It was trying to clone itself.

“We’re not pushing 8.5.182.0 tonight,” she said.