Critical Malicious Code Vulnerability in rimarf Package

rimarf Updated 20 Feb 2026

Summary

20/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-968: Malicious code in rimarf (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 rimarf package is an npm module designed for specific functionalities within JavaScript applications. It is commonly used for various tasks, but its security has been compromised due to the presence of malicious code. This vulnerability poses a significant risk to any system utilizing this package, as it can lead to unauthorized access and control over the affected systems.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the rimarf package. This code can fully compromise any computer that has the package installed, allowing attackers to gain control and access sensitive information such as secrets and keys. The ramifications of this vulnerability are severe, as it can lead to data breaches and unauthorized actions performed on behalf of the compromised system. Users are advised to treat any system with this package as fully compromised.

How To Fix

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

npm uninstall rimarf

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. The only recommended action is to remove the rimarf package entirely from your system.

Conclusion

The rimarf package has been identified as containing malicious code that poses a significant risk to systems using it. Immediate removal of the package and rotation of sensitive information is essential to mitigate the threat. Users are encouraged to utilize tools like Vulert for ongoing monitoring of their dependencies.

See every vulnerability recorded for rimarf →

Share this vulnerability

FAQ

You should remove the rimarf package immediately and rotate any sensitive information stored on the affected system.

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.

Keeping rimarf installed can lead to unauthorized access, data breaches, and potential control over your system by malicious actors.

Currently, there is no patch available. The best course of action is to remove the package entirely.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert and keep your packages updated.

How To Fix

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

npm uninstall rimarf

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