Adguard 7.18.1 -7.18.4778.0- Stable ⇒

The attacker had exploited a flaw in the previous build, 7.18.0. They assumed the patch would take days. They were wrong.

The attack didn’t stop. It reversed . The same injection channels that had spread the exploit now carried Mira’s fix. The attacker’s own infrastructure was flooded with clean routing tables. Adguard 7.18.1 -7.18.4778.0- Stable

At 12:03 AM, the hospital in Chicago went silent—then rebooted, clean. The container ship’s GPS recalibrated. The traffic lights in Seoul began their gentle, synchronized dance again. The attacker had exploited a flaw in the previous build, 7

Tokyo: 47,000 updated. Attack signature detected. Neutralized. London: 89,000 updated. Reverse payload deployed. Honeypot active. New York: 112,000 updated. CNAME cloaking bypassed. The attack didn’t stop

It was 11:47 PM on a Friday. Her team had gone home. The "Stable" tag was supposed to be a celebration—a final, polished release of Adguard’s core filtering engine. Instead, it felt like a death sentence.

Three hours ago, a silent, weaponized zero-day exploit had begun propagating. It didn’t look like a virus. It looked like a harmless analytics packet. But once it slipped past standard firewalls, it rewrote DNS routing tables on a hardware level. In Seoul, traffic lights flickered. In Rotterdam, a container ship’s navigation system froze. In Chicago, a hospital’s internal paging system started screaming static.

Her phone buzzed. A text from her boss: “What the hell did you just push? The board is panicking. They’re calling it a miracle.”