Adguard 7.18.1 -7.18.4778.0- Stable May 2026

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

Now, with her cat watching from atop the server rack, Mira executed a force-update push to all Adguard users still on 7.18.0. Within sixty seconds, 200 million clients began pulling .

Mira leaned back. Her hands were shaking. Adguard 7.18.1 -7.18.4778.0- Stable

She hadn't told anyone. Not her PM, not legal. It was technically a violation of five different compliance rules. But she’d labeled it as "experimental telemetry" in the commit.

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 attacker had exploited a flaw in the previous build, 7

For the first time all night, she smiled.

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. Now, with her cat watching from atop the

Mira pulled up the changelog one more time: Fixed: rare race condition in TLS handshake emulation (issue #4778). Improved: stealth mode pattern matching for CNAME cloaking. Updated: CoreLibs to 7.18.4778.0 – Stable. That innocuous little number——was her secret weapon.