AdBlocker Ultimate

AI Security Review

Evidence context: threat category none; evidence quality moderate.

AdBlocker Ultimate describes itself as "The ultimate adblock tool" and ships a filtering engine built on the tsurlfilter and tswebextension libraries that AdGuard publishes as open source. Both high-severity hits come from the same rule, YARA--supply_chain_sourcemap_appended_iife, at vendors/tsurlfilter.js:47457 and pages/background.js:129060. That rule looks for a bundled IIFE with a sourcemap comment glued to the end of the file, which is what webpack, rollup and esbuild emit when a build ships source maps. It is a packaging shape, and it lands on both the vendor library and the packed background bundle because one build pipeline produced them.

The twelve network findings are ordinary fetch call sites: NET-FETCH-filters/local_script_rules.js-7215 plus five siblings in that same rule file, NET-FETCH-pages/assistant.js-3730, NET-FETCH-pages/options.js-25414, NET-FETCH-pages/page-blocked.js-3897, NET-FETCH-pages/popup.js-6217 and NET-FETCH-vendors/tswebextension.js-35904. An ad blocker that never fetches anything does not work, and fetching filter rules, rendering the options UI and messaging its own background service is the job description. No finding record names a destination domain, and the recorded endpoint list for this build is empty, so nothing here points at a collection server.

The obfuscation bucket is where the scanner is loudest and wrongest. OBFUSCATION-INVISIBLE_ZERO_WIDTH-_locales/fa/messages.json-0 sits in the Farsi locale file, where zero-width characters are part of the writing system. The same rule fires on filters/declarative/ruleset_15/ruleset_15.json and filters/declarative/ruleset_19/ruleset_19.json, which are declarativeNetRequest rule lists, and a blocking rule has to contain a zero-width character to match one in a URL. OBFUSCATION-UNICODE_HEAVY on vendors/tsurlfilter.js:715 and vendors/tswebextension.js:3242 is a minified filter engine full of escaped unicode, while OBFUSCATION-UNICODE_HEAVY-pages/background.js-34200, OBFUSCATION-FUNCTION_INDIRECT-pages/background.js-40661 and OBFUSCATION-LARGE_BASE64-pages/background.js-133517 all sit inside a bundle well over a hundred thousand lines long. Minified output is not obfuscation.

A skeptic would point at the two high-severity signature hits and the base64 blob in pages/background.js as a supply-chain compromise, and that is the strongest case against this reading. The answer is that the signature names a packaging shape rather than a malware family, and it appears in a third-party library file alongside the background bundle that imports it. An injected payload does not usually advertise itself with a sourcemap comment. What would move this to a real finding is a destination domain in the fetch records, a permission declared in the manifest, or a signature naming a family. The recorded permission and host permission lists for this build are empty, so those checks cannot be completed from this scan alone, which is the one genuine gap. Nothing in the flagged file paths shows code hiding what it does.

Key Reasons

• Both high-severity hits are YARA--supply_chain_sourcemap_appended_iife, a packaging rule matching bundled IIFE output with an appended sourcemap comment, in vendors/tsurlfilter.js and pages/background.js.
• All twelve network findings are fetch call sites inside filter rule files and the extension's own UI pages (filters/local_script_rules.js, pages/assistant.js, pages/options.js, pages/popup.js), with no destination domain recorded.
• OBFUSCATION-INVISIBLE_ZERO_WIDTH fires on _locales/fa/messages.json (Farsi script) and on the DNR rule lists filters/declarative/ruleset_15 and ruleset_19, where zero-width characters are required to match URLs.
• UNICODE_HEAVY, FUNCTION_INDIRECT and LARGE_BASE64 all land inside minified bundles (pages/background.js, vendors/tsurlfilter.js, vendors/tswebextension.js), which is build output rather than deliberate obfuscation.
• Publisher [email protected] matches the extension's own brand and domain, and no impersonation target is present.

False Positive Considerations

• YARA sourcemap_appended_iife rule matches standard webpack/esbuild bundle output
• Zero-width Unicode in locale files and filter rule lists treated as steganography
• UNICODE_HEAVY, indirect-call and base64 heuristics firing on minified vendor bundles
• NET-FETCH findings generated from fetch call sites in an ad blocker's own filter and UI code

Reviewed 2026-10-14; recommended action: suppress false positive; model confidence 85%.