browser extension

The QuickLens Chrome Extension Supply Chain Attack

Updated 5 Oct 2026 · Incident date 17 Feb 2026

QuickLens, a Chrome extension with about 7,000 users, ran code from an outside server after a malicious update on 17 February 2026.

A new owner bought the extension and used the normal update path. The related extension ShotBird changed owner in the same month.

What happened

The original developer listed QuickLens on ExtensionHub on 11 October 2025. A new owner, support@doodlebuggle.top, took control on 1 February 2026.

  • The update of 17 February 2026 stripped security headers such as X-Frame-Options.
  • It fingerprinted the victim's country, browser and operating system.
  • It polled a remote server every five minutes for JavaScript to run.
  • It ran that code through a hidden 1x1 image element and kept payloads in local storage.
  • ShotBird (about 800 users) later showed fake Chrome update prompts and downloaded googleupdate.exe on Windows.

Affected versions

  • QuickLens - Search Screen with Google Lens, ID kdenlnncndfnhkognokgfpabgkgehodd. Update of 17 February 2026. About 7,000 users. Removed from the Chrome Web Store.
  • ShotBird - Scrolling Screenshots, Tweet Images & Editor, ID gengfhhkjekmlejbhmmopegofnoifnjp. About 800 users. The Hacker News reported it still listed when it published.

The sources do not give version numbers for the malicious builds.

Indicators of compromise

  • Extension IDs: kdenlnncndfnhkognokgfpabgkgehodd and gengfhhkjekmlejbhmmopegofnoifnjp.
  • Owner addresses named in the reports: support@doodlebuggle.top (QuickLens) and loraprice198865@gmail.com (ShotBird).
  • File on Windows machines: googleupdate.exe, downloaded after a fake Chrome update prompt.
  • Behavior: a request to an outside server every five minutes from the extension, and a hidden 1x1 image element in pages.

The sources name no command-server domains, so this page lists none.

How to check

Open chrome://extensions and look for the two names. You can also search the Chrome profile folders for the IDs on macOS.

ls ~/Library/Application\ Support/Google/Chrome/*/Extensions | grep -E "kdenlnncndfnhkognokgfpabgkgehodd|gengfhhkjekmlejbhmmopegofnoifnjp"

On Windows, search under %LOCALAPPDATA%\Google\Chrome\User Data\*\Extensions. Search for googleupdate.exe outside the real Google Update folders.

What to do now

  1. Remove QuickLens and ShotBird from every browser profile.
  2. If anyone ran a PowerShell command from a fake Chrome update page, reinstall that machine.
  3. From a clean device, change passwords and tokens used in the browser while the extension was installed.

Frequently asked questions

How did QuickLens turn malicious?

A new owner took control on 1 February 2026. On 17 February 2026 the owner pushed an update that ran remote JavaScript in pages.

Which extension is linked to QuickLens?

ShotBird, ID gengfhhkjekmlejbhmmopegofnoifnjp. It changed owner in February 2026 and showed fake Chrome update prompts.

Sources

  1. thehackernews.com/2026/03/chrome-extension-turns-malicious-after.html
  2. cyberwarzone.com/2026/03/16/chrome-extensions-turned-malicious-after-ownership-transfer-pushing-code-injection-and-fake-updates/

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