<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>Browser-Security - PhishFort | AI-Powered Brand Protection</title><link>https://phishfort.com/resources/blog/tag/browser-security/</link><description>PhishFort delivers agentic brand protection: detecting and eliminating phishing sites, fake apps, and impersonations across every digital channel.</description><generator>Hugo -- gohugo.io</generator><language>en-US</language><lastBuildDate>Mon, 08 Jun 2026 13:22:04 +0000</lastBuildDate><atom:link href="https://phishfort.com/resources/blog/tag/browser-security/index.xml" rel="self" type="application/rss+xml"/><item><title>7 Critical Browser Extension Security Risks: How to Stay Safe in 2026</title><link>https://phishfort.com/browser-extension-security-risks-prevent-phishing/</link><pubDate>Tue, 17 Mar 2026 12:00:00 +0000</pubDate><dc:creator>PhishFort Team</dc:creator><guid>https://phishfort.com/browser-extension-security-risks-prevent-phishing/</guid><description><![CDATA[<p>Browser extension security risks represent a growing supply-chain threat where attackers hijack legitimate, trusted software to gain unfettered access to your private data. The primary danger stems from the buy-and-infect model, where cybercriminals purchase established extensions from independent developers, push a malicious update, and exploit the trust users have already placed in that tool to execute code directly inside your active browser tabs.</p>
<h2 id="key-takeaways">Key Takeaways</h2>
<ul>
<li><strong>The Buy-and-Infect Model:</strong> Hackers specifically target popular, free extensions with established user bases to minimize suspicion during the update process.</li>
<li><strong>Automated Bypass:</strong> Malware authors use <em>stagers</em> — innocuous code that fetches malicious payloads from external servers days or weeks after installation — to bypass store moderation.</li>
<li><strong>The Manifest Manipulation:</strong> Attackers modify the <code>manifest.json</code> file to expand permission scope, effectively granting themselves the ability to read or change all data on sites you visit.</li>
<li><strong>Proactive Defense:</strong> You must adopt a least-privilege mindset by auditing permissions, restricting site access, and removing extensions you do not actively use.</li>
</ul>
<hr>
<h2 id="what-are-browser-extension-security-risks">What Are Browser Extension Security Risks?</h2>
<p>Browser extension security risks are vulnerabilities that occur when an add-on, initially created for productivity or utility, is weaponized to perform unauthorized actions like credential theft, session hijacking, or malware distribution. Because browser extensions operate within the browser&rsquo;s memory and have access to the Document Object Model (DOM) of your active tabs, they occupy a privileged position that few other applications possess.</p>]]></description><content:encoded><![CDATA[<p>Browser extension security risks represent a growing supply-chain threat where attackers hijack legitimate, trusted software to gain unfettered access to your private data. The primary danger stems from the buy-and-infect model, where cybercriminals purchase established extensions from independent developers, push a malicious update, and exploit the trust users have already placed in that tool to execute code directly inside your active browser tabs.</p>
<h2 id="key-takeaways">Key Takeaways</h2>
<ul>
<li><strong>The Buy-and-Infect Model:</strong> Hackers specifically target popular, free extensions with established user bases to minimize suspicion during the update process.</li>
<li><strong>Automated Bypass:</strong> Malware authors use <em>stagers</em> — innocuous code that fetches malicious payloads from external servers days or weeks after installation — to bypass store moderation.</li>
<li><strong>The Manifest Manipulation:</strong> Attackers modify the <code>manifest.json</code> file to expand permission scope, effectively granting themselves the ability to read or change all data on sites you visit.</li>
<li><strong>Proactive Defense:</strong> You must adopt a least-privilege mindset by auditing permissions, restricting site access, and removing extensions you do not actively use.</li>
</ul>
<hr>
<h2 id="what-are-browser-extension-security-risks">What Are Browser Extension Security Risks?</h2>
<p>Browser extension security risks are vulnerabilities that occur when an add-on, initially created for productivity or utility, is weaponized to perform unauthorized actions like credential theft, session hijacking, or malware distribution. Because browser extensions operate within the browser&rsquo;s memory and have access to the Document Object Model (DOM) of your active tabs, they occupy a privileged position that few other applications possess.</p>
<p>When an extension goes rogue, it essentially becomes a Trojan Horse. You believe you are using a tool to block ads, format PDFs, or manage passwords, but that same tool is silently capturing your keystrokes, injecting malicious scripts, or exfiltrating your browser cookies to an attacker&rsquo;s command-and-control (C2) server.</p>
<h2 id="how-do-cybercriminals-use-buy-and-infect-attacks">How Do Cybercriminals Use Buy-and-Infect Attacks?</h2>
<p>Cybercriminals execute buy-and-infect attacks by targeting independent developers who are exhausted by the maintenance of popular, free extensions. When a developer receives a lucrative offer to sell their project, they often accept without vetting the buyer, unaware that the purchaser is a shell company acting on behalf of malicious actors.</p>
<p>Once the ownership transfer is complete, the trap is set. Because browsers like Chrome and Edge are designed to keep users secure through automatic background updates, the new owner can push a minor update to every user simultaneously. The user sees no red flags, receives no new permission prompts, and remains entirely unaware that the extension&rsquo;s internal DNA has been rewritten to facilitate an attack.</p>
<h2 id="why-does-automated-store-moderation-fail-to-stop-malicious-extensions">Why Does Automated Store Moderation Fail to Stop Malicious Extensions?</h2>
<p>Automated store moderation fails to stop malicious extensions because it relies heavily on static analysis — scanning the code for known malware signatures at the moment of submission. Malware authors circumvent this by writing stagers, which are tiny, clean-looking pieces of code that do nothing during the initial review process.</p>
<p>After the extension is approved and installed on thousands of machines, the stager then fetches the actual malicious payload from an external, attacker-controlled domain. By delaying the malicious behavior for days or even weeks after the update, attackers effectively bypass the initial automated review.</p>
<table>
  <thead>
      <tr>
          <th style="text-align: left">Defense Mechanism</th>
          <th style="text-align: left">Why It Often Fails</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td style="text-align: left"><strong>Automated Static Analysis</strong></td>
          <td style="text-align: left">Cannot detect code that is fetched from an external server later.</td>
      </tr>
      <tr>
          <td style="text-align: left"><strong>User Permission Prompts</strong></td>
          <td style="text-align: left">Users often click &ldquo;Allow&rdquo; without reading the full scope of access.</td>
      </tr>
      <tr>
          <td style="text-align: left"><strong>Review Timers</strong></td>
          <td style="text-align: left">Malware triggers behavior only after a delay to evade sandbox analysis.</td>
      </tr>
      <tr>
          <td style="text-align: left"><strong>Store Bans</strong></td>
          <td style="text-align: left">By the time one malicious extension is banned, the attacker has already moved to another.</td>
      </tr>
  </tbody>
</table>
<h2 id="what-is-the-technical-anatomy-of-an-extension-hijack">What Is the Technical Anatomy of an Extension Hijack?</h2>
<p>The technical anatomy of an extension hijack centers on the manifest.json file, the fundamental blueprint that defines what an extension is allowed to do. When an extension is hijacked, the new developer modifies this file to request elevated permissions, such as the ability to &ldquo;Read and change all your data on the websites you visit.&rdquo;</p>
<p>This permission allows the extension to monitor every interaction you have with your web apps, banking sites, and crypto wallets. The extension can then inject JavaScript to scrape sensitive form data, steal session tokens, or even alter the transaction destination for crypto transfers — all while appearing perfectly normal to the end user.</p>
<h2 id="how-can-you-protect-your-browser-from-rogue-extensions">How Can You Protect Your Browser from Rogue Extensions?</h2>
<p>To protect your browser from rogue extensions, you must strictly practice the principle of least privilege. This means assuming that any third-party code you install is a potential liability and taking active steps to minimize the blast radius if an extension becomes compromised.</p>
<h3 id="follow-these-4-steps-to-secure-your-browser">Follow These 4 Steps to Secure Your Browser:</h3>
<ol>
<li><strong>Ruthless Auditing:</strong> Navigate to <code>chrome://extensions/</code> (or the equivalent in your browser) and delete every single extension you do not use daily.</li>
<li><strong>Restrict Site Access:</strong> Right-click on your essential extensions and change their <strong>Site access</strong> to <em>On click</em> rather than <em>On all sites</em>. This ensures the extension only runs when you explicitly authorize it.</li>
<li><strong>Watch for &ldquo;Permission Creep&rdquo;:</strong> If a simple utility suddenly requests a new, invasive permission, uninstall it immediately. Never click Allow blindly.</li>
<li><strong>Use Official Versions:</strong> Stick to extensions provided by verified companies or reputable, well-funded open-source projects with high community scrutiny.</li>
</ol>
<hr>
<h2 id="frequently-asked-questions-faqs">Frequently Asked Questions (FAQs)</h2>
<p><strong>Q: Can I trust extensions with millions of users?</strong></p>
<p>A: High user counts are not a guarantee of safety. Attackers actively look for high-install-count extensions to acquire because they provide instant access to a massive, trusted user base. Always check if the extension&rsquo;s ownership has recently changed.</p>
<p><strong>Q: Does Incognito Mode protect me from malicious extensions?</strong></p>
<p>A: Not necessarily. Depending on your browser settings, extensions may still be enabled in Incognito/Private mode. You must manually verify in your extension settings that <em>Allow in Incognito</em> is disabled for all extensions unless absolutely required.</p>
<p><strong>Q: How do I know if my browser extension has been hijacked?</strong></p>
<p>A: Indicators include sudden browser slowdowns, unexpected redirects to phishing pages, or pop-up ads appearing on websites that shouldn&rsquo;t have them. If your extension starts asking for new permissions, uninstall it immediately and run a security scan.</p>
<hr>
<h2 id="conclusion--next-steps">Conclusion &amp; Next Steps</h2>
<p>Browser extensions are a double-edged sword. While they offer incredible utility, they also provide a direct pathway for threat actors to bypass network security and execute code on your personal device. Trust is temporary; an extension that is safe today can easily become a weapon tomorrow with a single malicious update. Vigilance is your only true line of defense.</p>
<p>If your organization is concerned about browser-based threats, brand impersonation, or supply chain attacks, you need visibility that extends beyond your corporate perimeter.</p>
<p><a href="/solutions"><strong>Protect your brand and digital assets with our comprehensive Digital Risk Protection solutions today.</strong></a>
</p>
]]></content:encoded><category>Cybersecurity</category><category>security</category><category>browser-security</category><category>phishing</category><category>brand-protection</category></item><item><title>10 Key Insights into Chrome Extension Phishing and How PhishFort's Nighthawk Protects You</title><link>https://phishfort.com/chrome-extension-phishing/</link><pubDate>Mon, 01 Jan 2024 10:10:00 +0000</pubDate><dc:creator>Matt Marx</dc:creator><guid>https://phishfort.com/chrome-extension-phishing/</guid><description><![CDATA[<p>














  
  
  
    
    
    

    
    

    
      
      
      
        
          
          
        
      
        
          
          
        
      
        
          
          
        
      
        
      
        
      
      

      <img src="/img/2025-08-image-73.webp"
        srcset="/img/2025-08-image-73_hu_adc2146b56f2921.webp 480w, /img/2025-08-image-73_hu_da9d4949746b51c9.webp 768w, /img/2025-08-image-73_hu_63d241904a394c55.webp 1200w, /img/2025-08-image-73.webp 1600w"
        sizes="(max-width: 768px) 100vw, 700px"
        alt="Chrome extension phishing investigation"
        
        width="1600" height="569"
        
        loading="lazy"
        >
    
  




