Malicious Code Injection in hungry_tern_z3n: npm Package Vulnerability

hungry_tern_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-94887: Malicious code in hungry_tern_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 'hungry_tern_z3n' package 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 through automated publishing scripts, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability in 'hungry_tern_z3n' involves the presence of malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is part of a broader scheme to create and publish numerous variants of the package, thereby compromising the integrity of the npm registry and potentially affecting users who unknowingly install these malicious packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which incentivizes such malicious practices.

How To Fix

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

npm uninstall hungry_tern_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 workaround, you can avoid using the 'hungry_tern_z3n' package altogether. If you have already installed it, you can uninstall it using the command: npm uninstall hungry_tern_z3n.

Conclusion

The 'hungry_tern_z3n' package poses a significant risk due to its malicious code that manipulates package metadata and floods the npm registry. It is crucial for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities in their dependencies.

See every vulnerability recorded for hungry_tern_z3n →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

If your application uses the 'hungry_tern_z3n' package, it may inadvertently publish malicious variants and compromise the integrity of your project.

You should uninstall the 'hungry_tern_z3n' package immediately to mitigate any risks associated with its malicious behavior.

Yes, you can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without requiring any signup.

How To Fix

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

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