Malicious Code Vulnerability in hydra-node-consent-sdk: A Critical Security Risk

hydra-node-consent-sdk Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1746: Malicious code in hydra-node-consent-sdk (npm). Affects hydra-node-consent-sdk versions 99.99.1 – 99.99.2. 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 hydra-node-consent-sdk is an npm package designed to facilitate user consent management in applications. It provides developers with tools to implement consent flows, manage user preferences, and ensure compliance with data protection regulations. However, this package has recently been identified as containing malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within versions 99.99.1 and 99.99.2 of the hydra-node-consent-sdk package. This code can potentially compromise the integrity of applications using the package, leading to unauthorized access, data breaches, or other malicious activities. The origin of this vulnerability is linked to the package being tampered with, making it essential for developers to be vigilant about the packages they integrate into their projects.

How To Fix

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

npm uninstall hydra-node-consent-sdk

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 measure, consider removing the hydra-node-consent-sdk package from your project until a secure version is confirmed. You can do this by running the command: npm uninstall hydra-node-consent-sdk.

Conclusion

The hydra-node-consent-sdk package has been compromised with malicious code, affecting specific versions. It is imperative for developers to update or remove the package to safeguard their applications. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for hydra-node-consent-sdk →

Share this vulnerability

FAQ

It is an npm package that helps developers manage user consent for data processing in applications.

Versions 99.99.1 and 99.99.2 of the hydra-node-consent-sdk are known to contain malicious code.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.

Consider removing the package from your project as a temporary workaround until a secure version is available.

The vulnerability was identified by ReversingLabs, a cybersecurity firm specializing in threat detection.

How To Fix

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

npm uninstall hydra-node-consent-sdk

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