When Chrome Extensions Turn Rogue: The Hidden Dangers Behind Browser Add-ons

A sophisticated spam campaign that took advantage of 131 malicious Chrome extensions masquerading as WhatsApp Web automation tools was discovered by a recent cybersecurity investigation. These extensions, which were mostly aimed at Brazilian clients, were linked to DBX Tecnologia, a single business that supported a reseller model that let affiliates rebrand and distribute nearly identical copies. The extensions violated Chrome Web Store standards by covertly automating bulk messages and getting beyond WhatsApp’s anti-spam measures, even though they were represented as CRM or sales tools. By showing how fraudsters expand spam operations, gather data, and avoid detection by using legitimate platforms and business models, this example emphasizes the growing risk of malicious or cloned browser extensions and emphasizes the necessity of stricter extension vetting and user awareness.

Technical Description

In order to interact with and automate WhatsApp’s built-in features, the campaign made use of customized Chrome extensions that introduced malicious JavaScript straight into the WhatsApp Web interface. The extensions might schedule automatic outreach, send bulk messages, and get around WhatsApp’s rate constraints by executing alongside authentic scripts. A centralized development source was indicated by the fact that all 131 extensions had a common codebase, infrastructure, and command patterns.

The extensions employed obfuscation techniques to hide automation functionality from Chrome’s review mechanisms and talked with distant servers for command updates. Their actions qualified as spamware even though they weren’t considered classic malware because they abused browser permissions and API access to enable unsolicited communications on a large scale while posing as genuine productivity tools. The details and technicalities of the attack campaign are discussed further:

Delivery and Infection Chain:

The malicious Chrome extensions were released through the Google Chrome Web Store under an appearance of genuine WhatsApp Web sales automation or customer relationship management (CRM) products. Features like lead tracking, message scheduling, and automated follow-ups were promised by these add-ons. Marketing websites like zapvende[.]com and lobovendedor[.]com[.]br, which marketed the extensions as tools to enhance customer connection, were used to encourage Brazilian small businesses. After installation, the extensions loaded into the user’s browser automatically and enabled automation by embedding scripts into the web.whatsapp.com domain. The Infection chain was identified as follows,

  • Assuming it was a CRM or marketing tool, victims manually installed one of the 131 malicious extensions from the Chrome Web Store.
  • The extension hooked into WhatsApp’s web interface and APIs by inserting malicious JavaScript onto the page when the user visited web.whatsapp.com.
  • After that, the script carried out commands that enabled bulk message dispatch and automated message scheduling without requiring human input.
  • In order to synchronize spam campaigns and update configurations, the extension interacted with distant servers that were managed by DBX Tecnologia and affiliates.
  • To keep the campaign running well, the extensions were routinely inspected for updates or new commands. If any were found or eliminated, new clones were published to the Chrome Web Store to replace them.

Technical Capabilities:

Due to their sophisticated automation capabilities, the malicious Chrome extensions were able to directly communicate with and control the WhatsApp Web interface. They introduced JavaScript code into the WhatsApp Web environment after installation, running alongside authentic programs to automate scheduling, contact management, and bulk message sending without user consent. The extensions could get beyond anti-spam rate constraints and automate outreach tasks that normally demand for human interaction by taking over WhatsApp’s internal APIs. In order to facilitate dynamic configuration updates and synchronization across several cloned versions, each extension maintained remote connectivity with centralized servers under the operators’ control. In order to get over Chrome’s automated review mechanisms, the extensions also exploited obfuscation techniques and codebase reuse, which may have exposed user information including contacts and message metadata through backend API calls.

Attribution and Evolution:

Brazilian businesses running a white-label reseller program under the direction of DBX Tecnologia have been attributed for the campaign. The same extension was marketed for selling through affiliates under names like Grupo OPT, WL Extensão, and WLExtensão. With resellers spending roughly R$12,000 (~USD $2,180) for the right to sell cloned versions, sold with promises of significant recurring revenue, the operation operated on a franchise-like model. Over the course of nine months, new variants were added to the Chrome Web Store with updated metadata to replace versions that had been previously withdrawn or warned, demonstrating ongoing adaptability and evasion strategies.

