Tracked campaign: Troywell VPN

Our analysis confirmed the behaviour described in the threat library entry. Do not install it. Read the analysis and indicators →

Also reported by socket.dev

Chrome Web Store Verified

Webfilter

eec1a010-348b-576c-9298-2d206cb572c4 | v5.3
28/ 100
LOW risk
No change since v5.0
Threat verdict
Do not install

Confirmed member of a tracked malicious supply-chain campaign.

Analysis record

Analysed
Yesterday
Version
v5.3
Artifact
SHA256 C45…80D
Source
Findings (non-IoC)

Is Webfilter safe?

Webfilter describes itself as a tool for blocking unwanted domains and declares no special permissions or host permissions. Its endpoint list includes 000a.de and 000free.us, while XIOC-DOMAIN-01-casino.com shows the kind of domain string a web filter can place in a blocklist. The listed developer is [email protected].

The scanner also flagged XIOC-DOMAIN-d1dext3t9dk55e.cloudfront.net, XIOC-DOMAIN-fastline.club, and XIOC-DOMAIN-zerivox.xyz from extracted_from_files. If those strings were used for live requests, they would deserve attention, yet the finding titles only show that domain text was extracted. They do not show cookies, credentials, uploads, or browser changes.

The scan record for extracted_from_files contains no malware-signature, obfuscation, network, or tool-poisoning finding. The scanner treated a large domain list as many medium-severity IoCs, which fits Webfilter's stated job. The supplied data therefore supports a benign blocklist explanation, with no special permission or harmful behavior shown.

Evidence ledger

Ranked by severity · findings with a source location link to the code viewer

29 detail rows

YARA Rule Matches

10 rules
SeverityRuleHitsFilesMetadata
LOWcredential env files 2
rules/rules_ext_1.jsonrules/rules_ext_2.json
-
LOWpostinstall persistence mechanism 2
rules/rules_ext_1.jsonrules/rules_ext_2.json
-
LOWpostinstall crypto operations 3
_metadata/verified_contents.jsonrules/rules_ext_1.jsonrules/rules_ext_2.json
-
LOWpostinstall file manipulation 2
background.jsrules/rules_ext_2.json
-
LOWpostinstall registry modification 1
rules/rules_ext_2.json
-
LOWpostinstall obfuscation 4
rules/rules_ext_1.jsonrules/rules_ext_3.jsonblocked.html +1 more
-
LOWpostinstall network communication 6
rules/whitelist.jsonrules/rules_ext_1.jsonbackground.js +3 more
-
LOWpostinstall system command 4
rules/rules_ext_1.jsonrules/rules_ext_3.jsonblocked.html +1 more
-
LOWcredential steam data 2
rules/rules_ext_1.jsonrules/rules_ext_3.json
-
LOWpostinstall file download 3
rules/rules_ext_3.jsonrules/rules_ext_1.jsonrules/rules_ext_2.json
-

Publisher Evidence

Limited evidence

[email protected]

Publisher identity, store signals, distribution reach, and warning signals used for context. Treat this as supporting evidence, not a clean bill of health.

Chrome does not expose the same publisher verification data as IDE stores, so this score is deliberately conservative.

28
Noisy-finding weight
x1.00
Publisher domain
edu.harnosand.se
Observed
Store verification signal
Limited signal
Limited
Extension portfolio
1
Portfolio

13 evidence rows available.

Finding Categories

YARA Rules Matched

10 rules(29 hits)
credential env files postinstall persistence mechanism postinstall crypto operations postinstall file manipulation postinstall registry modification postinstall obfuscation postinstall network communication postinstall system command credential steam data postinstall file download

Requested Permissions

3 permissions
<all_urls>

Access and modify data on every website you visit

Dangerous
declarativeNetRequest
Low
storage
Low

AI Security Report

AI Security Review

Evidence context: threat category none; evidence quality moderate.

The extension is named Webfilter, and its description is “Statisk blockering av oönskade domäner och webbplatser.” That stated purpose matches the domain-heavy results tied to extracted_from_files, including XIOC-DOMAIN-000a.de, XIOC-DOMAIN-000free.us, and XIOC-DOMAIN-01-casino.com. A static web filter needs a list of domains to block, so domain matches alone fit the advertised function.

The strongest signal is the nature of the extracted domains. XIOC-DOMAIN-d1dext3t9dk55e.cloudfront.net, XIOC-DOMAIN-d3pu2nwk20c7jt.cloudfront.net, and XIOC-DOMAIN-sradg.eastus.cloudapp.azure.com identify common hosting platforms or cloud subdomains. XIOC-DOMAIN-dns.matthias-prost.com and XIOC-DOMAIN-dns.kamilszczepanski.com identify names that can occur in DNS or blocklists. These titles show that the extractor found domain strings in extracted_from_files; they do not show that the extension contacted those domains or sent user data to them.

Several entries are suitable blocklist material. XIOC-DOMAIN-fastline.club, XIOC-DOMAIN-zerivox.xyz, and XIOC-DOMAIN-tuxlervpn.com are specific domains that a web filter could intentionally classify as unwanted. XIOC-DOMAIN-ac6.de, XIOC-DOMAIN-scientificsense.org, and XIOC-DOMAIN-fr.fragoria.com provide the same kind of domain-list evidence. The finding titles contain no URL paths, request parameters, credential targets, cookie operations, or data-upload indicators.

