Image downloader extensions reviewed: the Save Image as Type hijack & safer picks
Save Image as Type ran hidden affiliate fraud on 1M+ browsers for months after a quiet sale, Featured the whole time. What image downloader extensions need.

Right-click, save, pick a file type, done. Image downloader extensions are among the most boring utilities in the Chrome Web Store — which is exactly what made Save Image as Type such a good hiding place.
In March 2026, Chrome disabled the extension — over a million users — as malware. XDA Developers' teardown traced what happened: sometime between November 13 and 29, 2025, the listing changed owners, and an update turned its content script into an affiliate-fraud engine that loaded affiliate links in invisible frames and planted their cookies in your browser. Google took about four months after that sale to remove it.
And for all of those months, the Chrome Web Store wasn't just hosting Save Image as Type. Per XDA, the listing kept its "Featured" badge until the day it was removed.
The uncomfortable part: there was nothing to see. Broad host access is a normal profile for an image converter, and the badge was shiny. The fraud lived in the code and the update channel — the two places an install dialog never shows you. Here's what happened, what this category genuinely needs, and how to save images without handing a stranger a script that runs everywhere.
Quick verdict
- It wasn't born malicious. Per XDA, the May 2023 build (v1.2.3) was completely clean, and the late-2024 build (v1.4.6) added a page script,
inject.js, for legitimate image conversion. - It turned after a quiet sale. Between November 13 and 29, 2025, the Chrome Web Store owner changed, and v1.7.2 repurposed that same script to load server-supplied affiliate URLs in hidden iframes.
- The payload was affiliate fraud, not credential theft. XDA recovered 578 affiliate redirect URLs from one browser alone, aimed at retailers including Amazon, Adidas and Shein.
- A permission check would not have caught this. Broad host access is standard for image converters. What changed was the owner and the code, after install.
- If it's still in your toolbar, remove it. Chrome already disabled it with a "contains malware" notice.
- For casual saving, skip extensions entirely. Right-click save, drag-and-drop and "save complete page" cover most needs with zero permissions. For batch work, trust only code that's public and a developer with a face.
What an image downloader extension actually does
The category comes in two shapes, and their permission asks differ.
Shape one: the right-click helper. The promise: save the image under your cursor with the name you choose, instead of whatever the browser picks. For that alone, the honest toolkit is two modest APIs: contextMenus to add the right-click entry, and downloads to write the file under your chosen name. I walked through what downloads really allows in my breakdown of the downloads permission.
Converting the format — Save Image as Type's whole selling point, turning a WebP into a PNG or JPG — needs more. The extension has to fetch the image bytes and re-encode them, which means reaching into the page and, for images hosted elsewhere, cross-origin access. That's why even the clean 2023 build of Save Image as Type declared offscreen, scripting and activeTab alongside contextMenus and downloads, plus host access to <all_urls>. Nothing about that profile was a red flag. That's the problem.
Shape two: the batch downloader. These scan a page — or every open tab — for images, let you filter by size or type, and download dozens at once. Scanning pages means content scripts, and content scripts that work everywhere mean host permissions for everywhere. That's how batch tools end up asking for <all_urls>, the broadest grant in the extension model. It's defensible for the feature, but install one consciously: here's what that grant really hands over.
The line I draw for the whole category: an image saver's job is looking at pictures and writing files to disk. Nothing in that job requires your browsing history, your cookies, your clipboard, or a server telling the extension what to do next.
The timeline
Piecing XDA's version-by-version analysis together with 9to5Google's and gHacks' reporting:
- October 2024 — researcher Wladimir Palant documents a network of bought-up Chrome extensions doing affiliate fraud and user tracking, which he links to Karma Shopping. Save Image as Type isn't among them yet.
- May 2023 → late 2024 — v1.2.3 is clean: no content script, no page injection. v1.4.6 adds
inject.json every HTTP and HTTPS page plus a hidden iframe, but per XDA both are legitimate — the iframe loads the extension's own conversion page. - February 2025 — Microsoft removes a Save Image as Type listing from the Edge add-ons store. Per XDA, that Edge version was clean and came from a different publisher, so it wasn't a response to the later fraud.
- November 13–29, 2025 — the Chrome Web Store owner changes from Image4Tools to "laurenbridgecool," and v1.7.2 repurposes
inject.jsfor page injection. Its affiliate URLs all route through karmanow, the affiliate service tied to the Karma network Palant described. - December 12, 2025 → February 10, 2026 — the payload fires in XDA's own browser, heaviest over the Christmas and New Year period.
- March 16, 2026 — Chrome disables the extension for users with a "contains malware" notice; a Chrome Help Community thread opened that morning records users asking whether it was a false positive.
So the fraud itself ran for about four months, not years. What makes it notable is the context: Palant had published the Karma playbook — buy a trusted extension, inject monetization — more than a year earlier, and a Featured, million-user listing still changed hands and ran that exact playbook for months. Google hasn't said why. I found no public statement from either the original developer or the later owner.
How a "boring" utility monetized a million browsers
The mechanism is cookie stuffing, and it's elegantly grubby. Per XDA's teardown, v1.7.2's inject.js fetched a list of affiliate redirect URLs from a remote server, then loaded each one in a full-screen iframe set to invisible. Each load planted that merchant's affiliate cookie in your browser. As 9to5Google described it, the extension used that server-supplied list "to load in corresponding affiliate codes, essentially stealing commissions from the original clicked link."
Translated: later, if you buy from one of those merchants — by any route, a blog link, a friend's message, typing the address — the stuffed cookie can claim the sale. The commission goes to the operator, displacing a genuine referrer or billing the merchant for a referral that never happened.
It was also built not to be noticed. XDA found the payload stayed dormant until you'd saved at least 10 images with the extension, fired only on image-heavy pages, ran at most once an hour, and phoned home at most every 36 hours.
Nobody's password moves. No wallet drains. That's precisely why this kind of fraud survives: affiliate injection trips none of the classic malware alarms — no destructive payload, no credential theft, nothing for an antivirus engine to recognize. When an AI sidebar extension got caught opening an affiliate tab on every update, the economics were the same: fraud that pays quietly instead of breaking loudly. And Save Image as Type is a single-listing cousin of the ShadyPanda campaign, which industrialized affiliate fraud across 145 extensions before escalating into keylogging spyware.
The direct cost to you is small. The real cost is what the story proves: a Featured, million-user utility can be resold, repurposed and monetized against its users for months, and every check the store surfaces — permissions, badge — stays green the whole time.
What a permission check can't see
If you did everything right before installing Save Image as Type — read the warnings, checked the reviews, saw the Featured badge — you'd still have gotten it wrong. Three things the install dialog never shows you:
- Ownership. Chrome doesn't notify users when an extension is sold. The developer name on the listing can change quietly, and with it every assumption you made. That blind spot is the subject of my piece on ownership-transfer supply chain attacks after QuickLens was weaponized the same way.
- Updates. The package you vetted at install time isn't the package running next month. v1.4.6 and v1.7.2 shared a file name, a hidden iframe and a permission set; only the code inside changed.
- The soft-malware gap. Affiliate fraud doesn't look like malware to most scanners — which is how a Featured listing can run it for months before anyone pulls it.
So what can you check? Developer continuity — does the listing still show the publisher you installed from? A privacy-practices tab that matches the feature set? And a fresh scan of the live package every so often, which is what the Extenshi catalog does: search image downloader extensions and each report shows the permissions from the package that's live now. Same caveat as always: a report describes today's build. It can't tell you what last year's build did, and it can't see what an operator's servers send back.
The permission profile: legitimate vs suspicious
When I evaluate an image tool, this is the table I run:
| Permission / behavior | Legitimate for an image saver? |
|---|---|
contextMenus |
✓ The right-click entry point |
downloads |
✓ Writing the file to disk |
offscreen, activeTab, scripting |
✓ Format conversion and reading the current page |
<all_urls> host access |
⚠ Common for converters and batch downloaders — accept only if the tool genuinely needs every page |
history, cookies, clipboardRead |
✗ No image feature needs these |
| Remote configuration (extension fetches instructions or URL lists from a server) | ✗ The post-install weaponization channel |
| Privacy tab disclosing "browsing activity" or "market analytics" sales | ⚠ Legal, disclosed data selling — read it before you install |
The two ⚠ rows are where judgment lives. <all_urls> isn't disqualifying for a converter or batch tool, and a data-sale disclosure isn't disqualifying for a free one — but both deserve a conscious yes, not a click-through. Chrome's permission warnings list is the decoder ring for what each install warning actually grants.
Safer ways to save images
My honest ranking for this category:
- Right-click → "Save image as." Covers single images. Zero permissions, zero vendor.
- Drag the image onto your desktop or into a folder. Faster than the context menu once it's muscle memory.
- Ctrl+S (Cmd+S on Mac) → "Webpage, Complete" when you need every image on a page — it saves the full asset set into a local folder.
- The DevTools trick for stubborn images: F12 → Network tab → filter by Img → reload. Every image the page requested shows up, including CSS backgrounds you can't right-click — open one in a new tab and save it.
None of these converts formats: a WebP stays a WebP. If you need a JPG or PNG, open the saved file in an image editor or your operating system's built-in viewer and export it — one extra step, zero browser permissions.
For regular batch work — "download every product photo on this page" — an extension genuinely earns its place, and that's where the checklist above applies. I'm deliberately not blessing specific batch downloaders by name from here: this category's own history is the reason, and today's clean tool is one quiet acquisition away from tomorrow's inject.js. Pick one whose code is public enough for researchers to audit and whose developer has a findable track record — then check the extension by its store URL before it goes in, not after.
Final recommendation
- Had Save Image as Type installed: remove it. Chrome already disabled it — you're carrying dead weight with a documented history.
- Casual image saving: use the built-ins. Right-click, drag-and-drop, complete-page save. Zero permissions beats any extension.
- Batch downloading: accept
<all_urls>only with open eyes, prefer public code and named developers, and re-scan periodically — not just at install time. - Any extension you've kept for years: check whether the developer name still matches the one you installed from. Ownership transfers are silent, and this category has now shown what happens next.
If you want a second opinion on everything already in your browser, scan the extensions you installed from a store with Guard — it checks your installed list against the Extenshi catalog and flags the ones worth a second look.
Scan the extensions you installed from a store with Guard →
Sources
- XDA Developers — "Google kept featuring this Chrome extension for months after it turned malicious" (March 16, 2026): https://www.xda-developers.com/google-featuring-chrome-extension-months-malicious/
- 9to5Google — "Your favorite image-saving Chrome extension was scraping your data for cash" (March 16, 2026): https://9to5google.com/2026/03/16/image-saving-chrome-extension-removed-as-malware/
- gHacks — "Chrome Extension 'Save Image as Type' Was Hijacked, Putting Over 1 Million Users at Risk" (March 19, 2026): https://www.ghacks.net/2026/03/19/chrome-extension-save-image-as-type-was-hijacked-putting-over-1-million-users-at-risk/
- Wladimir Palant — "The Karma connection in Chrome Web Store" (October 30, 2024): https://palant.info/2024/10/30/the-karma-connection-in-chrome-web-store/
- Google Chrome Help Community — users reporting Chrome's malware disable notice for "Save Image as Type" (March 16, 2026): https://support.google.com/chrome/thread/417557178
- Chrome for Developers —
contextMenusAPI reference: https://developer.chrome.com/docs/extensions/reference/api/contextMenus - Chrome for Developers —
downloadsAPI reference: https://developer.chrome.com/docs/extensions/reference/api/downloads - Chrome for Developers — permission warnings list: https://developer.chrome.com/docs/extensions/reference/permissions-list
This article is based on publicly available security research and news reporting. Extenshi does not independently verify all claims made by third-party researchers. References to specific companies or products reflect the findings of cited sources and do not constitute accusations of intentional wrongdoing. If you believe any information is inaccurate, please contact us at [email protected].
Related Articles

Extension ownership transfers: how to protect yourself when your add-on changes hands
QuickLens got hijacked via an extension ownership transfer to push ClickFix and crypto-stealing malware. Here's how to check your own add-ons are still safe.

Malware that arrives in the update, not the install: how to check your extensions
A Chrome extension pulled in January is back — and shipped its payload two weeks after a clean release. How update-time malware works, and how to check yours.

Screenshot extensions reviewed: the permissions they really need, the ShotBird hijack & safer alternatives
Screenshot extensions can read every page they capture. Here's the permission breakdown, what the ShotBird hijack revealed, and how to grab screens safely.

The `downloads` permission explained: what extensions can really do with your files
The downloads permission lets an extension read every file you've downloaded, write new ones, and hide the download UI. Here's what it allows and how to check.