Malicious Code Detected in fsimage Package - Security Alert

fsimage Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-21012: Malicious code in fsimage (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 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

The fsimage package is an npm library designed for managing file system images. It provides functionalities that allow developers to work with file system structures in a more efficient manner. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The fsimage package has been identified to contain malicious code that could potentially compromise the security of applications using it. This vulnerability originated from the package itself, which was found to be intentionally designed to execute harmful operations. The ramifications of this vulnerability include unauthorized access to sensitive data, data corruption, and potential system breaches. It is crucial for developers to be aware of this issue as it can lead to severe consequences for their applications and users.

How To Fix

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

npm uninstall fsimage

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 fsimage package from your project if it is not critical to your application. You can do this by executing the command: 'npm uninstall fsimage'. This will help prevent any potential exploitation of the malicious code until a secure version is released.

Conclusion

The fsimage package has been flagged for containing malicious code, posing serious security risks to applications. It is essential for developers to take immediate action by updating or removing the package to safeguard their applications and users. Utilizing tools like Vulert can help in monitoring vulnerabilities effectively.

See every vulnerability recorded for fsimage →

Share this vulnerability

FAQ

The fsimage package is an npm library used for managing file system images, allowing developers to interact with file system structures.

The malicious code in fsimage is designed to execute harmful operations that could compromise application security and user data.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup at Vulert Scanner.

If you cannot update the package right away, consider uninstalling it as a temporary measure to prevent potential exploitation.

While specific exploits have not been detailed, the presence of malicious code indicates a high risk of unauthorized access and data compromise.

How To Fix

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

npm uninstall fsimage

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