Malicious Code Detected in dhkey Package - Security Alert

dhkey Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18425: Malicious code in dhkey (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 dhkey package is a Node.js library used for cryptographic key generation and management. It is designed to facilitate secure communication in applications. However, it has been identified to contain malicious code, posing significant security risks to users and applications that depend on it.

Vulnerability Detail

The vulnerability in the dhkey package stems from the inclusion of malicious code that can compromise the security of applications utilizing this library. This code may allow unauthorized access to sensitive data or enable other malicious activities. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to take immediate action to mitigate potential risks.

How To Fix

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

npm uninstall dhkey

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 dhkey package from your project until a secure version is released. You can do this by running: npm uninstall dhkey. Additionally, review your application for any dependencies that may rely on this package and assess their security.

Conclusion

The discovery of malicious code in the dhkey package poses a serious threat to applications using this library. Immediate action is required to mitigate risks, including updating or removing the package. Users are encouraged to stay informed about updates and utilize tools like Vulert for ongoing vulnerability monitoring.

See every vulnerability recorded for dhkey →

Share this vulnerability

FAQ

The dhkey package is a Node.js library used for cryptographic key generation and management.

The malicious code can compromise application security, potentially allowing unauthorized access to sensitive data.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Check your application against the vulnerability using the Vulert playground at Vulert Scanner.

Currently, there is no patched version available. Users should monitor the package repository for updates.

If removal is not possible, ensure to implement additional security measures and monitor your application closely for any suspicious activity.

Related vulnerabilities

Recent vulnerabilities recorded for dhkey.

How To Fix

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

npm uninstall dhkey

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