Malicious Code Injection in rolling_heron_z3n: A Threat to npm Ecosystem

rolling_heron_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96395: Malicious code in rolling_heron_z3n (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package 'rolling_heron_z3n' is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores for token rewards, making them a significant threat to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in 'rolling_heron_z3n' originates from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the security of applications that depend on these packages. The malicious payload can also allow unauthorized access to sensitive information and disrupt the normal functioning of applications using this package.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall rolling_heron_z3n

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, you can remove the 'rolling_heron_z3n' package from your project by executing: 'npm uninstall rolling_heron_z3n'. This will help mitigate the risk until a secure version is available.

Conclusion

The 'rolling_heron_z3n' package poses a significant threat due to its malicious code designed to exploit the npm ecosystem. It is crucial to take immediate action by updating or removing the package to safeguard your applications. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for rolling_heron_z3n →

Share this vulnerability

FAQ

The vulnerability involves malicious code that modifies package.json files and floods the npm registry with derivative packages.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application against the vulnerability using the Vulert playground at Vulert Scanner.

Using this package can lead to unauthorized access to sensitive data, disruption of application functionality, and pollution of the npm registry.

Check the npm registry for any updated versions of 'rolling_heron_z3n' that address this vulnerability.

As a temporary measure, uninstall the package using 'npm uninstall rolling_heron_z3n' to mitigate risks.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall rolling_heron_z3n

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback