Which versions of sha256-validation are malicious?

The following npm versions of sha256-validation are flagged malicious: 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.5, 1.0.6, 1.0.7, 1.0.8, 1.0.9, 1.1.0, 1.1.1, 1.1.2, 1.1.3, 1.1.4, 1.1.6, 1.1.7, 1.1.8, 1.1.9, 1.2.0, 1.2.1, and 11 more. Treat any of these as compromised.

How do I remediate sha256-validation if I installed it?

Remove sha256-validation 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 sha256-validation — how do I know if it already compromised me?

If sha256-validation 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 sha256-validation part of a known attack campaign?

Yes — sha256-validation is associated with the RLMA-2025-04679, RLUA-2025-05156, RLUA-2026-01562 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 sha256-validation across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for sha256-validation (31 malicious versions).

Malicious package

sha256-validationnpm

Advisory published Aug 14, 2025Updated Mar 19, 2026

sha256-validation is a confirmed malicious npm package (MAL-2025-33045) that executes malicious code on install (malicious versions 1.0.0, 1.0.1, 1.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in sha256-validation (npm)

MAL-2025-33045

Immediate action

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

npm uninstall sha256-validation

What this malware does

The package sha256-validation was found to contain malicious code.

Malicious versions

31 flagged

1.0.01.0.11.0.21.0.31.0.51.0.61.0.71.0.81.0.91.1.01.1.11.1.21.1.31.1.41.1.61.1.71.1.81.1.91.2.01.2.11.2.21.2.31.2.41.2.51.2.61.2.71.2.81.2.91.3.01.3.11.3.2

Indicators of compromise (SHA-256)

9517825d6b96484bf22ed4960d5c022bfe7068fea75cf3c4f3198b69554be838

f2580675d809684737d4ac9e8dc5a843163c20c79ac7c0737d4efd21a66dc16c

bb5ee9d6d98d98b2bdb246de19e07ecb148ef274cd996fbb49e9244db97f1148

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for sha256-validation (31 malicious versions).
If you installed it — respond
Remove sha256-validation 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 sha256-validation 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. sha256-validation on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.5, 1.0.6, 1.0.7, 1.0.8, and 23 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-04679RLUA-2025-05156RLUA-2026-01562

References

getsafety.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks sha256-validation-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