Malicious Code Injection in stingy_roadrunner_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-109144: Malicious code in stingy_roadrunner_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
Background
The package 'stingy_roadrunner_z3n' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This campaign has been known to flood the npm registry with numerous packages that often contain malicious scripts. These scripts are designed to manipulate package metadata and inflate developer reputation scores, posing a significant risk to developers and users alike.
Vulnerability Detail
The vulnerability in 'stingy_roadrunner_z3n' is characterized by the presence of malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which aims to exploit the npm registry by polluting it with derivative packages. The ramifications include compromised package integrity, potential security risks for users, and a degraded reputation for legitimate developers.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall stingy_roadrunner_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 workaround, you can remove the 'stingy_roadrunner_z3n' package from your project by executing the command: 'npm uninstall stingy_roadrunner_z3n'. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The 'stingy_roadrunner_z3n' package poses a significant threat due to its malicious code that alters package metadata. It is essential for developers to take immediate action by updating or uninstalling the package to safeguard their applications. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.
See every vulnerability recorded for stingy_roadrunner_z3n →
FAQ
The main issue is the presence of malicious code that alters package metadata and repackages it, which can lead to security vulnerabilities.
You can use tools like Vulert to monitor your package-lock.json file for vulnerabilities. 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.
Regularly audit your dependencies, use automated tools for vulnerability detection, and stay updated on security advisories related to your packages.
Ignoring this vulnerability can lead to compromised application security, data breaches, and damage to your project's reputation.
