Security readout for executives and security teams
Plain-English summary
Version 0.4.9 of the popular Web Developer for Chrome extension was hijacked and shipped with hidden malicious code that committed ad fraud, redirected users through fake repair alerts, and tried to steal logins. Anyone who installed or auto-updated to that version in early August 2017 ran the backdoor under their browser identity until the maintainer pushed a clean v0.5.0.
Executive priority
Treat as a closed historical incident with low active risk if your fleet is current, but high reputational and credential-exposure risk for any user who ran v0.4.9. Prioritize a one-time audit of historical installs and credential resets, then fold extension governance into routine endpoint hygiene.
Technical view
CVE-2017-20202 covers a supply chain compromise of Web Developer for Chrome v0.4.9 (CWE-506). The trojanized build used a domain generation algorithm to fetch a remote loader, which conditionally pulled modules that enumerated standard banner sizes, substituted third-party ad calls, redirected traffic to affiliate landing pages, surfaced fake repair prompts, and harvested credentials on login events. The malicious build was identified by the maintainer on 2017-08-02 and replaced by v0.5.0.
Likely exposure
Exposure is limited to environments that installed or auto-updated to Web Developer for Chrome v0.4.9 during the brief 2017 compromise window. Modern installs from the Chrome Web Store run clean post-0.5.0 releases, so present-day exposure is largely historical credential reuse risk for users active during that window.
Exploitation context
Sources confirm the malicious version was published to the Chrome Web Store and actively executed in users' browsers, performing ad substitution, malvertising redirects, and credential harvesting. The CVE is not listed in CISA KEV, but Proofpoint and the maintainer document real-world abuse of the trojanized extension during the August 2017 incident.
Researcher notes
CWE-506 (embedded malicious code) and CVSS 4.0 9.3 reflect a supply chain trojanization rather than a coding flaw. Loader behavior relied on a DGA plus conditional module fetch, so static review of v0.4.9 is the cleanest indicator; live IOC value is limited a decade later. VulnCheck and Proofpoint coverage tie this to a broader 2017 Chrome extension hijacking campaign worth referencing in extension governance threat models.
Mitigation direction
- Confirm Web Developer for Chrome is at v0.5.0 or later, or remove it.
- Force-update or reinstall the extension from the official Chrome Web Store listing.
- Rotate credentials for any account logged into during the compromise window.
- Review browser extension allowlists and disable unused extensions.
- Monitor outbound traffic for suspicious DGA-style domain lookups from browsers.
- Enable enterprise extension management and pinning to vetted versions.
Validation and detection
- Check installed Web Developer for Chrome version against the Chrome Web Store listing.
- Inventory endpoints for any historical install of v0.4.9 via EDR or browser telemetry.
- Search proxy and DNS logs from August 2017 for unexplained algorithmic domains.
- Review SSO and account logs for anomalous logins tied to affected users.
- Validate extension signatures and update channels match the official publisher.
- Confirm no residual sibling extensions or sideloaded copies remain on managed devices.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-506: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2017-20202 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.3 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
9.3CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N
Source materials
- CVE List V5 sourceCVE List V5
- https://web.archive.org/web/20170803163618/https://chrispederick.com/blog/web-developer-for-chrome-compromised/CVE reference · vendor-advisory, patch
- https://ui.vision/blog/chrome-extension-adware/CVE reference · technical-description
- https://www.proofpoint.com/us/threat-insight/post/threat-actor-goes-chrome-extension-hijacking-spreeCVE reference · technical-description
- https://gist.github.com/piedpiperRichard/076516da60f45842f1a6e6ae35a9a240/CVE reference · exploit
- https://chromewebstore.google.com/detail/web-developer/bfbameneiokkgbdmiekhjnmfkcnldhhm?pli=1CVE reference · product
- https://www.vulncheck.com/advisories/web-developer-for-chrome-malicious-backdoor-supply-chain-compromiseCVE reference · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Embedded Malicious Code
Embedded Malicious Code represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.