browser extension

The MEGA Chrome Extension Supply Chain Attack

Updated 5 Oct 2026 · Incident date 4 Sept 2018

MEGA Chrome extension 3.39.4 asked for wider permissions and stole logins and cryptocurrency keys after upload to the Chrome Web Store on 4 September 2018.

MEGA published a clean 3.39.5 about four hours later. Roughly 1.6 million users had the extension installed, according to BleepingComputer.

What happened

At 14:30 UTC on 4 September 2018, an attacker uploaded a trojanized MEGA extension to the Chrome Web Store.

  • MEGA said the attacker used its publisher account on the store.
  • The build asked for a permission to read and change data on the websites you visit.
  • It watched logins on Amazon, Microsoft, GitHub and Google, and on MyEtherWallet, MyMonero and IDEX.
  • SerHack reports that it read wallet addresses and private keys from the MyEtherWallet and MyMonero pages.
  • It sent the data by HTTP POST to megaopac.host, a server in Ukraine.

Google removed the extension at 19:19 UTC. Namecheap blocked the C2 domain at 20:19 UTC, per SerHack. MEGA said that the Firefox extension and the mega.nz website were not affected.

Affected versions

  • 3.39.3: last clean version.
  • 3.39.4: malicious, uploaded 4 September 2018 at 14:30 UTC.
  • 3.39.5: clean version that replaced it.

Indicators of compromise

  • Extension version 3.39.4 in the Chrome extension list.
  • Network traffic to the domain megaopac[.]host.
  • IPv4 address 176.119.1[.]146, hosted in Ukraine, per SerHack.
  • A TLS certificate with the common name la02abd2.justinstalledpanel.com, per SerHack.
  • A permission prompt that asked to read and change all data on the websites you visit.

How to check

Open the extension list in Chrome and read the MEGA version.

chrome://extensions

On a managed network, search the DNS log for the domain. Use the path of your own resolver or proxy. Any hit from 4 September 2018 means a machine ran the bad build.

grep -i "megaopac.host" /var/log/dns/*.log

What to do now

  1. Update MEGA to 3.39.5 or later, or remove the extension.
  2. Change the passwords for Amazon, Microsoft, GitHub, Google and any other account you used while 3.39.4 was active.
  3. Treat cryptocurrency private keys as stolen if you used MyEtherWallet, MyMonero or IDEX in that period. Move the funds to a new wallet.
  4. Block megaopac.host and the IP address above on the network.

Frequently asked questions

Who was at risk?

A user was at risk if the browser auto-updated to 3.39.4 and the user accepted the new permission, or if the user installed 3.39.4 fresh.

Was the MEGA Firefox extension affected?

No. MEGA said the Firefox extension and the mega.nz website were not affected.

Sources

  1. bleepingcomputer.com/news/security/mega-chrome-extension-hacked-to-steal-login-credentials-and-cryptocurrency/
  2. thehackernews.com/2018/09/mega-file-upload-chrome-extension.html
  3. serhack.me/articles/mega-chrome-extension-hacked/

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