The scan record for extracted_from_files reports no malware-signature, malware, obfuscation, network, dependency, secret, or tool-poisoning findings. That absence matters because the domain matches have no companion finding that ties them to credential theft, browser hijacking, proxyware, or a delivered payload. The 29 low-severity code-smell results are also insufficient to change that reading, since no code-smell title or file path identifies harmful behavior.

The extension declares no permissions and no host permissions. That limits the capability shown in the supplied metadata. The listed publisher, [email protected], also provides a concrete developer identity, while Webfilter makes a direct claim about domain blocking. Neither extracted_from_files nor any listed XIOC title shows impersonation of a known product.

The strongest counterargument is the presence of domains such as XIOC-DOMAIN-dns.matthias-prost.com, XIOC-DOMAIN-fastline.club, and XIOC-DOMAIN-zerivox.xyz. A domain list containing obscure or unwanted sites can look like a threat when every entry receives a medium-severity label. Those titles still describe extracted domain strings, and the scan record for extracted_from_files supplies no runtime connection or payload finding. The counterargument therefore supports checking the source list if behavior changes, while the current evidence supports a blocklist false positive.

The available evidence is limited to extracted indicators and metadata. extracted_from_files does not identify the source file or show the surrounding code, so it cannot prove how the list is used. Even with that limit, the advertised filtering purpose, empty permission sets, identifiable publisher, and absence of malware or obfuscation findings support treating the results as scanner noise rather than an unsafe extension.

Key Reasons

  • Webfilter describes static blocking of unwanted domains, matching the domain strings extracted from extracted_from_files.
  • XIOC-DOMAIN-000a.de and XIOC-DOMAIN-01-casino.com fit blocklist entries rather than proof of runtime communication.
  • The scan record for extracted_from_files reports no malware-signature, malware, obfuscation, network, or tool-poisoning finding.
  • The metadata lists empty permissions and host permissions, plus the identifiable developer [email protected].
  • No listed finding title shows credential access, data upload, browser hijacking, or impersonation.

False Positive Considerations

  • IoC extraction from a domain-blocking list in extracted_from_files
  • Cloud and infrastructure domains in XIOC-DOMAIN-d1dext3t9dk55e.cloudfront.net and XIOC-DOMAIN-sradg.eastus.cloudapp.azure.com
  • Medium-severity labels applied to domain strings without runtime network evidence
  • High finding volume without malware-signature or obfuscation findings

Reviewed 2026-09-29; recommended action: suppress false positive; model confidence 88%.

Chrome version history

Risk trend by version

4 analyzed versions. Each point is the latest successful scan for that version; failed zero-score scans are hidden. Dates are based on first seen by risky plugins.

Selected
28
Change since first
-19
Change from previous
No change
Versions:
First analyzed version
1.3
Sep 27, 2026
Risk range
28 to 46
Across analyzed versions
Latest analyzed version
5.3
Oct 26, 2026
Selected version
low
Version
v5.3
Yesterday
Risk score
28
Findings
29
Change vs previous
No change

Pick any point on the chart to explore that version's code below.

About This Extension

Webfilter is a school-managed web filtering extension developed for Hedda Wisingskolan in Härnösand, Sweden. It enforces a static blocklist of domains across categories including social media, online gaming, VPN and proxy services, dynamic DNS providers, random chat platforms, and AI content generation tools. All filtering is performed locally on the device using Chrome's built-in declarativeNetRequest API. The extension contains no tracking, analytics, or data collection of any kind. No user data is transmitted, stored, or processed externally. The extension is force-installed and centrally managed by the school's IT administrator via Google Admin (Google Workspace for Education). Students cannot modify, disable, or remove the extension. Configuration changes are made exclusively by the administrator by publishing a new version through the Chrome Web Store. When a student attempts to navigate to a blocked domain, the browser displays a locally hosted block page informing the student that the site is restricted by the administrator. After 15 seconds the browser automatically redirects to google.com. All other resource types (scripts, images, stylesheets, API calls) from blocked domains are silently dropped before the browser initiates a network connection. A static whitelist of approved school domains is included to ensure that critical educational tools, Microsoft 365, Google Workspace, and school-specific platforms remain accessible at all times, regardless of broader blocking rules. Blocking rules are compiled into the extension at build time as static declarativeNetRequest rulesets. There are no dynamic rule updates, no remote configuration endpoints, and no dependency on external services at runtime. ----Whats new----- -------V5.3 removed rules_words.json to block freqvent search words to bypass filter -------V5.2.1 Fixed redirect → /blocked.html för main_frame, block för sub_frame, rules_words.json -------V5.2 Blocked.html fixed so countdown works .json files are merged for easier management Added rules_words.json to block freqvent search words to bypass filter added correct id-sequence and max 30000urls per .json Added new urls to the filter -------V5.0 Added schema.json due to it was missing Added more URLS to whitelist.json updated and added urls to rules_randchat.json -------V4.6 * Added AllowedDomains for an easy whitelist if a blocked URL needs to be allowed. { "allowedDomains": { "Value": [ "exempel.se", "annan-sida.com" ] } } * Added more proxy websites * Added more URL´s to the filter * Merged files to minimize the usage of files * Added more domains to randchat.url --------- V4.5 * Changed icon * Changed redirect screen * Added more VPN´s and bypass

Frequently Asked Questions