Critical Malicious Code Vulnerability in iron-image Package

iron-image Updated 10 Mar 2026

Summary

10/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1308: Malicious code in iron-image (npm). Affected versions are not published. 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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The iron-image package is a Node.js library used for image processing and manipulation within web applications. It allows developers to easily handle image uploads, transformations, and optimizations. However, this package has been found to contain malicious code that compromises the security of any system where it is installed, leading to potential data breaches and unauthorized access.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the iron-image package. This code can fully compromise any computer that has the package installed or running, allowing attackers to gain control over the system. As a result, all secrets and keys stored on the affected computer should be considered compromised, necessitating immediate rotation. The malicious nature of the code is classified under CWE-506, indicating that it embeds harmful functionality that can lead to severe security risks.

How To Fix

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

npm uninstall iron-image

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 workaround, if you need to maintain functionality similar to iron-image, consider using alternative image processing libraries that have been vetted for security, such as sharp or jimp. Ensure to review their documentation for proper installation and usage.

Conclusion

The discovery of malicious code within the iron-image package poses a significant threat to users and their systems. Immediate action is required to remove the package and secure any compromised data. Utilizing tools like Vulert can help monitor for vulnerabilities in the future.

See every vulnerability recorded for iron-image →

Share this vulnerability

FAQ

Immediately remove the iron-image package from your project and rotate any sensitive credentials stored on the affected system.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

Failure to address this vulnerability can lead to unauthorized access to sensitive data, potential data breaches, and complete control of your system by malicious actors.

If your system has been compromised, it is essential to perform a full security audit, remove any malicious software, and restore from backups if necessary.

Yes, consider using packages like sharp or jimp for image processing tasks, which are known for their security and performance.

How To Fix

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

npm uninstall iron-image

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