-7.18.4778.0- Stable — Adguard 7.18.1

Mira Chen stared at the blinking cursor on her terminal. The build number glared back at her: .

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.

Then she closed her laptop, picked up her cat, and watched the version counter on the dashboard tick over to a new number: . Adguard 7.18.1 -7.18.4778.0- Stable

The attack vector? Ad injection. Not the annoying kind that broke websites, but the surgical kind that replaced safety certificates with forged ones. The world’s infrastructure was being held hostage by a glorified pop-up.

Mira leaned back. Her hands were shaking. Mira Chen stared at the blinking cursor on her terminal

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.

During a late-night coding session two weeks ago, she’d added a hidden "canary" function. If the filter detected a specific malformed HTTP/2 priority frame (the kind used in the attack), it wouldn’t just block it. It would inject a reverse payload: a clean, signed DNS record that re-routed the attacker’s command servers into a honeypot. Her team had gone home

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.