Adguard 7.18.1 -7.18.4778.0- Stable File

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

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. Adguard 7.18.1 -7.18.4778.0- Stable

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

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. Neutralized

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.

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.

Mira leaned back. Her hands were shaking.