2FA Authenticator Assistant
- 34 users
- No ratings yet
- #1,723in Privacy & Security
Companion to github.com/wuzf/2fa. Deploy a 2FA instance, then connect to view, copy and autofill two-factor authentication codes.
by wzf · 1 listing
- Users
- 34
- #1,723 of 5,957 in category
- Rating
- —
- No ratings yet · median 4.35
- Version
- 1.3.0
- 2.77 MiB · Manifest V3
- Access
- Low16/100
- 3 permissions
Description
As written by the publisher on the store2FA Authenticator Assistant (2FA 验证助手) is the browser companion for the open-source wuzf/2fa project. Connect your own instance to view, copy and fill time-based one-time passwords (TOTP). It supports 15 languages in one extension: Simplified Chinese, Traditional Chinese, English, Japanese, Korean, German, French, Spanish, Portuguese (Brazil), Italian, Russian, Turkish, Indonesian, Vietnamese and Thai. The interface follows your browser language or a manual selection in Display language. Unsupported browser languages use English.
What’s new in 1.3.0: Better detection of code fields on authenticator app pages. A single 6- or 8-digit field labeled only “Code” or “Enter code” can now be filled without clicking it first, when the page clearly asks for the code from an authentication app and nothing nearby points to an SMS or email code, such as a delivery message, a send or resend button or a countdown. Automatic filling still needs your approval for the website and a clear account match. Visible fields in dialogs with rounded corners, such as those in Meta Accounts Center, are no longer ignored.
A self-hosted instance is required. Deploy the project, add your accounts and sign in to that instance in the same browser profile before connecting the extension. The extension does not provide hosted accounts and does not connect directly to arbitrary authenticator products.
- Features
- View current and upcoming codes; search by service, username or email.
- Pin frequently used accounts and remember account bindings for individual websites.
- Fill a code with the account's Fill button or Ctrl+Shift+U (Command+Shift+U on macOS).
- Explicitly enable automatic filling for a website, while filling a code or with “Autofill on this website”. After you approve access to that site, the extension detects code fields on its pages. It fills the remembered account or a unique reliable match, or offers a choice of matching accounts.
- Work with common single-field and segmented code inputs, accessible same-origin frames and open Shadow DOM. Copy and paste remains available when a page is incompatible.
- Switch between self-hosted instances while keeping each instance's website bindings separate.
Connection options
The default mode uses your existing website login session. The extension retrieves account secrets from your configured instance and calculates codes temporarily in its background process without persistently storing the seeds. The instance's tab may be closed, but code generation requires a working connection and a valid login session.
You can explicitly enable "Allow offline use" (允许离线使用). After synchronization, the extension stores the current instance's account secrets and time calibration in this browser and can calculate codes after the instance tab is closed, the browser restarts or the network becomes unavailable. This local cache contains raw secrets and has no additional password encryption; enable it only on a trusted device. Turning offline use off, switching instances or revoking instance access deletes this extension cache. Uninstalling deletes the extension's local data. While offline, the extension cannot immediately learn about server-side account deletion or session revocation.
Permissions and data
Site access is requested only when you configure an instance or explicitly enable automatic filling for a target website. Automatic filling is additionally restricted to the authorized full origin (scheme, host and port), or to a single page if you limit it in the settings. Settings, account bindings and favorites stay in the current browser and are not synchronized through your browser account.
The extension handles account names, usernames, TOTP secrets and codes, and reads the page structure needed to fill a code. On an identifiable Google TOTP page, it can use the displayed signed-in email to match the account. This processing serves code display, matching and filling only. Filling shares the selected code with the target page; a multiple-account panel displays names and usernames for that site's candidates. The complete account vault and seeds are not provided to target websites.
There are no ads, telemetry or developer relay service. Online requests go to your configured instance for accounts, server time and service icons; that instance and its hosting provider receive normal network requests. The extension does not click Submit, although a website may submit its own form after the code is filled.
For desktop Chrome and Edge. Incognito mode and counter-based HOTP codes are not supported.
Project: https://github.com/wuzf/2fa
Deployment guide: https://github.com/wuzf/2fa/blob/main/docs/DEPLOYMENT.md
Support: https://github.com/wuzf/2fa/issues
https://github.com/wuzf/2fa/blob/main/extension/PRIVACY.md
Ratings and reviews
Ratings as the store shows themNo written reviews held for this listing yet.
Track 2FA Authenticator Assistant on Radar
This page shows the listing as it is today. Add it to Radar and get one email when it changes.
- Users and rating
- Store text and screenshots
- Permissions it asks for

2FA Authenticator Assistant, in plain words
What it is, what to use instead, what it can access and how to fix it.
2FA Authenticator Assistant at a glance
2FA Authenticator Assistant is a Privacy & Security extension by wzf with 34 users. It has no store ratings yet, so there is little public feedback to go on. By users it sits in the top half of Privacy & Security extensions.
- By users
- #1,723of 5,957 in Privacy & Security
- Access
- Low16 of 100
2FA Authenticator Assistant alternatives
Closest by what they do · users as the store shows them · bars on a log scaleIs 2FA Authenticator Assistant safe?
2FA Authenticator Assistant asks for 3 permissions. None of them are on our list of wide-access permissions.
Permissions show what it could do, not what it does. See the full permission list.
activeTabNot on our wide-access listscriptingNot on our wide-access liststorageNot on our wide-access list
Every permission 2FA Authenticator Assistant asks for
3 permissions · none sensitive · Low access overallBrowser permissions · 3
- Work on the tab you click it on
activeTab - Run its code on pages it can access
scripting - Save its own settings
storage
Sensitive marks access that reaches your data or other sites. The access level is a 0 to 100 score of all of it: under 25 is Low, 60 and up is High.
2FA Authenticator Assistant not working?
What recent reviews say
Store reviews from the last 90 daysWe have no recent public signals of problems with 2FA Authenticator Assistant.
Common fixes
Try them in this order- 1Update Chrome and the extension
- 2Turn it off and on in chrome://extensions
- 3Reload the page
- 4Turn other extensions off in case two clash
Still stuck? Contact the maker or try an alternative.
Know when a listing changes
Track any extension on Radar: users, rating, permissions and store text, with one email when something moves.