Critical Malicious Code Vulnerability in filerc Package

filerc Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20553: Malicious code in filerc (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The filerc package is a utility for managing file paths in Node.js applications. It provides a simple API for manipulating file paths and is widely used in various projects for its ease of use and efficiency. However, recent findings have revealed that this package contains malicious code, posing a significant security risk to applications that rely on it.

Vulnerability Detail

The vulnerability in the filerc package stems from the inclusion of malicious code that can compromise the integrity of applications using it. This code can lead to unauthorized access, data breaches, or even complete system takeover. The issue was introduced in version 0 and affects all subsequent versions. Users of the package are at risk of exploitation if they do not take immediate action to mitigate this threat.

How To Fix

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

npm uninstall filerc

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, consider removing the filerc package from your project until a secure version is released. You can do this by executing the command: 'npm uninstall filerc'. This will help mitigate the risk while you seek alternative solutions.

Conclusion

The filerc package has been identified as containing malicious code, posing a serious risk to applications that utilize it. Immediate action is required to update or remove the package to safeguard your projects. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities effectively.

See every vulnerability recorded for filerc →

Share this vulnerability

FAQ

The filerc package is used for managing file paths in Node.js applications, providing a simple API for path manipulation.

You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in real-time. By analyzing your package-lock.json file, Vulert can identify if your application is affected.

If an immediate update is not possible, consider removing the package from your project as a temporary measure to reduce risk.

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

Failing to address this vulnerability could lead to unauthorized access, data breaches, or severe security incidents within your application.

How To Fix

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

npm uninstall filerc

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