Critical Malicious Code Vulnerability in iruchache Package

iruchache Updated 20 Feb 2026

Summary

20/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-962: Malicious code in iruchache (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 iruchache package is a Node.js library available via npm, designed for caching purposes in web applications. It is utilized to enhance performance by storing frequently accessed data. However, this package has been compromised, embedding malicious code that poses significant security risks to any system using it.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the iruchache package. Any system that has this package installed is considered fully compromised, allowing unauthorized access to sensitive information such as secrets and keys. The malicious code can lead to severe ramifications, including data breaches and loss of control over the affected system. Users are advised to treat any computer running this package as potentially compromised.

How To Fix

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

npm uninstall iruchache

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 uninstall the iruchache package and secure the system.

Conclusion

The iruchache package has been identified as containing malicious code, posing significant risks to any system using it. Immediate action is required to uninstall the package and secure sensitive information. Users are encouraged to monitor their systems and utilize tools like Vulert for real-time vulnerability alerts.

See every vulnerability recorded for iruchache →

Share this vulnerability

FAQ

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

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

Failing to address this vulnerability can lead to unauthorized access to sensitive data, potential data breaches, and loss of control over your system.

While removing the package is essential, you should also rotate all secrets and keys to prevent unauthorized access.

If a patched version is released, updating the package may resolve the issue, but immediate removal is still necessary due to the potential for existing compromises.

How To Fix

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

npm uninstall iruchache

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