NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

normal-storenpm

Advisory published Updated

normal-store is a confirmed malicious npm package (MAL-2025-191135) that steals credentials and exfiltrates sensitive data (malicious versions 1.3.1, 1.3.2, 1.3.3…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in normal-store (npm)

MAL-2025-191135
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall normal-store

What this malware does

The package normal-store was found to contain malicious code.

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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

4 flagged
1.3.11.3.21.3.31.3.4

Indicators of compromise (SHA-256)

1e1d6a2537e74912ec3831bf85e49e8ba908fc28838ec60c07f7218717ba36ae
6933adf61af3af4e10dde8860c7b535c3d2c0c8803bd28b099dc9e8cc27a0b8e
3f3cc821206cbfa969e8f4e3472a09caf43736b8e70d4ec80ed20931b64406b8
5cb1d11f446bdbfb6cb772b6de422e660279e89994a66b2e218adffd831e6e92

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for normal-store (4 malicious versions).

  2. If you installed it — respond

    normal-store is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If normal-store 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. normal-store on npm has been identified as a malicious package (versions 1.3.1, 1.3.2, 1.3.3, 1.3.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-h55v-443q-qjm4RLMA-2025-06437

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks normal-store-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

normal-store (npm) malicious package — MAL-2025-191135 | O3 Security