Malicious Code Detected in fs Package - Security Alert

fs Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-21003: Malicious code in fs (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The fs package is a widely used Node.js module that provides an API for interacting with the file system. It allows developers to perform operations such as reading and writing files, managing directories, and handling file streams. This package is integral to many applications, making its security paramount. However, recent findings have revealed that the fs package contains malicious code, posing a significant risk to users and their applications.

Vulnerability Detail

The vulnerability in the fs package stems from the inclusion of malicious code that can compromise the integrity of applications utilizing this package. This code can lead to unauthorized access, data breaches, and potential exploitation of the affected systems. The malicious code was introduced in version 0.0.1-security and affects all subsequent versions. Users of the fs package are at risk of severe ramifications, including data loss and security breaches.

How To Fix

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

npm uninstall fs

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, users can remove the fs package from their project until a secure version is available. This can be done by executing the following command: npm uninstall fs. However, this may affect the functionality of applications relying on the fs package.

Conclusion

The fs package has been identified as containing malicious code, posing a significant security risk to applications that utilize it. Users are strongly advised to update to the latest version or remove the package until a secure version is available. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for fs →

Share this vulnerability

FAQ

The fs package is a Node.js module that provides an API for file system operations, such as reading and writing files.

The malicious code can lead to unauthorized access and potential exploitation of systems using the fs package.

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

As a temporary measure, consider uninstalling the fs package to mitigate risks until a secure version is available.

The vulnerability was discovered by Amazon Inspector, a security assessment service.

How To Fix

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

npm uninstall fs

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