Malicious Code Detected in old-hd-keyring Package - Security Alert

old-hd-keyring Updated 01 Dec 2025

Summary

01/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191501: Malicious code in old-hd-keyring (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 old-hd-keyring package is a Node.js library used for managing keyrings in applications. It provides developers with a simple interface for storing and retrieving sensitive information securely. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the old-hd-keyring package, which was identified by Amazon Inspector. This code can potentially compromise the security of applications using the package, leading to unauthorized access to sensitive data or system manipulation. The malicious nature of this code makes it imperative for developers to take immediate action to mitigate any risks associated with its use.

How To Fix

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

npm uninstall old-hd-keyring

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, you can remove the old-hd-keyring package from your project until a secure version is available. Use the following command to uninstall it: npm uninstall old-hd-keyring.

Conclusion

The discovery of malicious code in the old-hd-keyring package highlights the importance of regularly monitoring and updating dependencies in software projects. Developers are urged to take immediate action to secure their applications by updating or removing the affected package.

See every vulnerability recorded for old-hd-keyring →

Share this vulnerability

FAQ

The old-hd-keyring package is a Node.js library designed for managing keyrings, allowing developers to securely store and retrieve sensitive information.

The malicious code was detected by Amazon Inspector, a security service that identifies vulnerabilities in software packages.

Using the compromised old-hd-keyring package can lead to unauthorized access to sensitive data, potential data breaches, and system vulnerabilities.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check your application for vulnerabilities without signing up at the Vulert playground.

If you cannot update the package immediately, consider removing it from your project as a temporary measure to mitigate risks until a secure version is available.

How To Fix

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

npm uninstall old-hd-keyring

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