Active Campaign and Geographic Spread:

Targeting Portuguese-speaking consumers and companies that utilize WhatsApp Web for customer service, this was mostly active in Brazil. Together, the extensions had more than 20,905 active users, mostly from Brazil and the surrounding Latin American countries. Through message forwarding chains, the spam was able to reach thousands of WhatsApp users worldwide, despite the fact that small businesses were the primary victims. At least until October 17, 2025, when fresh uploads were still being found, the campaign was still in operation,

Compromised Extensions

Chrome Extension Identifier Compromise Date C2 Domains
Proxy SwitchyOmega (V3) hihblcmlaaademjlakdpicchbjnnnkbo 30/12/2024 proxyswitchyomega[.]pro
GraphQL Network Inspector ndlbedplllcgconngcnfmkadhokfaaln 29/12/2024 graphqlnetwork[.]pro
YesCaptcha assistant jiofmdifioeejeilfkpegipdjiopiekl 29/12/2024 yescaptcha[.]pro
Castorus mnhffkhmpnefgklngfmlndmkimimbphc 26/12/2024 castorus[.]info
Uvoice oaikpkmjciadfpddlpjjdapglcihgdle 26/12/2024 uvoice[.]live
VidHelper – Video Download Helper egmennebgadmncfjafcemlecimkepcle 26/12/2024 videodownloadhelper[.]pro
ParrotTalks kkodiihpgodmdankclfibbiphjkfdenh 25/12/2024 parrottalks[.]info
Bookmark Favicon Changer acmfnomgphggonodopogfbmkneepfgnh 25/12/2024 bookmarkfc[.]info
Internxt VPN dpggmcodlahmljkhlmpgpdcffdaoccni 25/12/2024 internxtvpn[.]pro
Vidnoz Flex cplhlgabfijoiabgkigdafklbhhdkahj 25/12/2024 vidnozflex[.]live
Cyberhaven pajkjnmeojmbapicmbpliphjmcekeaac 24/12/2024 cyberhavenext[.]pro
Wayin AI cedgndijpacnfbdggppddacngjfdkaca 19/12/2024 wayinai[.]live
Reader Mode llimhhconnjiflfimocjggfjdlmlhblm 18/12/2024 readermodeext[.]info
Primus (prev. PADO) oeiomhmbaapihbilkfkhmlajkeegnjhe 18/12/2024 primusext[.]pro
TinaMind befflofjcniongenjmbkgkoljhgliihe 15/12/2024 tinamind[.]info
VPNCity nnpnnpemnckcfdebeekibpiijlicmpom 12/12/2024 vpncity[.]live

Conclusion:

This kind of activity is not a typical malware infection, but rather a cunning misuse of browser extension ecosystems. Using what appeared to be authentic business tools, the attackers built a massive spamware network by taking advantage of the trust of individuals in the Chrome Web Store and WhatsApp Web. White-label commercialization, code reuse, and policy evasion all show how the threat model is changing and how cyber risk interacts with automation and monetization. The issue also highlights the growing risk of supply chain-style misuse in browser extensions and the shortcomings of browser security testing.

Impact

The impact of the campaign was broad, impacting individual users, businesses, and platform integrity.  Due to automated spam activity, more than 20,000 users were exposed to high-risk spamware masquerading as genuine productivity tools, which might have resulted in data leaks, privacy violations, and account limits. When their WhatsApp accounts were flagged or blocked, small and medium-sized businesses in Brazil suffered financial losses and damage to their reputations after being tricked into buying and implementing these bogus CRM extensions. On a larger scale, the operation exposed structural flaws in browser extension vetting and policy enforcement, undermining trust in Google’s Chrome Web Store and WhatsApp Web. The event serves as a reminder of how browser-based automation abuse can develop into a substantial online danger with worldwide spam ramifications.

