# A "sleeper extension" named by a security firm that grew to 200k users after cleanup: 2 FA Authenticator's playbook and the money it doesn't make · Chrome extension

> Source: https://stringers.io/en/ext/chrome_ebhcbenbgjmaebpgbldimndmfomjmphd.html (Stringers / 什么值得做, generated 2026-11-15)
> Stringers tracks which small products suddenly took off each day, investigates why one by one, and distils playbooks from them. Numbers come from 15 databases we collect daily, each with source and date.
> For agents: these investigations and the underlying databases (verified revenue, App Store / Google Play charts, ad libraries, GitHub, Product Hunt…) are queryable live over MCP — tools feed (daily breakouts) / plays (playbooks) / hot / products / data. Setup: https://github.com/komako-workshop/stringers (the user signs in with Google at stringers.io/en/start.html to get a personal URL). Site index: https://stringers.io/llms.txt

> Neither Google nor Microsoft's validator has a desktop version. Chrome's top 10M-user verifier hasn't been updated in two years and has only 3.59 ratings. It uses a generic word as its name, supports 55 languages, and carries the Featured badge it inherited from its malicious-gang days, which lets it siphon search traffic from the leader.

[Chrome extension](https://stringers.io/en/ext/index.md) · written 11-8

2FA Authenticator · Aleksandr Lysanov

# A "sleeper extension" named by a security firm that grew to 200k users after cleanup: 2 FA Authenticator's playbook and the money it doesn't make

**What it is** A Chrome extension that generates the same two-factor codes as Google Authenticator on your phone, fully offline. You can import accounts from your phone in one go and fill codes via right-click. Open source, with a Pro subscription since October.

**Why it took off** Neither Google's nor Microsoft's authenticator has a desktop version, and the Chrome leader has 10M users but hasn't updated in two years and sits at 3.59 stars. This one uses a generic name, is localized into 55 languages, and carries a Featured badge inherited from the malicious-group era, taking search traffic from the leader.

**C** **How to follow it** Don't build another 2FA extension for Chrome. Take its store playbook (generic keyword names, dozens of languages, pop-up right after install, ask for reviews by open count, open source with minimal permissions), and look for the next category where big companies only ship mobile versions and the top store listing has stopped updating and is rated low.

Grade C: it took off through store distribution, so the playbook is copyable. But its Featured badge, ranking and initial users were inherited from a period of malicious-group activity that followers can't get. Chrome already has 20+ similar extensions, and 200k users over 30 days only brought in $325, so following this in this category isn't worth it. Hardly anyone knows about it yet

200,000 users · rating 4.8533333333333335 (332)

2FA Authenticator is a Chrome extension that generates two-step verification codes. It launched in 2026 February, passed 200k users by September, and is rated 4.87. What got it going wasn't the features, it was Chrome Web Store distribution: the name uses the exact term people search for, the store page was localized into 55 languages, it earned a Featured badge early, and it took search traffic from a veteran that hadn't been updated in two years. Its origins aren't exactly clean either. It also ran into a problem every free tool faces: 200k people use it, paid plans started in October, and in 30 days it brought in $325. Below is how it took off, what's worth copying, and what isn't.

### The Apr 23 report

On Apr 2026 23, security firm DomainTools published a report titled "The AI Frame Campaign Continues", about a malicious extension group that reportedly infected over 2025k Chrome users since 260. The first extension the report named was this one: "a Chrome extension impersonating Google Authenticator", with over 30k downloads at the time and already carrying the store's Featured badge.

The report said it looked normal but requested permission to read every web page (`<all_urls>`), which a code generator has no use for, and its background script kept an open entry point that accepted any message. DomainTools' read was "ship clean first, push malicious updates later". After install it opened a welcome page at authenticator.whitelab.studio, and two other extensions under whitelab.studio already contained working malicious code.

18 days later, on May 11, the extension shipped version 1.7.0, which dropped `<all_urls>`. The same day, the GitHub organization authenticator-sh and the open-source repo 2fa went up, with a one-line description: "Your secrets never leave your device. No host permissions." Over the following half year, versions went from 1.5 to 1.16, reproducible builds and a security policy page were added, and the store listing spent a lot of space explaining why it can be trusted.

The developer currently listed on the store is Kobaltstack LLC in New York, at a common virtual office address. The main committer on GitHub matches an engineer in Tbilisi named Aleksandr Lysanov on LinkedIn. Whether the current authors are the same group or bought the extension from them can't be told from the outside. What is certain is that the Featured badge, store ranking, and about 30k users from the group era were kept. It's no longer listed on whitelab.studio's homepage product list.

### What it is

Click the toolbar icon and the six-digit codes for every account are listed. Click again to copy. It uses the same standard as the Google Authenticator app on your phone (TOTP), generates codes offline, and needs no sign-up. The first paragraph of the store page is blunt: "Stop pulling out your phone every time you log in. Unlock, find the app, find the account, read six digits, type them before they expire, 15 seconds each time, several times a day."

Features added since: scan the QR code from a Google Authenticator export to move your whole set of accounts over, with backups from Authy, Microsoft, 2FAS and Bitwarden readable too; right-click or a shortcut fills the code into the input box; accounts matching the current site are sorted to the top; automatic correction of computer clock drift (the most common reason codes fail); optional encryption and local backup. There's also a Mac menu bar app now.

### How fast it's growing

| Timeline | users | Sources |
|---|---|---|
| 2026-02-10 | Launched | Chrome Web Store |
| Late April | 30k+, Featured already | DomainTools report |
| 9-01 | 100k tier | Extension stats site extops.dev |
| 9-17 | 200k tier (1.13.1 shipped that day) | Same as above |
| 11-08 | 200k, 4.87 points / 324 ratings | Chrome Web Store |

Once users passed 10k, the store only shows two significant digits, so whether it kept growing after mid-September can't be seen. 11-08 On the chrome-stats overall chart it ranks #972, and #86 in the Tools category.

### Where users come from: mainly store search

Almost nobody talks about it off-store. No discussion on X, nothing on Reddit; it was launched on Product Hunt in Sep 29 with the claim "200,000+ users trust us" and got only 7 votes. Yet users still climbed to 200k. That leaves the store itself as the explanation (inference, with plenty of evidence):

- **The name is the search term.** It's called "2FA Authenticator", and the description includes "TOTP two-factor authentication" and "Google Authenticator".

- **55 languages.** The store page runs from Indonesian and Vietnamese to Swahili and Amharic. DomainTools noticed at the time that it "uses Chrome's localization system".

- **Featured came early.** In April, when it had only 30k downloads, it already had the badge. The same group's JPG to PDF and MP4 to MP3 extensions also carry Featured, which suggests they knew how to earn it.

- **The veteran stopped.** The category leader Authenticator (authenticator.cc) has 10M users, was last updated 2024-08-27, and is rated 3.59 / 2,497 ratings. Someone searching "authenticator" sees an old 3.59-star extension next to a 4.8-star one with Featured and a fresh interface, and will probably install the second.

- **The author admits it was installed casually.** The first line of 1.15.1's release notes reads: "Half of the people who install the extension never open it". The rating count is only 0.16% of the user count. This is search traffic, not word of mouth.

A few secondary channels:

- **Ratings asked by open count.** The open-source code says: after 15 opens, with at least 1 accounts, a prompt asks for a store rating; if you tap "not now", it asks again only after 50 more opens. So ratings rise in waves, 11-07 to 11-08 added 20 in a single day, and the reviews are mostly short lines like "Best 2FA", "nice", "good".

- **Programmatic SEO site.** authenticator.sh's sitemap has 2,842 URLs, mostly about 119 guides on "how to enable 2FA for Roblox / Discord / ChatGPT / Coinbase", each in 20 languages. The site ranks 10-22 globally at 980k, and climbed to 11-07 at 570k. But installing the extension automatically opens the site's welcome page, so part of that traffic is just install-driven.

- **TikTok.** The author's self-reported channels include TikTok and YouTube. One findable example: 9-28 an account with 0 followers, "Armando · Tools & Tricks", posted "The authenticator I use for Roblox: a Chrome extension called 2FA Authenticator", with 3,773 views. That account has only 3 videos total, so it looks like the author's own account, or one paid to post (unverified).

- **Ads.** No evidence of paid placement found, but it can't be ruled out.

### Why now: you're at the computer, the codes are on your phone

- **The big players only made mobile apps.** Google Authenticator and Microsoft Authenticator have no desktop version; Microsoft's own page literally says "not available for PC or Mac". People log in at a computer while the codes sit on their phone, so they search "google authenticator chrome" in the Chrome Web Store.

- **More and more places are forcing 2FA on.** Indonesia's education data system Dapodik requires every account to enable 2FA starting 2025-09-15. School operators do their work on desktops, and TikTok and YouTube are full of "how to set up Google Authenticator on a laptop without a phone" tutorials. The comments are full of Indonesian names, like ABIMANYU SATYA DANISWARA on 11-06 writing "Truly beneficial". Roblox trades require 2FA, and so do GitHub, exchanges and Discord.

- **The veteran stopped maintaining it,** and new users compare ratings in the search results.

### Who it's competing with

| Competitors | Scale | Compared with alternatives |
|---|---|---|
| Authenticator(authenticator.cc) | Chrome 10M users, 3.59 rating | The old open-source leader, not updated since 2024-08; the main target of its traffic capture |
| 2FA Authenticator(TypingDNA) | 100k, 3.35 points | Same name, requires sign-up, has in-app purchases |
| 2FAS Auth | 70k, 3.51 points | Needs to be used with a phone app |
| Authenticator - 2FA(2fauthenticator.com) | 30k, 4.6 points | Listed in June, 4 months later, same approach, an order of magnitude smaller |
| Google / Microsoft Authenticator, Authy | Hundreds of millions | Mobile only, which is exactly why this kind of extension exists |
| Proton Authenticator, Bitwarden / 1Password's built-in codes | Big | Have desktop versions, but you have to join their ecosystem or pay |

Chrome has 20+ extensions with authenticator, 2FA or TOTP in the name that have passed 5,000k users, so there's no shortage of competitors, just no one seriously polishing the experience. Copycats have already arrived: the "Authenticator" listed on 10-14 (523 users) copies its description almost word for word; Keyrook (223 users), listed on 9-17, has the exact same selling points.

There's one open gap: on the Firefox store, the leader authenticator.cc has 163k users with its last update in 2024-09; the runner-up 2FAS has only 9,263; and 11-08 itself is not on Firefox.

### Money: 200k users, $325 in 30 days

Pro launched on Oct 4,1.14.0 with monthly, yearly and lifetime one-time purchase options, paid through Stripe Link. The release notes say: "The prices you see may differ, we're still finding the right ones." Pro sells two things: unlimited accounts, and encrypted cloud backup. The free plan's account cap only applies to new installs; existing users stay unlimited.

The numbers the author publicly reported on TrustMRR (a site that shows revenue for connected payment accounts): over the last 30 days $325, MRR $7.91,8 from subscriptions, and $280 in October. Most of it is lifetime one-time purchases. 200k users produced that much money; half installed and never opened it, and few of those who did open it need "unlimited accounts".

There's also a risk. The store description still says "free, no paid tier", "no analytics", "only the storage and activeTab permissions", but Pro has existed since 1.14, the extension checks in with a server every day reporting account counts, open counts and paywall events, and its permissions grew to 5. For an extension already named in a security report, a mismatch between the description and actual behavior is an easy target for complaints or review.

### What to learn from it

1. **Find a category where the big players only have mobile apps and the store leader has stopped updating and is rated low.** The demand is already there, and so is the search traffic; nobody is serving it.

2. **Name it with a generic term, and localize the store page into dozens of languages in one go.** In store search, these two things matter more than any feature.

3. **Make it useful the moment it's installed.** After install, the welcome page opens and brings up the extension window itself, and the first screen can scan the QR code on the current page. The author added this after finding that half of users never opened it.

4. **Ask for ratings by open count, not by update.** The author's code comment says earlier ratings were low because the prompt only fired on updates.

5. **In trust-sensitive categories, open source, minimal permissions and reproducible builds are the selling point.** That's how it turned from "malicious extension" back into a trusted one.

### If it were you

**C: worth learning from, not worth following.** It captured traffic through store distribution, and that playbook can be learned. But following it in the 2FA category isn't worth it: the Featured badge, the name and the 200k users are all inherited, and a follower can't get them; there are already 20+ similar products; and 200k users only brought in $325 over 30 days.

**Who it's for** : people who have built Chrome extensions and understand store search and multilingual localization, using this playbook to find the next category where the big players only have mobile apps and the store leader has stopped updating; or teams that want to use a free verification-code tool to funnel users into a bigger product (password management, shared team codes).

**Who it's not for** : anyone who wants to build yet another 2FA extension on Chrome (the name, badge and ratings are all taken; 2fauthenticator.com, which went after the same play at the same time, only reached 30k); anyone who wants to make money from this (200k users, 30 days, $325); anyone without store distribution experience who wants to win on features (when it hit its first 100k users, right-click code fill and code sharing didn't exist yet).

