Malicious Code Vulnerability in imgbundle Package

imgbundle Updated 30 Sep 2026

Summary

30/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17330: Malicious code in imgbundle (npm). Affects imgbundle versions 1.0.0 – 1.0.1. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

imgbundle is an npm package that is purported to function as an image bundler. It is designed to facilitate the management and bundling of image assets within applications. However, the package has been found to contain malicious code that undermines its intended functionality, posing significant security risks to users and their systems.

Vulnerability Detail

The vulnerability originates from the package's index.js file, which does not perform any legitimate image bundling as advertised. Instead, it executes a top-level Immediately Invoked Function Expression (IIFE) that reads an AES-256-CBC-encrypted file from a sibling dependency, cdn-img-fetch. The file is decrypted using a hardcoded key derived from a specific SHA-256 hash, and the plaintext is written to the filesystem, effectively staging malicious content. This behavior is coordinated with the cdn-img-fetch package, which supplies the encrypted data, making it a coordinated dropper. The README description misleadingly suggests legitimate functionality that is not present in the code, highlighting the deceptive nature of this vulnerability.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall imgbundle

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, you can remove the imgbundle package from your project to prevent the execution of the malicious code. Use the following command to uninstall it: npm uninstall imgbundle. Additionally, consider using alternative packages that provide legitimate image bundling functionality.

Conclusion

The imgbundle package has been identified as containing malicious code that compromises its intended functionality. Users are advised to update or remove the package to mitigate potential security risks. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for imgbundle →

Share this vulnerability

FAQ

The vulnerability involves the presence of malicious code that decrypts and stages attacker-controlled content on the filesystem.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without requiring access to the code or installation.

If you cannot update the package, it is recommended to remove it from your project and look for alternative solutions that do not pose security risks.

Uninstalling imgbundle should not result in data loss, but ensure that you have backups of any important files or configurations before making changes.

Detailed information about the vulnerability can be found in the official security advisory and the package's repository on GitHub.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall imgbundle

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback