Malicious Code Injection in noble_frog_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-88860: Malicious code in noble_frog_z3n (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The package noble_frog_z3n is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior can lead to significant pollution of the npm registry, affecting developers and users relying on npm packages for their projects.
Vulnerability Detail
The vulnerability in noble_frog_z3n stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior allows the package to continuously republish variants, which can clutter the npm registry and potentially introduce security risks to users who unknowingly install these packages. The origin of this vulnerability is linked to automated scripts designed to exploit the npm ecosystem for token rewards.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall noble_frog_z3nIf 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 measure, you can avoid using the noble_frog_z3n package and any other related packages that may have been published during the tea.xyz campaign. Regularly audit your dependencies using tools like npm audit to identify and address any vulnerabilities.
Conclusion
The noble_frog_z3n package poses a significant risk to the npm ecosystem due to its malicious behavior of modifying package.json files and republishing variants. It is crucial for developers to remove this package and monitor their dependencies for any vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your software.
See every vulnerability recorded for noble_frog_z3n →
FAQ
The primary risk is that it can clutter the npm registry with maliciously published packages, potentially leading to security vulnerabilities for users who install them.
You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without needing to sign up.
You should uninstall the package immediately using the command npm uninstall noble_frog_z3n and check your project for any other affected packages.
Yes, tools like npm audit and Vulert can help you identify and manage vulnerabilities in your npm packages.
The tea.xyz token reward campaign aimed to incentivize developers to publish packages, but it led to the proliferation of malicious packages like noble_frog_z3n.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
