Is 2FA Authenticator safe?

Clean risk

2FA Authenticator sends authenticator action events with a persistent client ID to Google Analytics.

When you open the creation popup, scan a QR code, copy a code, or request a 2FA code, the extension sends an event to Google Analytics. The event includes a stored client ID plus browser language and screen resolution, linking these authenticator actions to the same browser profile.

extension.vnv1.0.0.2Chrome Web Store
1Risk
Who publishes it

extension.vn - 3 other listings from the same operator, none carrying a finding

What this publisher told the store about itself, and the other listings that told it the same thing.

Publisher
extension.vn

Same store account

3 other listings published from this account, 209k+ users between them, none of them carrying a finding.

AI-generated. Findings may contain errors. Those marked Verified have been manually reviewed.

Publishers can request a review.

What it can do

Permissions this extension asks for, as declared in version 1.0.0.2. Asking for a permission is not a finding on its own - it is what the extension can do if it chooses to.

  • Read and change your data on every secure site you visit

    https://*/*

  • Read and change your data on every site you visit

    http://*/*

  • Store data in your browser

    storage

  • Act on the current tab, but only after you click the extension

    activeTab

  • Show a panel beside the page

    sidePanel

Where it sends data

Destinations our analysis observed 2FA Authenticator contacting. Sending data somewhere is not a finding on its own - an extension that syncs your settings has to talk to its own server - but it is where your data can go, and who else it goes to.

  • www.google-analytics.comwidely used

    2FA Authenticator sends data to www.google-analytics.com. A widely used service: 346 other extensions we have analysed send data here.

Updated 30 September 2026lihconfopkpbjpkbbcpofjofmpaopgol