Malicious Code Injection in wet_heron_z3n: A Threat to npm Packages

wet_heron_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-97352: Malicious code in wet_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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The wet_heron_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package, like many others in this campaign, is designed to manipulate the npm registry by generating and publishing derivative packages with randomized names. Its primary function is to inflate developer reputation scores for token rewards, but this functionality comes with significant security risks.

Vulnerability Detail

The vulnerability in wet_heron_z3n originates from its malicious payload, which 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 integrity of other packages. The malicious code can affect developers by damaging their reputation and introducing security risks into their applications.

How To Fix

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

npm uninstall wet_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 wet_heron_z3n package from your project by executing the command: npm uninstall wet_heron_z3n. This will prevent any malicious code from executing in your application until a fix is applied.

Conclusion

The wet_heron_z3n package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is essential for developers to take immediate action by updating or removing the package to protect their applications from potential threats.

See every vulnerability recorded for wet_heron_z3n →

Share this vulnerability

FAQ

wet_heron_z3n is an npm package associated with the tea.xyz token reward campaign, designed to manipulate npm registry entries.

The vulnerability can lead to the introduction of malicious code, which may compromise your application's integrity and security.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

If an immediate update is not possible, consider uninstalling the package as a temporary measure to mitigate risks.

Detailed information can be found in the vulnerability report on the GitHub repository for malicious packages.

How To Fix

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

npm uninstall wet_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