browser extension

The Cyberhaven Chrome Extension Supply Chain Attack

Updated 5 Oct 2026 · Incident date 25 Dec 2024

Cyberhaven Chrome extension 24.10.4 sent cookies and sessions to an attacker domain after a phishing attack on 24 December 2024.

Version 24.10.5 is the fixed release. The attack was part of a wider campaign against Chrome extension developers.

What happened

A phishing attack gave an attacker access to the Cyberhaven Chrome Web Store account.

  • The email went to a public support address and led to a malicious OAuth app named "Privacy Policy Extension".
  • Multi-factor authentication was on. It guards sign-in, not OAuth consent.
  • The attacker published 24.10.4 with changed worker.js and content.js files.
  • The code sent signed-in sessions and cookies to cyberhavenext[.]pro.
  • It also targeted Facebook access tokens and account details.

The company found the breach on 24 December and removed the code within one hour. It published 24.10.5 on 26 December 2024.

Affected versions

  • Cyberhaven Chrome extension 24.10.4. The last clean version before it is 24.10.3.
  • Fixed in 24.10.5, released on 26 December 2024.

Indicators of compromise

  • Domain that received stolen data: cyberhavenext[.]pro.
  • Phishing OAuth app name: "Privacy Policy Extension". For other extensions, Sekoia lists "Privacy Policy Extensions".
  • Phishing domains: app.checkpolicy[.]site, chromeforextension[.]com and supportchromestore[.]com.
  • Changed extension files: worker.js and content.js.

How to check

Open chrome://extensions and read the Cyberhaven version. Then search the extension files on disk for the attacker domain. This command works on macOS. On Linux, use ~/.config/google-chrome instead.

grep -rl "cyberhavenext" ~/Library/Application\ Support/Google/Chrome/*/Extensions/ 2>/dev/null

A match means a profile holds the bad build.

What to do now

  1. Update the extension to 24.10.5 or later.
  2. Revoke sessions and change passwords for sites you used in the browser, including Facebook.
  3. Rotate API tokens.
  4. Search DNS and proxy logs for cyberhavenext.pro.

Frequently asked questions

Which Cyberhaven extension version was compromised?

Version 24.10.4. Version 24.10.5 is the fixed release.

How was the Cyberhaven Chrome extension compromised?

A phishing email led an employee to approve a malicious OAuth app. The app gave the attacker access to the Chrome Web Store account.

How do I check if I had the compromised extension?

Check chrome://extensions for version 24.10.4. Search your extension files and network logs for cyberhavenext.pro.

Sources

  1. web.archive.org/web/20260917101941/https://socradar.io/blog/phishing-attack-cyberhaven-chrome-extension/
  2. bleepingcomputer.com/news/security/cybersecurity-firms-chrome-extension-hijacked-to-steal-users-data/
  3. sekoia.com/blog/targeted-supply-chain-attack-against-chrome-browser-extensions

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