Critical Malicious Code Vulnerability in custom-redis Package

custom-redis Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17836: Malicious code in custom-redis (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 custom-redis package is a Node.js library designed to provide a simplified interface for interacting with Redis databases. It is commonly used in applications that require fast data storage and retrieval. However, the package has been found to contain malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the custom-redis package. This code can potentially allow unauthorized access to sensitive data, compromise application integrity, and lead to further exploitation of the system. The malicious nature of the code means that any application relying on this package could be at risk of data breaches and other security incidents.

How To Fix

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

npm uninstall custom-redis

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 custom-redis package from your project and replacing it with an alternative Redis client that does not have known vulnerabilities. This can be done by uninstalling the package with the command: npm uninstall custom-redis.

Conclusion

The discovery of malicious code in the custom-redis package highlights the importance of maintaining vigilance in open-source software usage. Users are strongly encouraged to update their dependencies regularly and monitor for vulnerabilities to protect their applications.

See every vulnerability recorded for custom-redis →

Share this vulnerability

FAQ

custom-redis is a Node.js library that provides an interface for interacting with Redis databases, allowing for efficient data storage and retrieval.

The malicious code was identified by security researchers from Amazon Inspector, who reported the findings to the open-source community.

Using the compromised custom-redis package can lead to unauthorized access to sensitive data, application integrity issues, and potential exploitation of the system.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just the package-lock.json file. You can check your application for vulnerabilities using the Vulert playground without any signup.

If immediate updates are not possible, consider removing the custom-redis package and replacing it with a secure alternative until you can safely update.

How To Fix

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

npm uninstall custom-redis

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