fake VPN extensions were reported in a gHacks article published via Google News on 2026-08-24 that identified more than 700 browser add-ons described as fake and estimated about 75,000 total installs.
What happened: the gHacks finding: fake VPN extensions
- According to the gHacks report cited in the RSS cluster, researchers found over 700 fake VPN extensions listed on the Chrome Web Store.
- The report states these extensions had a combined install count of around 75,000.
- The findings were shared through a Google News feed item that referenced the gHacks article; the RSS metadata carried the headline and summary used here.
Who is affected by the report
- Users who installed any of the identified extensions are the most directly affected; the report implies those installs represent potential exposure but does not publish a list of specific extension names in the RSS data provided.
- Developers and legitimate VPN vendors may be indirectly affected through reputation risk or increased scrutiny of extensions labeled as VPNs.
- The broader Chrome Web Store ecosystem — including extension reviewers and platform operators — may also be implicated because the presence of many fake entries raises questions about discovery and vetting processes.
What changes are expected or possible
- The report itself does not specify platform actions. Based on the nature of the finding, possible changes that stakeholders might consider include:
- Increased review or removal of flagged extensions by the Chrome Web Store team.
- Users may be advised to audit installed extensions and remove suspicious VPN add-ons.
- Security researchers and industry watchers could publish follow-up analyses or lists to help users identify problematic extensions.
- These outcomes are potential responses inferred from the report's discovery; the RSS item does not confirm any specific takedown or remediation steps by the store operator.
When changes may take effect and timing uncertainty
- The RSS cluster provides a publication timestamp (2026-08-24) for the gHacks story; that date marks when the report was made public via the feed.
- The report does not include a timeline for removals, user notifications, or other platform actions in the data provided here.
- Any concrete changes (for example, extension removals or official advisories) would depend on subsequent actions by the Chrome Web Store operator or security researchers and are not confirmed in the supplied RSS content.
Verification limits and uncertainty
- This article is based solely on the gHacks report as surfaced in the RSS cluster. The feed supplied a headline and summary but no primary dataset or full investigative methodology.
- The numbers presented — "over 700" and "about 75,000 installs" — come from the gHacks summary in the RSS item; the underlying research details, criteria for labeling an extension as "fake," and the list of affected extension IDs were not included in the RSS data.
- Because the available material is secondary reporting, there is limited ability here to independently confirm which exact extensions are involved or how the install-count totals were calculated.
What users and administrators can do now
- Users: review installed browser extensions labeled as VPNs, remove anything unfamiliar, and check for official vendor guidance when possible.
- Administrators / platform operators: consider reviewing flagged categories and respond to researcher disclosures; any concrete platform intervention would need confirmation from the Chrome Web Store operator.
- Researchers: the report may warrant further investigation; however, methodological details are needed before broader conclusions are drawn.
Bottom line
The gHacks report in the provided RSS feed claims a sizable group of fake VPN extensions exists on the Chrome Web Store with roughly 75,000 installs. The finding raises potential risks for users and the platform, but the RSS data does not include primary evidence or a timeline for removals. More detailed verification from primary sources or follow-up reporting will be needed to confirm which extensions are affected and what remedial steps are taken.