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

next-styled-nprogressnpm

Advisory published Updated

next-styled-nprogress is a confirmed malicious npm package (MAL-2025-190981) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.4, 1.0.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in next-styled-nprogress (npm)

MAL-2025-190981
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall next-styled-nprogress

What this malware does

The package next-styled-nprogress 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

2 flagged
1.0.41.0.5

Indicators of compromise (SHA-256)

7e26fab049a1c502938cf70ba18bda3f50a054d340a699fc95c43a7dac7da8c4
73288a3937c0b6e5fe20c011142795ae2f436252a77e2ab6b24dabcdb9ab7dd5
f2beb88f76a61f7df77568df38e7f7e58993cf7d371b8578f84c70aeecbc474a

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for next-styled-nprogress (2 malicious versions).

  2. If you installed it — respond

    next-styled-nprogress 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 next-styled-nprogress 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. next-styled-nprogress on npm has been identified as a malicious package (versions 1.0.4, 1.0.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-8m3r-xr49-5g64

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks next-styled-nprogress-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

next-styled-nprogress (npm) malicious package — MAL-2025-190981 | O3 Security