**How to do it** : start by picking the category. Search a generic term in the Chrome Web Store. If the top results were last updated over a year ago, rate below 4, yet have millions of users, and big companies have phone apps but no desktop version, that's the pattern. Then name it with the generic term, localize the store page into dozens of languages, request the fewest permissions possible, open source it if you can; on install, open a welcome page and pop the extension open; ask for reviews based on how many times it's been opened. If you really must build 2FA, the only visible gap right now is Firefox, but the pool there is small, and since it's open source you can port it over any time.

**How to get users** : store search is the core, everything else is secondary. You can build multilingual "how to enable 2FA for X" pages; or make tutorial videos aimed at a group forced to use 2FA, like school operators on Dapodik or Roblox players. Don't count on Product Hunt.

**Deadline** : this isn't a window-limited opportunity, no need to rush. If you do want the Firefox gap, ship before Q1 of 2027, ahead of the point where it gets ported over.

**Where this read could be wrong** : ① if its Pro revenue climbs past a few thousand dollars a month within a few months, that shows free-to-paid works for this kind of tool, and the opportunity should be rated higher; ② if the store pulls its Featured badge or delists it for mismatched descriptions, the top spot for 2FA on Chrome opens up and deserves another look; ③ late entrants like 2fauthenticator.com, which inherited no assets, also reached 100k, which suggests the intercept play doesn't depend on inherited assets, so following it has more value; ④ conversely, if Google ships a desktop or Chrome version of Authenticator, this whole category disappears.