<em>The investigation was carried out by <a href="https://mycrypto.com/" target="_blank" rel="noopener">MyCrypto</a>
 and PhishFort</em></p>
<p><em>PhishFort has recently launched <strong>Nighthawk:</strong> an extension monitoring and takedown service as part of our comprehensive phishing protection suite which includes social media, websites, domains, mobile applications, and takedowns. This was borne out of research conducted alongside MyCrypto into the phishing attacks delivered over Chrome browser extensions, including Chrome extension phishing.</em></p>]]></description><content:encoded><![CDATA[<p>














  
  
  
    
    
    

    
    

    
      
      
      
        
          
          
        
      
        
          
          
        
      
        
          
          
        
      
        
      
        
      
      

      <img src="/img/2025-08-image-73.webp"
        srcset="/img/2025-08-image-73_hu_adc2146b56f2921.webp 480w, /img/2025-08-image-73_hu_da9d4949746b51c9.webp 768w, /img/2025-08-image-73_hu_63d241904a394c55.webp 1200w, /img/2025-08-image-73.webp 1600w"
        sizes="(max-width: 768px) 100vw, 700px"
        alt="Chrome extension phishing investigation"
        
        width="1600" height="569"
        
        loading="lazy"
        >
    
  




<em>The investigation was carried out by <a href="https://mycrypto.com/" target="_blank" rel="noopener">MyCrypto</a>
 and PhishFort</em></p>
<p><em>PhishFort has recently launched <strong>Nighthawk:</strong> an extension monitoring and takedown service as part of our comprehensive phishing protection suite which includes social media, websites, domains, mobile applications, and takedowns. This was borne out of research conducted alongside MyCrypto into the phishing attacks delivered over Chrome browser extensions, including Chrome extension phishing.</em></p>
<h2 id="motivation-and-purpose-for-nighthawk">Motivation and Purpose for Nighthawk</h2>
<p>We keep an eye on the type of attacks that come to cryptocurrency users on a daily basis and often write about our findings to help educate the community. We&rsquo;ve seen various types of attacks on users, ranging from <a href="https://medium.com/mycrypto/research-into-trust-trading-scams-on-twitter-ba6309d87a18" target="_blank" rel="noopener">simple trust-trading scams</a>
 to <a href="https://medium.com/mycrypto/what-to-do-when-sim-swapping-happens-to-you-1367f296ef4d" target="_blank" rel="noopener">SIM hijacking</a>
 to compromising and stealing funds from exchange accounts.</p>
<p>














  
  
  
    
    
    

    
    

    
      
      
      
        
          
          
        
      
        
          
          
        
      
        
      
        
      
        
      
      

      <img src="/img/2025-08-image-74.webp"
        srcset="/img/2025-08-image-74_hu_7a2a14cb75ed254a.webp 480w, /img/2025-08-image-74_hu_b910523b75009444.webp 768w, /img/2025-08-image-74.webp 879w"
        sizes="(max-width: 768px) 100vw, 700px"
        alt="An example of a malicious extension being delivered via Google Ads"
        
        width="879" height="627"
        
        loading="lazy"
        >
    
  




<em>An example of a malicious extension being delivered via Google Ads</em></p>
<p>Recently, we&rsquo;ve come across big campaigns pushing fake browser extensions to users and targeting well-known brands via Google Ads and other channels. Whilst this is not a new attack vector — and we&rsquo;ve <a href="https://medium.com/mycrypto/the-dangers-of-malicious-browser-extensions-ef9c10f0128f" target="_blank" rel="noopener">written about malicious browser extensions</a>
 before — the brands targeted are new.</p>
<p>These attacks highlight the increasing importance of awareness regarding Chrome extension phishing among users.</p>
<p>The goals of the research are:</p>
<ul>
<li>Educate &ldquo;everyday-users&rdquo; on what the different attack vectors are</li>
<li>Report on big campaigns to make people aware</li>
<li>Give &ldquo;everyday-users&rdquo; real-life examples of attacks so they are more likely to enforce security controls on their assets</li>
<li>Help shut down scam campaign infrastructure</li>
<li>Gather intelligence to feed into custom tools to help detection before victims are made</li>
</ul>
<h2 id="overview">Overview</h2>
<p>We have found a range of extensions targeting brands and cryptocurrency users. Whilst the extensions all function the same, the branding is different depending on the user they are targeting. Essentially, the extensions are phishing for secrets — mnemonic phrases, private keys, and keystore files. Once the user has entered them, the extension sends an HTTP POST request to its backend, where the bad actors receive the secrets and empty the accounts.</p>
<p>We&rsquo;ve identified 14 unique <a href="https://www.secpod.com/blog/command-and-control-servers-things-you-should-know/" target="_blank" rel="noopener">C2s</a>
 (also known as a command &amp; control server that continues to communicate with your compromised system) but by using fingerprinting analysis, we can link specific C2s to each other to conclude which of the phishing kits have the same bad actor(s) behind them. Some kits sent the phished data back to a Google Docs form. However, most hosted their own backend with custom PHP scripts. The C2s identified are:</p>
<ul>
<li><code>analytics-server296[.]xyz</code></li>
<li><code>coinomibeta[.]online</code></li>
<li><code>completssl[.]com</code></li>
<li><code>cxext[.]org</code></li>
<li><code>ledger[.]productions</code></li>
<li><code>ledgerwallet[.]xyz</code></li>
<li><code>mecxanalytic[.]co</code></li>
<li><code>networkforworking[.]com</code></li>
<li><code>trxsecuredapi[.]co</code></li>
<li><code>usermetrica[.]org</code></li>
<li><code>walletbalance[.]org</code></li>
<li><code>ledgers[.]tech</code></li>
<li><code>vh368451[.]eurodir[.]ru</code></li>
<li><code>xrpclaim[.]net</code></li>
</ul>
<p>Whilst some of the domains are relatively old, 80% of the C2s were registered in March and April 2020 (an even split). The oldest domain (ledger.productions) has the most &ldquo;connections&rdquo; to other C2s in terms of fingerprints, so we have some indication of the same backend kit (or same actors behind this) for the majority of the extensions.</p>
<p>














  
  
  
    
    
    

    
    

    
      
      
      
        
          
          
        
      
        
          
          
        
      
        
      
        
      
        
      
      

      <img src="/img/2025-08-image-75.webp"
        srcset="/img/2025-08-image-75_hu_14aa4008a329d93d.webp 480w, /img/2025-08-image-75_hu_29a89ddb7edd11fa.webp 768w, /img/2025-08-image-75.webp 970w"
        sizes="(max-width: 768px) 100vw, 700px"
        alt="C2 domain connections"
        
        width="970" height="417"
        
        loading="lazy"
        >
    
  



</p>
<p>We&rsquo;ve also inspected some of the other C2s for common log files, and whilst most of them did not have them available on the web root, some issuing 403&rsquo;s, there was one that belonged to trxsecuredapi.co that gave <em>some small</em> insight (if we take it all at face value):</p>
<ul>
<li>The server used for this C2 is trxsqdmn</li>
<li>The admin email follows this mask: &ldquo;b — 0@r — r.ru&rdquo; — potentially indicating Russia-based actors</li>
<li>The first log was 29-Mar-2020 10:43:14 America/New_York</li>
<li>The C2 hosts files other than those to collect the phished secrets</li>
</ul>
<p>Below is a video of how a malicious extension targeting MyEtherWallet users works. It looks the same as your typical MyEtherWallet experience until you type in your secrets. After you&rsquo;ve submitted them, the malicious application sends your secrets back to the server controlled by the bad actor(s) before sending you back to the default view, and then does nothing, resulting in either:</p>
<ul>
<li>A user getting frustrated and submitting secrets again (maybe even different ones)</li>
<li>A user uninstalling the extension and forgetting about the ramifications of typing their secrets until their wallet is drained of funds — which most likely will be after the extension is removed from the store so they cannot investigate where their security hole was.</li>
</ul>
<div style="position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden;">
      <iframe allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share; fullscreen" loading="eager" referrerpolicy="strict-origin-when-cross-origin" src="https://www.youtube.com/embed/kRoDFPu27cw?autoplay=0&amp;controls=1&amp;end=0&amp;loop=0&amp;mute=0&amp;start=0" style="position: absolute; top: 0; left: 0; width: 100%; height: 100%; border:0;" title="YouTube video"></iframe>
    </div>

<p>Some of the extensions have had a network of fake users rate the app with 5 stars and give positive feedback on the extension to entice a user to download it. Most of the positive feedback by bad actors were low quality, such as &ldquo;good,&rdquo; &ldquo;helpful app,&rdquo; or &ldquo;legit extension.&rdquo; One extension did stand out by having the same &ldquo;copypasta&rdquo; around 8 times, authored by different users, sharing an introduction into what Bitcoin is and explaining why the [malicious] MyEtherWallet was their preferred browser extension (Note: MEW doesn&rsquo;t support Bitcoin).</p>
<p>There was also a network of vigilant users who wrote legitimate reviews about the extensions being malicious — however, it is hard to say if they were victims of the phishing scams themselves, or just helping the community to not download.</p>
<p>














  
  
  
    
    
    

    
    

    
      
      
      
        
          
          
        
      
        
          
          
        
      
        
          
          
        
      
        
      
        
      
      

      <img src="/img/2025-08-image-76.webp"
        srcset="/img/2025-08-image-76_hu_a1472ad89e2e9525.webp 480w, /img/2025-08-image-76_hu_e56d198a4b11a56d.webp 768w, /img/2025-08-image-76_hu_86f849dbc65fcb99.webp 1200w, /img/2025-08-image-76.webp 1512w"
        sizes="(max-width: 768px) 100vw, 700px"
        alt="A collage of reviews on various malicious extensions"
        
        width="1512" height="627"
        
        loading="lazy"
        >
    
  




<em>A collage of reviews on various malicious extensions</em></p>
<p>Google Webstore has a report section and we&rsquo;ve had the extensions removed within 24 hours.</p>
<p>An analysis from our dataset suggests the malicious extensions started to hit the store slowly in February 2020, increased releases through March 2020, and then rapidly released more extensions in April 2020.</p>
<ul>
<li><strong>February 2020:</strong> 2.04% were published in this month from our dataset</li>
<li><strong>March 2020:</strong> 34.69% were published in this month from our dataset</li>
<li><strong>April 2020:</strong> 63.26% were published in this month from our dataset</li>
</ul>
<p>This means that either our detection is getting much better, or that the number of malicious extensions hitting browser stores to target cryptocurrency users is <strong>growing exponentially</strong>.</p>
<p>An analysis from our dataset suggests Ledger is the most targeted brand — without speculating, it&rsquo;s hard to say why. Ledger accounted for 57% of the attacks that were discovered.</p>
<h2 id="where-did-the-stolen-funds-go">Where did the stolen funds go?</h2>
<p>We&rsquo;ve sent funds to a few addresses and submitted the secrets to the malicious extensions. However, they were not automatically swept. This could be for a couple of reasons:</p>
<ul>
<li>The bad actors are only interested in high-value accounts</li>
<li>The bad actors have to manually sweep accounts</li>
</ul>
<p>Even though our addresses weren&rsquo;t swept, there have been public reports from users about losing funds to malicious browser extensions:</p>
<ul>
<li><a href="https://support.google.com/chrome/thread/39247659" target="_blank" rel="noopener">Google Chrome Support Thread: Extension stole funds</a>
</li>
</ul>
<p>If you suspect you have become a victim of a malicious browser extension, please report it to <a href="https://www.phishfort.com/resources/report-phishing" target="_blank" rel="noopener">PhishFort</a>
.</p>
<h2 id="how-can-i-stay-safe">How can I stay safe?</h2>
<p>Whilst there are many different attack vectors for everyday cryptocurrency users that are not limited to malicious browser extensions, the following will be addressing only the malicious browser extensions.</p>
<h3 id="i-am-an-everyday-user-of-cryptocurrency">I am an everyday user of cryptocurrency.</h3>
<ul>
<li>Familiarize yourself with what permissions each of your browser extensions have by going to chrome://extensions/ and clicking on the &ldquo;Details&rdquo; tab for each extension.</li>
<li>Understand the risks associated with each permission.</li>
<li>Consider removing the extension if it has permissions that you feel are out of scope of the extension use.</li>
<li>Limit extensions to only execute on <a href="https://support.google.com/chrome_webstore/answer/2664769" target="_blank" rel="noopener">certain domains or when you click the extension icon</a>
 in the top right corner of your browser.</li>
<li>READ: A fake anti-cryptominer targeting MyEtherWallet[.]com and Blockchain[.]com domains — <a href="https://medium.com/mycrypto/hunting-huobi-scams-662256d76720" target="_blank" rel="noopener">https://medium.com/mycrypto/hunting-huobi-scams-662256d76720</a>
</li>
<li>READ: A fake cashback extension targeting popular cryptocurrency exchanges — <a href="https://medium.com/mycrypto/the-dangers-of-malicious-browser-extensions-ef9c10f0128f" target="_blank" rel="noopener">https://medium.com/mycrypto/the-dangers-of-malicious-browser-extensions-ef9c10f0128f</a>
</li>
<li>Consider creating a separate browser user that you use solely for cryptocurrency data — this will limit any attack surface scope, and a separation of concerns (personal and cryptocurrency profiles), increasing the privacy related to your cryptocurrency profile.</li>
</ul>
<h3 id="i-am-a-teamcompany-providing-a-solution-to-everyday-users">I am a team/company providing a solution to everyday users.</h3>
<ul>
<li>Consider monitoring the browser extension stores if your product meets the criteria we&rsquo;ve seen targeted — by using either in-house monitoring or partnering with a third-party that will investigate and take down these extensions on your behalf. PhishFort offer this service. If you think we can assist you, <a href="/contact-us/">please reach out to us.</a>
</li>
<li>Remind and enforce users to stay safe with their secrets.</li>
<li>Deprecate the use of raw secrets (mnemonic phrases, keystore files, private keys) with your product and promote other signing mechanisms.</li>
<li>Create a public list of all your products and links so users have a reliable source of trusted information.</li>
</ul>
<h2 id="iocs">IOCS</h2>
<h3 id="extension-ids">Extension IDs:</h3>
<p>afephhbbcdlgdehhddfnehfndnkfbgnm, agfjbfkpehcnceblmdahjaejpnnnkjdn, ahikdohkiedoomaklnohgdnmfcmbabcn, ahlfiinafajfmciaajgophipcfholmeh, akglkgdiggmkilkhejagginkngocbpbj, anihmmejabpaocacmeodiapbhpholaom, bhkcgfbaokmhglgipbppoobmoblcomhh, bkanfnnhokogflpnhnbfjdhbjdlgncdi, bpfdhglfmfepjhgnhnmclbfiknjnfblb, bpklfenmjhcjlocdicfadpfppcgojfjp, ckelhijilmmlmnaljmjpigfopkmfkoeh, dbcfhcelmjepboabieglhjejeolaopdl, dbcfokmgampdedgcefjahloodbgakkpl, ddohdfnenhipnhnbbfifknnhaomihcip, dehindejipifeaikcgbkdijgkbjliojc, dkhcmjfipgoapjamnngolidbcakpdhgf, effhjobodhmkbgfpgcdabfnjlnphakhb, egpnofbhgafhbkapdhedimohmainbiio, ehlgimmlmmcocemjadeafmohiplmgmei, epphnioigompfjaknnaokghgcncnjfbe, gbbpilgcdcmfppjkdociebhmcnbfbmod, glmbceclkhkaebcadgmbcjihllcnpmjh, gpffceikmehgifkjjginoibpceadefih, idnelecdpebmbpnmambnpcjogingdfco, ifceimlckdanenfkfoomccpcpemphlbg, ifmkfoeijeemajoodjfoagpbejmmnkhm, igkljanmhbnhedgkmgpkcgpjmociceim, ijhakgidfnlallpobldpbhandllbeobg, ijohicfhndicpnmkaldafhbecijhdikd, jbfponbaiamgjmfpfghcjjhddjdjdpna, jfamimfejiccpbnghhjfcibhkgblmiml, jlaaidmjgpgfkhehcljmeckhlaibgaol, kjnmimfgphmcppjhombdhhegpjphpiol, lfaahmcgahoalphllknbfcckggddoffj, mcbcknmlpfkbpogpnfcimfgdmchchmmg, mciddpldhpdpibckghnaoidpolnmighk, mjbimaghobnkobfefccnnnjedoefbafl, mnbhnjecaofgddbldmppbbdlokappkgk, nicmhgecboifljcnbbjlajbpagmhcclp, njhfmnfcoffkdjbgpannpgifnbgdihkl, noilkpnilphojpjaimfcnldblelgllaa, obcfoaeoidokjbaokikamaljjlpebofe, oejafikjmfmejaafjjkoeejjpdfkdkpc, ogaclpidpghafcnbchgpbigfegdbdikj, opmelhjohnmenjibglddlpmbpbocohck, pbilbjpkfbfbackdcejdmhdfgeldakkn, pcmdfnnipgpilomfclbnjpbdnmbcgjaf, pedokobimilhjemibclahcelgedmkgei, plnlhldekkpgnngfdbdhocnjfplgnekg</p>
<h3 id="c2s">C2s:</h3>
<p><code>hxxp://ledgerwallet[.]xyz/api.php</code>, <code>hxxps://v1[.]ledgers[.]tech</code>, <code>hxxps://coinomibeta[.]online/post/connexion.php</code>, <code>hxxps://completssl[.]com/functions.php</code>, <code>hxxps://completssl[.]com/ssnd_1.php</code>, <code>hxxps://completssl[.]com/ssnd_el.php</code>, <code>hxxps://completssl[.]com/ssnd_ex.php</code>, <code>hxxps://completssl[.]com/ssnd_t.php</code>, <code>hxxps://cxext[.]org/6721e14f0257a64f1f0a9114197d59ba/</code>, <code>hxxps://docs[.]google[.]com/forms/d/1PXmiKeuYFdNS8D1q5yU1Cb7_9TwZQMbMCTl2PfSYhLI/formResponse</code>, <code>hxxps://docs[.]google[.]com/forms/d/e/1FAIpQLSc1DTYAqXYnGTaUH0AIJa-rC2lk7V5nsE6tEdGIKXTKNm36HQ/formResponse</code>, <code>hxxps://docs[.]google[.]com/forms/d/e/1FAIpQLScuQg9Rpct1ahMotYT12xBAt3MmcubQg-duV1a0BZ_vo1Tj4g/formResponse</code>, <code>hxxps://ledger[.]productions/api_v1/</code>, <code>hxxps://mecxanalytic[.]co/api_keystore.php</code>, <code>hxxps://mecxanalytic[.]co/api_mnemonic.php</code>, <code>hxxps://mecxanalytic[.]co/api_private.php</code>, <code>hxxps://trxsecuredapi[.]co/api_ledger.php</code>, <code>hxxps://usermetrica[.]org/api_v1/</code>, <code>hxxp://vh368451[.]eurodir[.]ru/api/v1/</code>, <code>hxxps://walletbalance[.]org/api_v1/</code>, <code>ws://analytics-server296[.]xyz:4367</code></p>
<hr>
<p>Chrome extensions are increasingly vulnerable to credential harvesting phishing and executive impersonation attacks. PhishFort offers essential services to detect and take down phishing websites, fraudulent mobile apps, and fake social media profiles that compromise users&rsquo; trust. By identifying these malicious extensions and eliminating threats, PhishFort upholds business and customer security, protecting brands from the reputation-damaging impact of compromised Chrome extensions. Learn more about common phishing tactics on social media in <a href="/most-common-social-media-phishing-attacks">Most Common Social Media Phishing Attacks</a>
, and <a href="/social-media-phishing-scams/">How Cybercriminals Exploit Trust on Social Media Platforms</a>
, or read about hidden attack vectors in <a href="/cryptocurrency-scams/">12 Common Attack Vectors That You Probably Didn&rsquo;t Know</a>
.</p>
<p>A big thank you to <a href="https://twitter.com/sniko_" target="_blank" rel="noopener">Harry Denley</a>
 who contributed significant time and work to putting this research together.</p>
]]></content:encoded><category>Research</category><category>phishing</category><category>chrome-extension</category><category>crypto</category><category>browser-security</category><category>nighthawk</category></item></channel></rss>