Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

sha256-validator-packnpm

sha256-validator-pack is a confirmed malicious npm package (MAL-2025-6199) that executes malicious code on install (malicious versions 1.3.2, 1.3.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in sha256-validator-pack (npm)

MAL-2025-6199
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall sha256-validator-pack

What this malware does

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

2 flagged
1.3.21.3.4

Indicators of compromise (SHA-256)

453f997676ddfb37b97659a39bdc5de8d8c2fc1b070f5feeda72545030850113
b2876c4527bb841cd67a37391e44d65f25acf9c25d3b11d75526ef0bcb7853d0
d2289f742c57fe4a738e4bf75e1d95d854c0af91848987b561d623e711677cef
9e67282c258ce6b69c6a899e1f7aebbc42c668c6834d2bd090afe057529f17c4
022ff14898a09f1d8efe81e2094d95af7f428749cfe9dcaeca3caf760995626c

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for sha256-validator-pack (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sha256-validator-pack across your stack and pipelines.

  2. If you installed it — respond

    Remove sha256-validator-pack 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.

  3. Did it already run?

    If sha256-validator-pack was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

  4. How O3 protects you

    O3 blocks sha256-validator-pack before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. sha256-validator-pack on npm has been identified as a malicious package (versions 1.3.2, 1.3.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-mmp2-hgc3-gh7xRLMA-2025-04024RLUA-2025-04681RLUA-2026-01563

References

Credits

  • ReversingLabs · finder

Detect & block this

O3 blocks sha256-validator-pack-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.

Explore

sha256-validator-pack (npm) malicious package — MAL-2025-6199 | O3 Security