[Chrome store page ↗](https://chromewebstore.google.com/detail/2fa-authenticator/ebhcbenbgjmaebpgbldimndmfomjmphd)

**Research notes: competitor table, acquisition evidence, full research report**

Competitors

| Name | Where | Launched | Scale | How it differs from this one |
|---|---|---|---|---|
| Authenticator(authenticator.cc) | Chrome | 2014-04 | 10M users, 3.59 stars / 2,497 ratings | The long-running open-source leader, but no updates since 2024-08, low ratings, dated UI; this one is more up to date, rated 4.87, and has taken its search traffic |
| 2FA Authenticator(TypingDNA) | Chrome | 2018-02 | 100k users, 3.35 / 54 | Same name; has in-app purchases and requires an account, low ratings |
| Authenticator(npjilhodcgmigpladpfkkclbmkebalfd) | Chrome | 2024-11 | 90k users, 3.76 / 41 | A small no-website clone, unmaintained after 2025-08 |
| 2FAS Auth | Chrome | 2022-07 | 70k users, 3.51 / 130 | Meant to be paired with a phone app; the extension itself has low ratings |
| Authenticator - 2FA(2fauthenticator.com) | Chrome | 2026-06 | 30k users, 4.6 / 10 | A similar new entrant 4 months later, an order of magnitude smaller |
| Google Authenticator / Microsoft Authenticator / Authy | Big-company features | Years | Hundreds of millions | Phone app only, no desktop, which is exactly why this product exists |
| Proton Authenticator | Other | 2025 | Not verified | Has a full desktop app across platforms, but it's tied to the Proton ecosystem and isn't competing for search on the Chrome Web Store |
| Bitwarden / 1Password have TOTP built in | Other | Years | Big | Requires paying or switching password managers |

Where users come from

- Inferred **Chrome Web Store search + Featured badge (generic-term name, 55 languages)** : the name is literally "2FA Authenticator"; 2026-04 already carries the Featured badge (DomainTools); almost zero external discussion yet it climbed to 200k; the author says "half of people who installed it never opened it"; ratings / users ratio 0.16%

- **Verified** **Programmatic SEO site** : sitemap has 2,842 URLs (about 119 articles on "how to enable 2FA" for each service × 20 languages); Tranco ranked 980k → 570k; CrUX September top 1M globally, top 500k in several countries; installing the extension auto-opens the site's welcome page, so some traffic is an echo of installs

- **Verified** **In-extension review prompt** : src/utils/review-prompt.ts: prompts only after 15 opens and at least 1 accounts; ratings rose in waves (11-07 to 11-08, up 20 reviews)

- Inferred **TikTok seeding** : @armandougc (0 followers, 3 videos total) posted a Roblox-scenario video 2026-09-28 with 3,773 views; the creator's self-reported channels on TrustMRR include TikTok and YouTube

- **Checked** **Product Hunt** : launched on 2026-09-29 with 7 votes, never made the homepage (producthunt library); a browser-extension promo banner ran for a day and didn't help

- **Verified** **Store assets inherited from a malicious extension ring** : DomainTools 2026-04-23: this id and authenticator.sh belong to the AiFrame / whitelab.studio ring, with 30k downloads at the time and Featured already granted; chrome-stats: publisher 2026-04-11 change, 2026-05-11 dropped <all_urls>, a GitHub repo created the same day

## 2FA Authenticator (authenticator.sh): why it took off

> Chrome extension · id ebhcbenbgjmaebpgbldimndmfomjmphd · research date 2026-11-08

### One line

A Chrome extension that generates TOTP two-factor codes offline in the browser. Launched 2026-02-10, reached 2026-09-17 users by 200.

It took off mainly through store distribution; the product itself is secondary. The name claims the category's generic term "2FA Authenticator" outright, the store page is localized into 55 languages, and it had the Featured badge by April. The category leader authenticator.cc has 10M users, but hasn't been updated in two years and has a 3.59 rating. So people searching "authenticator / 2FA" on the Chrome store often installed this one, which had 4.8+ ratings and a newer interface.

Some background on where it came from. 2026-04 The security firm DomainTools flagged it: this id and the authenticator.sh domain both trace back to the AiFrame malicious extension ring (whitelab.studio). At the time it had 30k downloads, carried the Featured badge, and requested `<all_urls>` permission, which got it labeled a "clean first, poisoned later" sleeper extension. After the report went out, 2026-05-11 the extension dropped `<all_urls>`, open-sourced on GitHub the same day, and has been iterating fast since. It added a Pro subscription in October and started charging, though revenue is still small (TrustMRR: $325 over 30 days).

### 1. Basic data

- **Store page** (read on 2026-11-08): 200,000 users, rated 4.87 out of 5 from 324 ratings. Version v1.16.0,2026-11-04, 834KiB, 55 languages. Carries the "Featured" and "Established publisher" badges. The developer is listed as Kobaltstack LLC at 447 Broadway Fl 2, New York (a common virtual office address in NYC), with a D-U-N-S number 149915302 and EU trader status. Our database records the developer as Aleksandr Lysanov, with the publisher contact cws@authenticator.sh. No in-app purchases are checked on the store.

- **Our database** (chromestore.item_snap): user count stayed in the 11-01 to 11-09 range, at the 200k tier; ratings count went from 291 to 324,9 over 33 days. Of that, 11-07→11-08 alone added 20 ratings in one day.

- **extops.dev curve** : from 9-01 to 9-15 it sat in the 100k tier, then **jumped to the 200k tier on 9-17** (the day it was posted about, 1.13.1), and has stayed in the 200k tier since. The ratings count is 9-01, 180,10-10, 260,11-09, 324. The store only gives two significant figures above 10k users, so whether it kept growing after 9-17 can't be determined.

- **Earlier readings** : DomainTools' report from 2026-04-23 says "Over 30,000 downloads", and it already carried Featured at the time (see section 4). Taken together: launched February, about 30k in April, 100k in early September, 200k in mid-September.

- **chrome-stats** (2026-11-08): #972 overall, #86 in Tools.

### 2. Competitors

| Product | Where | Launched | Scale | How it differs |
|---|---|---|---|---|
| Authenticator(authenticator.cc) | Chrome/Firefox/Edge, open source | 2014-04 | 10M users, 3.59 stars / 2,497 ratings | The category leader, recommended by many university IT departments; **last updated 2024-08-27** , low ratings, dated UI. It's the main target this extension is intercepting |
| 2FA Authenticator(TypingDNA) | Chrome | 2018-02 | 100k users, 3.35 / 54 | Same name; has in-app purchases and requires an account, low ratings |
| Authenticator (npjil…, no website) | Chrome | 2024-11 | 90k, 3.76 / 41 | A no-name clone, unmaintained after 2025-08 |
| 2FAS Auth | Chrome (paired with a phone app) | 2022-07 | 70k, 3.51 / 130 | Meant to be used with a phone app; the 2FAS ecosystem recommended by PCMag editors |
| Authenticator app(Albert Kag) | Chrome | 2025-07 | 40k, 4.29 / 24 | Similar function, no website or companion products |
| Authenticator - 2FA(2fauthenticator.com) | Chrome | 2026-06 | 30k, 4.6 / 10 | A similar new entrant 4 months later, with pricing on its website |
| Google Authenticator / Microsoft Authenticator / Authy | Phone app (big company) | Years | Hundreds of millions | None have a desktop or browser version (Microsoft's official docs say "not available for PC or Mac"). This is the root reason these extensions exist |
| Proton Authenticator | Full desktop + phone across platforms | 2025 | Not verified | The only major brand with a proper desktop app, but it's tied to the Proton ecosystem |
| Bitwarden / 1Password have TOTP built in | Password manager | Years | Big | Requires paying or switching password managers |

Bottom line: this category isn't short on competitors; Chrome is flooded with similar tools (in our database, ≥5,000 users with authenticator / 2FA / TOTP in the name, there are 20+ of them). But the top spots are an unmaintained old extension plus a pile of small clones rated 2–4 stars, and **nobody is seriously maintaining the experience** .

### 3. Growth tactics (where users come from)

1. **Chrome Web Store search + Featured badge** (inferred, strong evidence, but no direct source data):
    - The name is the generic search term "2FA Authenticator", and the description stuffs in "TOTP two-factor authentication" and "Google Authenticator". The store page is translated into 55 languages. DomainTools noticed at the time that it "uses Chrome's localization system".
    - Got Featured 2026-04 ago. Other extensions from the same ring (JPG to PDF, MP4 to MP3) also carry Featured (chromestore database), so this group knows how to earn the badge.
    - Almost no external discussion: zero posts on X, nobody mentioned it on Reddit, the Product Hunt launch flopped. Yet users kept climbing to 200k.
    - The author wrote in the v1.15.1 release notes: "Half of people who installed it never opened it." Ratings / users is only 0.16%. This looks like "install on the way past" traffic from store search, not word of mouth.

2. **Programmatic SEO site** (confirmed to exist; how much traffic it drives is unverified): the sitemap has 2,842 URLs in total, roughly 119 "how to enable 2FA for [service]" guides (Roblox, Discord, ChatGPT, Coinbase, Workday…) × 20 languages, plus a blog. Tranco rank went from 2026-10-22 at 980,071 to 11-07 at 573,074 (traffic database). CrUX September puts it in the top 1M globally, and in the top 500k in Brazil, Indonesia, Mexico, Vietnam, Thailand, the Philippines, Turkey, Spain, France, Australia and the US. Note: installing the extension auto-opens authenticator.sh's welcome page, so part of the site's traffic is just an echo of installs.

3. **TikTok / YouTube** (the author's self-reported channels on TrustMRR are SEO, YouTube, TikTok, Product Hunt): on TikTok we found @armandougc ("Armando · Tools & Tricks", 0 followers) posting 2026-09-28 a clip saying "the authenticator I use for Roblox: a Chrome extension called 2FA Authenticator", 3,773 views. The account has only 3 videos, and the other two are learning-style content, which looks like either the author's own account or a paid seeding account (unverified). The YouTube API quota ran out, so no specific videos were found.

4. **Product Hunt** : launched 2026-09-29, tagline "200,000+ users trust us", only 7 votes, never made the homepage (producthunt database). It ran a one-day banner in the extension for 200k users asking them to leave reviews, not votes, and that didn't work either. We can confirm PH was not a growth source.

5. **Extension review prompt (confirmed)** : `src/utils/review-prompt.ts` says the "Rate us on the store" prompt only appears after 15 opens with at least 1 accounts; if the user taps "Not now," it waits for 50 more opens before asking again. The code comments say that ratings were low before because the prompt only fired on updates. So ratings climb in bursts (10-30 to 11-01 added 16 reviews, 11-07 to 11-08 added 20), and the reviews are mostly short lines like "nice", "good", "Best 2FA". The approach is legitimate, but the rating count doesn't prove word of mouth.

6. **Ads** : Our Google ad library only tracks products on our list, and we didn't find this one. It doesn't show up in the other libraries either. Paid acquisition can't be ruled out, but there's no evidence for it.

### 4. Origin: from "suspected malicious extension" to a cleaned-up open-source product

- **DomainTools, "The AI Frame Campaign Continues" (2026-04-23):** This extension ID is named as a fake Google Authenticator extension, and the official site authenticator.sh is listed as a lure site. At the time, the manifest requested `<all_urls>` without using it, and the service worker kept an empty listener that accepts any message. The report's verdict: "deploy clean, update dirty," meaning a malicious update could be pushed at any time. Once installed, it opens a welcome page at authenticator.whitelab.studio and uses a Google Form to track uninstalls. The submitter's email domain is airnetic.space, matching several AiFrame-group extensions. AiFrame has reportedly infected 260k+ Chrome users over the past 2025 years, and two more extensions under whitelab.studio already carry working malicious payloads (hidden iframe injection, fake paywalls).

- **chrome-stats change log** : On 2026-04-11 the publisher changed from ai***** @gmail.com to qa***** @gmail.com, and on 2026-11-04 to su***** @authenticator.sh. On permissions, **2026-05-11 (v1.5.3→1.7.0) dropped `<all_urls>`** ; then 5-12 added activeTab, 8-21 added contextMenus and scripting, and 9-05 added sidePanel.

- **On the same day (2026-05-11) they created the GitHub org authenticator-sh and the repo 2fa** . The repo description says "No host permissions" outright. Later they added reproducible builds, a SECURITY.md, and a security policy page. The main committer, Asrover, has 44 commits, which matches Aleksandr Lysanov on LinkedIn (AI engineer & Fullstack, Tbilisi, graduate of the Moscow Aviation Institute); another committer is aleksandr1strel. The commit history contains many `worktree-agent-…` branch merges, which suggests batch development with AI coding agents. The founding date self-reported on TrustMRR is 2026-04-16, right after the publisher change.

- **Current state** : The whitelab.studio homepage no longer lists Authenticator. It now lists only tools like HEIC/PNG conversion, Image Upscaler, and NPI lookup, and claims "1M+ users."

- **How to read it** (inference): Either someone from the group split off this cleanest, most valuable extension and built a company around it, or it was sold to its current author. Either way, it **inherited the Featured badge, store ranking, and roughly 30k starting users built up during the group era** . After being publicly named, its response was "open source + cut permissions + publish a security model" to rebuild trust. That's why its store copy now spends so much space explaining why you can trust it.

### 5. Why now: the demand side

- **Mandatory 2FA is spreading, and often on desktop** :
    - Indonesia's education data system Dapodik has required 2025-09-15FA for all accounts since **2** (Kemendikdasmen guidelines, Kompasiana). School operators do their work on computers, and TikTok and YouTube are full of tutorials on "using Google Authenticator on a laptop without a phone." Its reviews include many Indonesian names (ABIMANYU SATYA DANISWARA, Kautsar Tisamawi, and others).
    - Roblox trading requires 2FA, and the creator's promo video targets Roblox.
    - Add GitHub, exchanges, and Discord.

- **Big players don't make desktop versions** : Google Authenticator and Microsoft Authenticator are mobile-only, so users search the Chrome Web Store for "google authenticator chrome."

- **The category leader has stopped updating** : authenticator.cc last updated on 2024-08 and is rated 3.59. Newcomers compare ratings in search results and naturally pick this one, with 4.8 stars and Featured status.

### 6. Differentiation

- **Compared with authenticator.cc and the pile of small clones** , here's what it does well:
    - Scan the QR code from a Google Authenticator export (camera, uploaded screenshot, or a direct screen capture) and import the whole list at once. It can also read backups from Authy, Microsoft, 2FAS, Proton, FreeOTP, and Bitwarden.
    - Right-click or Ctrl+Shift+Y to fill the code straight into the input field, and it sorts the matching account to the top based on the current site.
    - Detects and corrects clock drift on your computer, the most common reason codes fail.
    - Shares a code link valid for one hour without exposing the secret key.
    - Optional AES-256-GCM encryption with recovery codes, and it keeps 7 local backups automatically.
    - Open source, reproducible builds, very few permissions. There's also a Mac menu bar app.

- **Are these features why it took off?** Mostly no. When the first 100k users arrived, most of these features didn't exist yet: right-click fill was added in August 1.12, share links in September 1.13, and the early version was just "a working TOTP generator plus Google Authenticator import." **What actually got it going was store distribution** : a generic name, 55 languages, Featured status, high ratings. Product polish matters later: it keeps the rating at 4.8+, so it keeps outranking the leader in search, and it makes the "why you can trust it" pitch credible. Also, after September the user count stalled around the 200k level, and paid plans started in October, which suggests polish alone didn't bring another growth wave.

### 7. Monetization and visibility

- **Monetization** : v1.14.0 (2026-10-04) launched Pro with monthly, yearly and lifetime plans, paid via Stripe Link. Only new installs get a cap on free accounts; old users stay unlimited, and the limit is served from the backend and can be A/B tested. v1.15.0 added encrypted cloud backup. TrustMRR numbers: $325 in 30 days, $7.91,8 MRR from subscriptions, $280 in October. The revenue is mostly lifetime one-time purchases and is completely out of proportion to 200k users.

- **Contradictory copy** (a risk point):
    - The store description still says "Free, with no paid tier, no trial," "No analytics," and "two permissions: storage and activeTab."
    - In reality: Pro has existed since v1.14; it checks in daily with api.authenticator.sh, reporting account counts, open counts, and paywall events; v1.15.0 added "onboarding telemetry"; and the manifest now has 5 permissions.
    - Only the Privacy section on the store says "no data collected." This could draw complaints later, or trouble from store review.

- **Visibility** : Revenue is public on TrustMRR but small and undiscussed. X has zero mentions, and the Product Hunt launch failed. The only public coverage is a security report that flagged it as malicious. Overall, "few people know about it yet."

### 8. Copycats

- `bkdfkahakfehndnnpebadkefeabdihij` "Authenticator" (listed 2026-10-14, 523 users): The description is nearly a word-for-word copy of its "fast 2FA codes in your browser — TOTP two-factor authentication, offline. Import from Authenticator."

- 2FA Authenticator - Keyrook (2026-09-17,223 users): Same positioning and selling points (scan QR, one-click fill, import from Google Authenticator, encrypted sync).

- Authenticator - 2FA (2fauthenticator.com, 2026-06-1.73M users): A newer product with the same playbook from the same period. The store recommends it alongside this one.

### 9. What others can borrow

- Find a category where big players only make mobile apps and the top browser-store product has stopped updating and has low ratings. Use a generic name, localize the store page into dozens of languages, and aim for Featured first.

- Automatically open the official welcome page after install, and let the extension pop it up from within the page (externally_connectable), turning installation into the first-use experience.

- Trigger rating requests based on open count for a tool users open themselves, not on version updates. It works much better.

- Programmatic SEO pages like "how to enable 2FA on X" in 20 languages, following search intent to bring people to the extension.

- In trust-sensitive categories (secrets, passwords), open source, minimal permissions, and reproducible builds are the selling point itself.

- A cautionary lesson: converting 200k free users to paid is very hard ($325 over 30 days). Money for tools like this more likely comes from a Mac app or enterprise plans than from the extension.

### 10. Still unclear

- Real user growth after 9-17: The store only shows the 100k tier, so it can't be seen.

- Channel split: How much comes from store search, Google SEO, and TikTok has no data. Whether it runs paid ads: our library doesn't track it.

- Whether the current author and the whitelab/airnetic group are the same people, or whether someone bought the extension: only the publisher change and the timeline are circumstantial evidence.

- When and how the Featured badge was obtained.

- Whether the store's Featured status could be revoked because the copy doesn't match actual behavior.

### Sources

- Chrome Web Store page: [chromewebstore.google.com/detail/2fa-authenticator/ebhcbenbg…](https://chromewebstore.google.com/detail/2fa-authenticator/ebhcbenbgjmaebpgbldimndmfomjmphd) (2026-11-08)

- Store reviews page /reviews (2026-11-08)

- extops.dev: [extops.dev/extensions/ebhcbenbgjmaebpgbldimndmfomjmphd](https://extops.dev/extensions/ebhcbenbgjmaebpgbldimndmfomjmphd) (90-day readings)

- chrome-stats (scraped via Exa): [chrome-stats.com/d/ebhcbenbgjmaebpgbldimndmfomjmphd](https://chrome-stats.com/d/ebhcbenbgjmaebpgbldimndmfomjmphd) (publisher and permission change log)

- DomainTools:[dti.domaintools.com/securitysnacks/the-ai-frame-campaign-con…](https://dti.domaintools.com/securitysnacks/the-ai-frame-campaign-continues)(2026-04-23)

- GitHub: [github.com/authenticator-sh/2fa](https://github.com/authenticator-sh/2fa) (repo created 2026-05-11,59 stars; docs/release-notes/v1.10–v1.16; src/utils/review-prompt.ts; src/billing/gate.ts)

- Official site: [www.authenticator.sh/](https://www.authenticator.sh/), /pro, /sitemap.xml (2,842 URLs)

- whitelab.studio homepage (2026-11-08), authenticator.whitelab.studio/en/welcome

- Our library: chromestore (item / item_snap / related), traffic (rank_day, crux_domain), indie (TrustMRR: 2fa-authenticator), producthunt (post 1242251), googleads (adv_map)

- TikTok (TikHub): @armandougc 2026-09-28 video

- Dapodik mandatory 2FA: Kemendikdasmen guide PDF, Kompasiana, Scribd "Penerapan 2FA di Dapodik"

This article was written by AI from public data and the data we collect daily. Numbers are sourced, and inferences are labeled.
