Chrome Extension Ownership Transfer: 8 Buyer Red Flags
Originally published on ExtensionBooster. A Chrome extension ownership transfer keeps the same extension ID and sends no notice to users, so whoever buys your extension silently inherits every install and the auto-updat
Originally published on ExtensionBooster.
A Chrome extension ownership transfer keeps the same extension ID and sends no notice to users, so whoever buys your extension silently inherits every install and the auto-update channel. In August 2026, Socket reported a wallet-drainer campaign across 19 Chrome and Edge extensions, and five of them had been bought from their original developers before being turned malicious through ordinary updates. Here is how to read a buyout email, lock down your publishing path, and sell safely if you decide to.
Why a free extension with no revenue gets buy offers
Buyers are rarely after your code. They want a signed program that updates silently on thousands of machines and can often read every page.
- One developer who negotiated with buyers put the going rate at about $0.20 per user.
- The developer of Hover Zoom+ (300,000+ users) counted more than 130 monetization pitches over nine years, one promising up to $20K a month for "PII-free data".
- In the Socket campaign, the largest bought extension had roughly 70,000 Chrome users and 10,000 Edge users when it changed hands.
After the purchase, the new versions stripped Content-Security-Policy headers with declarativeNetRequest, kept a WebSocket open to rotating command servers, and pulled payload modules into chrome.storage to run in the page. Those modules included crypto wallet drainers, fake Ledger and Trezor seed-phrase screens, and fake browser-update lures.
What actually happens during a transfer
| Chrome Web Store | Edge Add-ons | |
|---|---|---|
| How | Google's developer account transfer form | Email with a "[Reparenting Request]" subject |
| Extension ID | Unchanged | Unchanged |
| Review | Manual, by store support | Confirmed with both publishers, about 3 weeks |
| What users see | Nothing, only the developer details change | Old owner's details stay until the new owner ships an update |
Users only get a prompt if an update asks for new permissions. That is why attackers prefer extensions that already have broad access, or that can fetch behavior from a server after review.
8 red flags in a "we'd like to buy your extension" email
One flag means be careful. Three or more means walk away.
- They ask about user counts before features.
- The buyer is vague: free webmail, a brand-new domain, no named people or company.
- The pitch says "portfolio", "data partnership", "monetize your traffic" or "add our SDK".
- They want your Google account, or to be added as a developer before payment clears.
- The timeline is rushed, or they want to pay in crypto or gift cards.
- The price is a few cents per user, with no interest in revenue, roadmap or code quality.
- They don't care whether open-source code stays open or the listing stays the same.
- They want the sale kept quiet.
A real acquirer can explain who they are, why your extension fits, what will change, and how the privacy policy will be kept, usually in a contract.
4 ways to protect your publishing path (even if you never sell)
1. Turn on Verified CRX Uploads. Every upload must then be signed with your private key, and the extension ID stays the same:
# generate a 2048-bit RSA key and keep it offline or in a secrets manager
openssl genpkey -algorithm RSA -pkeyopt rsa_keygen_bits:2048 -out cws-signing.pem
# print the public key to paste into the developer dashboard
openssl rsa -in cws-signing.pem -pubout
# pack the build with that key
google-chrome --pack-extension=./dist --pack-extension-key=./cws-signing.pem
Never commit the key. Replacing a lost one goes through support and can take up to a week.
2. Treat "Chrome Web Store Support" emails as phishing. The December 2024 Cyberhaven attack started with a fake policy email that got an employee to approve a malicious OAuth app; Darktrace counted 30+ extensions and about 2.6 million users affected. Never approve an OAuth screen reached from an email link, check policy notices in the dashboard itself, and review third-party app access on the owning Google account.
3. Diff permissions in CI before every release. A small script that fails the build when anything new appears forces a deliberate decision:
// scripts/permission-diff.mjs
import { readFileSync } from "node:fs";
const [prev, next] = process.argv.slice(2).map(f => JSON.parse(readFileSync(f, "utf8")));
const keys = ["permissions", "optional_permissions", "host_permissions", "optional_host_permissions"];
const collect = m => new Set([
...keys.flatMap(k => (m[k] || []).map(v => `${k}:${v}`)),
...(m.content_scripts || []).flatMap(cs => (cs.matches || []).map(v => `content_scripts:${v}`)),
]);
const before = collect(prev);
const added = [...collect(next)].filter(p => !before.has(p));
if (added.length) {
console.error("New permissions:\n" + added.join("\n"));
process.exit(1);
}
Run it as node scripts/permission-diff.mjs previous-manifest.json manifest.json, pulling the previous manifest from your last release tag.
4. Keep all logic in the package. Manifest V3 already bans remotely hosted code. Also avoid remote config that flips major features on and off, so reviewers can read everything your extension does.
If you do sell
- Verify the buyer: legal entity, named people, history and references.
- Write user protections into the contract: no new data collection without consent, same privacy policy, no ad injection or affiliate-link rewriting.
- Pay through escrow or a lawyer, not reversible payments.
- Tell users before the handover, and explain how to uninstall or export their data.
- Use the official transfer form, never your password, and rotate any API keys and OAuth clients you keep.
Key takeaways
- Cold buyout offers are usually priced per user, because the install base is the product.
- Transfers keep the extension ID and notify no one.
- Verified CRX Uploads, careful OAuth habits and CI permission diffs protect you whether or not you sell.
- If you sell, vet the buyer, put user protections in writing and announce it first.
The original post covers the full Socket campaign timeline, the QuickLens and ShotBird cases, and the complete permission-diff script in its guide to Chrome extension ownership transfers and buyer red flags. For more on building a trusted extension with genuine reviews, see ExtensionBooster's resources for extension and app developers.
Have you received an offer to buy your extension, and what tipped you off about whether the buyer was legitimate?
Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.