IOC and Context Details

Topics Details
Tactic Name Initial Access, Execution, Persistence, Command and Control, Defense Evasion, Collection
Technique Name Malicious browser extension distribution
JavaScript injection into web application
Remote command and control
Repackaging / white-label reseller model
Obfuscation and code reuse
Policy abuse for spam automation
Sub Technique Name Chrome Web Store delivery of repackaged extensions
DOM / script injection into web.whatsapp.com to automate UI actions
Scheduled bulk messaging and rate-limit evasion
Centralized backend for configuration and command updates
Frequent re-uploads and branding changes to evade detection
Marketing as CRM tools to gain user trust and permissions
Attack Type Malware
Targeted Applications Google Chrome, WhatsApp Web
Region Impacted Brazil & Latin America
Industry Impacted Small and medium-sized businesses
IOC’s Domains
chromewebstore-noreply[.]com
chromeforextension[.]com
supportchromestore[.]com
extensionpolicyprivacy[.]com
policyextension[.]info
extensionpolicy[.]net
checkpolicy[.]site
dearflip[.]pro
iobit[.]pro
ultrablock[.]pro
yujaverity[.]info
censortracker[.]pro
wakelet[.]ink
pieadblock[.]pro
locallyext[.]ink
moonsift[.]store
linewizeconnect[.]com
savgptforchrome[.]pro
gptdetector[.]live
bardaiforchrome[.]live
searchcopilot[.]co
chatgptextent[.]pro
youtubeadsblocker[.]live
geminiaigg[.]pro
chataiassistant[.]pro
aiforgemini[.]com
chatgptextension[.]site
blockforads[.]com
ytbadblocker[.]com
geminiforads[.]com
savegptforyou[.]live
searchgptchat[.]info
savechatgpt[.]site
adskiper[.]net
savegptforchrome[.]com
chatgptforsearch[.]com
searchaiassitant[.]info
goodenhancerblocker[.]site
internetdownloadmanager[.]pro
openaigptforgg[.]site
adsblockforyoutube[.]site
promptheusgpt[.]info
gpt4chrome[.]live
savegpt[.]pro
gptforads[.]info
gptforbusiness[.]site

IPs
136.244.115[.]219
45.76.225[.]148
137.220.48[.]214
149.248.44[.]88
149.28.124[.]84
140.82.45[.]42
155.138.253[.]165
108.61.23[.]192
149.248.2[.]160
140.82.50[.]201
45.77.5[.]196
149.28.117[.]236
65.20.99[.]178
45.77.185[.]211
149.248.56[.]63
185.92.222[.]127
136.244.113[.]231
144.202.101[.]155
CVE NA

Recommended Actions

  • Only install Chrome extensions from trusted publishers, check reviews, and validate the developer’s reputation. Avoid extensions promising unrealistic business gains.
  • Review and restrict extension permissions; avoid granting full access to sensitive applications like WhatsApp Web unless necessary.
  • Use browser security tools to detect unusual script injections, automated messaging, or other abnormal behaviors from installed extensions.
  • Periodically review and remove unused or suspicious extensions to reduce attack surface.
  • Train employees and small business owners to recognize marketing tactics that disguise malicious tools as CRM or productivity software.
  • Deploy endpoint monitoring and antivirus solutions capable of detecting high-risk automation scripts or unauthorized data transmissions.
  • Organizations should create policies restricting the installation of extensions on corporate devices, especially those interacting with communication platforms like WhatsApp Web.
  • Promptly report suspicious or malicious extensions to Google Chrome Web Store and messaging platforms to trigger takedowns and prevent wider distribution.

References

https://www.gasa.org/post/cyberhaven-and-the-chrome-extension-breach-lessons-from-a-sophisticated-phishing-attack