Malicious Code Detected in fsrazor Package - Security Alert

fsrazor Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-21014: Malicious code in fsrazor (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 fsrazor package is a Node.js library designed for file system manipulation and management. It provides various functionalities for developers to interact with the file system efficiently. However, recent findings have revealed that this package contains malicious code, posing a significant security risk to users and their applications.

Vulnerability Detail

The vulnerability in the fsrazor package originates from the inclusion of malicious code that can compromise the security of applications utilizing this library. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. Users of the fsrazor package are at risk of exploitation, making it crucial to address this issue promptly.

How To Fix

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

npm uninstall fsrazor

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 fsrazor package from their project until a secure version is confirmed. This can be achieved by executing the command: 'npm uninstall fsrazor'. Consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the fsrazor package highlights the importance of maintaining secure coding practices and regularly updating dependencies. Users are advised to take immediate action by updating or removing the package to protect their applications from potential threats.

See every vulnerability recorded for fsrazor →

Share this vulnerability

FAQ

fsrazor is a Node.js library for file system manipulation, allowing developers to manage files and directories efficiently.

The malicious code can lead to unauthorized access and potential data breaches, compromising the security of applications using this 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 fsrazor package and using alternative libraries until a secure version is available.

Utilizing tools like Vulert can help you monitor your dependencies for vulnerabilities in real-time, ensuring you are alerted to any security issues.

How To Fix

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

npm uninstall fsrazor

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