browser extension

The Web Developer for Chrome Hijack

Updated 5 Oct 2026 · Incident date 2 Aug 2017

Web Developer for Chrome 0.4.9 fetched remote JavaScript and injected ads into web pages after the developer was phished on 2 August 2017.

Version 0.5 fixed the hijacked update. Proofpoint links the same actor to a spree of hijacked Chrome extensions.

What happened

An attacker stole the developer's login with a fake Google email and published a bad update through the official store.

  • Chris Pederick, the developer, got an email that claimed to be from Google about a new store policy.
  • He entered his login on a fake page. The account had no two-factor authentication.
  • Version 0.4.9 fetched JavaScript from the web and ran it in the browser to inject ads.
  • The extension had more than 1 million users.
  • Proofpoint says the code in the wider campaign fetched scripts with a domain generation algorithm and stole Cloudflare logins.

Version 0.4.9 went out late on 2 August 2017. Pederick found the problem at about 6:30 AM the next day. Version 0.5 was out about two hours later.

Affected versions

  • Web Developer 0.4.9 (fixed in 0.5).
  • Chrometana 1.1.3.
  • Infinity New Tab 3.12.3 (compromised in May 2017).
  • CopyFish 2.8.5.
  • Web Paint 1.2.1.
  • Social Fixer 20.1.1.
  • TouchVPN and Betternet VPN (suspected, late June 2017).

Indicators of compromise

  • Fake login domains: chromedevelopment[.]site, login.chromeextensions[.]info.
  • Phishing server IP range: 31.186.103.146 to 31.186.103.149.
  • Script servers made by a domain generation algorithm, in the form wd[hash][.]win.
  • Ad injection domains: partner-net[.]men, partnerwork[.]men.
  • Exfiltration domains: searchtab[.]win, redirect2[.]top.
  • Files: content.js and a remotely fetched ga.js script.

How to check

List the version of each installed Chrome extension. This command works on macOS. On Linux, use ~/.config/google-chrome/Default/Extensions instead.

grep -H '"version"' ~/Library/Application\ Support/Google/Chrome/Default/Extensions/*/*/manifest.json

What to do now

  1. Update Web Developer to 0.5 or later. Remove any other extension on the list that you do not need.
  2. Change passwords for web accounts you used in the same browser.
  3. If you use Cloudflare, rotate your Cloudflare logins and check the account for changes.
  4. If you publish extensions, turn on two-factor authentication. Open the store dashboard directly, not the email link.

Frequently asked questions

How many users did the extension have?

The Hacker News reports 1,044,000 users. The Register reports more than 1 million.

Was the Firefox version affected?

No.

Sources

  1. proofpoint.com/us/threat-insight/post/threat-actor-goes-chrome-extension-hijacking-spree
  2. thehackernews.com/2017/08/chrome-extension-for-web-developers.html
  3. theregister.com/2017/08/03/web_developer_plug_creator_confirms_phishing_attack_and_hes_not_alone/

Send this page to the person who looks after AI at your company.

Email it

More supply chain attacks

All 172 attacks in the library · What is a supply chain attack? · How to prevent supply chain attacks

Check the next update before you install it

Vigilance compares the version you trust with the new one. It names the one file that gained a power the old version did not have.

Start the free 14-day trialBrowse the attack library