Malicious Code Detected in fsworker Package - Security Alert

fsworker Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-21018: Malicious code in fsworker (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 fsworker package is an npm module designed to facilitate file system operations in Node.js applications. It provides various functionalities to manage file and directory interactions efficiently. However, recent investigations have revealed that this package contains malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The fsworker package has been identified to contain malicious code that could compromise the security of applications using it. This vulnerability originated from the package's codebase, which was found to be intentionally designed to execute harmful operations. The ramifications of this vulnerability include unauthorized access to sensitive data, potential data corruption, and exploitation of the host system. Developers using this package are urged to take immediate action to mitigate risks associated with this malicious code.

How To Fix

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

npm uninstall fsworker

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, it is advisable to remove the fsworker package from your project until a secure version is released. You can do this by executing the following command: npm uninstall fsworker. Consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The fsworker package has been flagged for containing malicious code, which poses serious security threats to applications. It is essential for developers to take immediate action by updating or removing the package and to monitor their projects for vulnerabilities using tools like Vulert.

See every vulnerability recorded for fsworker →

Share this vulnerability

FAQ

The fsworker package is an npm module used for file system operations in Node.js applications.

The malicious code was discovered through security audits conducted by Amazon Inspector, which identified vulnerabilities in the package.

Using the fsworker package can lead to unauthorized access to sensitive data, data corruption, and exploitation of the host system.

You can use Vulert to monitor and alert in real-time for open-source vulnerabilities in your software. It requires only the package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall fsworker

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