Extension icon

AzurkaVPN

Critical risk Access: Full control Trust: Unproven

Version 1.0.23 View in Chrome Web Store

Last scanned: about 6 hours ago

Extension Details

From the Chrome Web Store listing

Users
3,000
Rating
4.8 out of 5
19 ratings
Last updated
November 14, 2026
Size
153KiB
Store badges
Established publisher

Developer contact

Website
azurka.org
Email
labreadai@proton.me

Rating

Critical risk

Very powerful, unproven publisher

Avoid it unless you know exactly who publishes it and why it needs this much access.

Access · what it could do

Full control

It could take over accounts, traffic or other parts of the browser or computer.

Based on the manifest, by fixed rules: 10 findings.

Also 2 routine or minor findings.

Trust · who stands behind it

Unproven

Few users or ratings, or no listing data, so there is little to go on.

Based on the store listing and the AI check.

  • Established publisher badge
  • 3,000 users
  • Only 19 ratings
  • Updated November 14, 2026
  • Asks for more than its stated purpose needs (AI check)
  • The AI check raised concerns

AI check

Broader than its purpose needs Some concerns

An AI model compares what the extension asks for with what its listing says it does. It can lower trust, never raise it, and it never changes access.

A VPN-style proxy client for VLESS/VMess/Shadowsocks/Trojan keys. Proxy, auth and all-sites access fit that purpose; scripting and tabs are less clearly needed. A browser extension cannot natively speak these protocols, so traffic likely goes through the developer's relay.

Trust factors

  • Proxy, webRequestAuthProvider and privacy (WebRTC leak control) are typical for a VPN extension
  • No content scripts declared and no web-accessible resources
  • Developer lists a website and contact email

Concerns

  • Chrome extensions cannot run VLESS/VMess/Trojan natively; your traffic may go through an unnamed third-party server
  • scripting and tabs permissions go beyond what a proxy toggle needs
  • Listing names other VPN apps but gives no detail on how or where keys are handled
  • Contact is a generic Proton email that does not match the website domain

Recommendations

  • Check azurka.org for a privacy policy explaining where traffic and pasted keys are sent
  • Avoid pasting keys for servers you rely on until the relay setup is clear
  • Consider using it in a separate Chrome profile to keep proxied browsing apart from logged-in accounts
  • Remove it when not in use, since it can route and observe all browsing

AI analysis by claude-opus-5-5 on 2026-11-19 01:30 UTC

Findings

Site access 1 finding

  • Broad reach
    Access to All Websites
    It can read and change every website you visit, including sites where you are signed in, such as email and banking.

Browser capabilities 9 findings

  • Full control
    Permission: proxy
    It asks for the proxy permission, which lets it choose the proxy server that your browser traffic goes through. All your browsing can be sent through a server it chooses, which can see which sites you visit.
  • Broad reach
    Permission: privacy
    It asks for the privacy permission, which lets it change privacy-related browser settings. It can turn off protections such as Safe Browsing or limits on third-party cookies.
  • Scoped
    Permission: declarativeNetRequest
    It asks for the declarativeNetRequest permission, which lets it block or change network requests using rules it declares. Its rules can block pages or send you somewhere else.
  • Scoped
    Permission: scripting
    It asks for the scripting permission, which lets it run scripts and add styles in pages it has access to. A script in a page can read and change that page.
  • Scoped
    Permission: tabs
    It asks for the tabs permission, which lets it see the address and title of every open tab. The addresses of your open tabs show what you are browsing.
  • Scoped
    Permission: webRequest
    It asks for the webRequest permission, which lets it watch network requests to the sites it has access to. It can see where your browser connects on those sites.
  • Scoped
    Permission: webRequestAuthProvider
    It asks for the webRequestAuthProvider permission, which lets it answer sign-in prompts for HTTP authentication. It can answer password prompts from websites on your behalf.
2 routine permissions: alarms · storage
  • Routine
    Permission: alarms
    It asks for the alarms permission, which lets it schedule its own code to run at set times. This is a routine permission with little risk on its own.
  • Routine
    Permission: storage
    It asks for the storage permission, which lets it save data in the extension's own storage. This is a routine permission with little risk on its own.

Code and policy

Nothing found in this area.

Network destinations

10 URLs across 8 domains appear in the extension's files. See them on the Network tab