Critical Malicious Code Vulnerability in rulesdir Package

rulesdir Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-76659: Malicious code in rulesdir (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 rulesdir package is an npm module designed for managing and organizing rules within various applications. It is commonly used in projects that require rule-based processing or configuration. However, this package has been identified as containing malicious code, which poses a significant security risk to any system that has it installed.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the rulesdir package. This code can compromise the entire system, allowing unauthorized access to sensitive information, including secrets and keys. Once installed, the package grants full control of the computer to an external entity, making it imperative for users to act swiftly to mitigate potential damage.

How To Fix

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

npm uninstall rulesdir

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

There are no effective workarounds for this vulnerability, as the only recommended action is to uninstall the malicious package completely.

Conclusion

The discovery of malicious code within the rulesdir package poses a serious threat to users. Immediate action is required to uninstall the package and secure any sensitive information. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for rulesdir →

Share this vulnerability

FAQ

You should uninstall the rulesdir package immediately and rotate any sensitive information stored on the affected system.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.

Leaving the rulesdir package installed can lead to unauthorized access to your system, data breaches, and potential loss of sensitive information.

While removing the package is essential, there is no guarantee that all malicious software will be eliminated. It is advisable to perform a thorough security audit and consider restoring from a clean backup.

To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay informed about security advisories related to the packages you use.

How To Fix

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

npm uninstall rulesdir

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