AdGuard Browser Assistant

AI Security Review

Evidence context: threat category none; evidence quality strong.

AdGuard Browser Assistant is published by Adguard Software Ltd, the company behind the AdGuard desktop ad blocker, and version 1.4.27 is the Firefox companion that lets the desktop app toggle filtering from the toolbar. The manifest declares no host permissions and no other permissions, and the bundle lists no network endpoints, so this extension has no destination of its own to send data to. It drives the desktop app over the native messaging channel you already installed.

The findings that produced the score come from three sources, and none of them describe behavior. content-scripts.js:10529 matches YARA--supply_chain_sourcemap_appended_iife. That rule targets a sourcemap comment appended to a bundled IIFE, which is what webpack and esbuild emit when source maps are left on in a production build. A sourcemap is a lookup table that maps minified code back to original source; it is a build setting, not a payload.

popup.js:13406 and popup.js:13409 trigger OBFUSCATION-UNICODE_HEAVY and OBFUSCATION-HEX_STRING_HEAVY. Both patterns come from minified JavaScript, where short identifiers and packed string tables create dense runs of escape sequences and high-byte characters. The file is the popup's bundled UI code. Minification is not obfuscation, it is the default output of a bundler.

_locales/fa/messages.json:0:0 triggers OBFUSCATION-INVISIBLE_ZERO_WIDTH. That file holds Persian translation strings. Persian uses the zero-width non-joiner (U+200C) as ordinary orthography, to stop letters joining where they should not. The same finding fires across extensions that ship Farsi, Sinhala, Kannada or Khmer locale files, and it belongs to a known false-positive class.

The strongest counterargument is the single high-severity malware-signature hit. A skeptic would say a supply-chain YARA match is precisely what a compromised build looks like. The rule name tells you what it actually matches: an appended sourcemap on an IIFE bundle, the shape of an ordinary build artifact, sitting on the vendor's own content script next to the popup bundle and locale files of a product with a public repository and a named company behind it. A loader stub in an unrelated file, or the same match co-located with an unknown endpoint, would read differently. Here there is no IoC, no host permission and no exfiltration path in the bundle.

What would change this assessment is runtime evidence: a network finding to a domain outside AdGuard's own infrastructure, or a permission request that exceeds what a desktop-app companion needs. Neither is present. The findings map cleanly onto bundler output and locale encoding, and a named publisher owns the code that carries them.

Key Reasons

• Publisher is Adguard Software Ltd, the named vendor behind the AdGuard desktop product this extension controls
• YARA--supply_chain_sourcemap_appended_iife on content-scripts.js:10529 matches a sourcemap comment on a bundled IIFE, a standard build artifact
• OBFUSCATION-UNICODE_HEAVY and OBFUSCATION-HEX_STRING_HEAVY on popup.js:13406 and popup.js:13409 reflect minified bundle output, not deliberate obfuscation
• OBFUSCATION-INVISIBLE_ZERO_WIDTH on _locales/fa/messages.json:0:0 fires on the Persian zero-width non-joiner, a documented i18n false positive
• No IoCs, no network endpoints, no permissions and no host permissions in the bundle, leaving no exfiltration path

False Positive Considerations

• OBFUSCATION-INVISIBLE_ZERO_WIDTH in _locales/fa/messages.json fires on Persian zero-width non-joiner characters (U+200C)
• OBFUSCATION-UNICODE_HEAVY and OBFUSCATION-HEX_STRING_HEAVY in popup.js reflect minified bundler output
• YARA--supply_chain_sourcemap_appended_iife matches an appended sourcemap on an IIFE bundle, a normal build setting
• Zero IoCs, zero network endpoints and zero declared permissions, so no data flow to evaluate

Reviewed 2026-10-11; recommended action: suppress false positive; model confidence 90%.