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

node-env-resolver-nextjsnpm

Advisory published Updated

node-env-resolver-nextjs is a confirmed malicious npm package (MAL-2026-5265) that steals credentials and exfiltrates sensitive data (malicious version 7.4.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in node-env-resolver-nextjs (npm)

MAL-2026-5265
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall node-env-resolver-nextjs

What this malware does

The package was found to contain malicious code or consuming dependency that contains malicious code

The Miasma malware is a self-propagating worm that spreads across the npm registry by abusing weaponized binding.gyp files to achieve execution during package installation, bypassing security tools that only inspect package lifecycle scripts. Upon execution, the malware attempts to exfiltrate credentials and OIDC tokens for various cloud and registry services, and propagates by compromising other packages managed by the stolen accounts or committing backdoor files to GitHub repositories.

Malicious versions

1 flagged
7.4.2

Indicators of compromise (SHA-256)

a6c7977dbc054cdb7fe56da0d2fbd26e2a6fed695deb4263ccbf4adfedd86acb
556430b576f70c519fdab92137b48779f60f127f48ff5bdef0bcef838e24131b

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for node-env-resolver-nextjs (version 7.4.2).

  2. If you installed it — respond

    node-env-resolver-nextjs 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 node-env-resolver-nextjs 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. node-env-resolver-nextjs on npm has been identified as a malicious package (version 7.4.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-008780

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks node-env-resolver-nextjs-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

node-env-resolver-nextjs (npm) malicious package — MAL-2026-5265 | O3 Security