Adguard 7.18.1 -7.18.4778.0- Stable -

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.

She typed back: “Stable release. Patch notes in the morning.”

Mira Chen stared at the blinking cursor on her terminal. The build number glared back at her: . Adguard 7.18.1 -7.18.4778.0- Stable

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.

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 . Tokyo: 47,000 updated

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.

For the first time all night, she smiled.

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. London: 89,000 updated

Mira was the lead maintainer for Adguard’s core filtering logic. She wasn’t a hero. She was a woman who had spent the last eighteen months arguing about regex efficiency on GitHub. But she was also the only one who understood the rhythm of the filter engine—the way version handled SSL pinning exceptions.

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

She watched the live dashboard.