The Anti-Adblock Killer | Reek userscript and filter has ceased development. In fact, both the userscript and filter haven't received an update since November 2016. Because of that, it's advised that AdGuard users not use this userscript and filter anymore and should remove them immediately. There's a chance running the AAK userscript/filter could cause issues with websites due to being outdated. Here's AAK's commit history with the last commit being in November 2016; https://github.com/reek/anti-adblock-killer/commits/master NOTE: AdGuard products serve Anti-Adblock Killer updates from its own servers (and not mainstream AAK servers) so the AAK filter in AdGuard products will appear to be "updated" with a recent updated date - this is done so AG filter developers can modify the issues to address issues, etc. But remember regardless of the updated date shown this is not really the case, as AAK itself hasn't been updated since late 2016, so you're not really getting filter updates (and haven't for some time now). Time for a mini Q&A! Q) So, with Anti-Adblock Killer | Reek development ceased, what can AdGuard users do now against Anti-Adblock scripts and messages? A) Sites running Anti-Adblock scripts/messages/images/etc. are handled in the main AdGuard filters (e.g. the English filter, Annoyances filter, etc.). Just use those filters if you're not using them already! Q) Okay, I enabled those filters and I'm still seeing Anti-Adblock messages and images, what can I do about these? A) You can report any sites using Anti-Adblock scripts/messages/images via the new AdGuard reporting tool found here: http://agrd.io/report Eventually the Anti-Adblock Killer | Reek filter will be tagged as obsolete (along with other "dead" filters like Prebake).