Which versions of hydra-consent-sdk are malicious?

The following npm versions of hydra-consent-sdk are flagged malicious: 99.99.1. Treat any of these as compromised.

How do I remediate hydra-consent-sdk if I installed it?

Remove hydra-consent-sdk from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed hydra-consent-sdk — how do I know if it already compromised me?

If hydra-consent-sdk was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is hydra-consent-sdk part of a known attack campaign?

Yes — hydra-consent-sdk is associated with the RLMA-2026-01346 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find hydra-consent-sdk across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for hydra-consent-sdk (version 99.99.1).

Malicious package

hydra-consent-sdknpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

hydra-consent-sdk is a confirmed malicious npm package (MAL-2026-1745) that executes malicious code on install (malicious version 99.99.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in hydra-consent-sdk (npm)

MAL-2026-1745

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall hydra-consent-sdk

What this malware does

The package hydra-consent-sdk was found to contain malicious code.

Malicious versions

1 flagged

99.99.1

Indicators of compromise (SHA-256)

b2c6b7dc3671ed2f22d8f2e8326a1a04311b6218e4503da0ddb1d7e271dc7a6f

bb154df736a12683f5680d8355dde8927952f257d80b1355152bcf337754be96

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for hydra-consent-sdk (version 99.99.1).
If you installed it — respond
Remove hydra-consent-sdk from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If hydra-consent-sdk was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. hydra-consent-sdk on npm has been identified as a malicious package (version 99.99.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01346

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks hydra-consent-sdk-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database