Malicious Code Injection in scrawny_gopher_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-96466: Malicious code in scrawny_gopher_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 'scrawny_gopher_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 not only clutters the npm registry but also poses a significant risk to developers who may unknowingly use these compromised packages.
Vulnerability Detail
The vulnerability in 'scrawny_gopher_z3n' originates from its malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This allows the package to continuously republish variants, polluting the npm registry and potentially leading to security risks for users who install these packages. The malicious payload is designed to exploit the npm ecosystem, making it crucial for developers to be aware of such threats.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall scrawny_gopher_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 avoid using the 'scrawny_gopher_z3n' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities.
Conclusion
The 'scrawny_gopher_z3n' package poses a significant threat to the npm ecosystem due to its malicious code that modifies project files and repopulates the registry with compromised packages. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain security.
See every vulnerability recorded for scrawny_gopher_z3n →
FAQ
The main risk is that it contains malicious code that can modify your project's package.json, leading to potential security vulnerabilities and cluttering the npm registry.
You can use Vulert, which allows you to monitor and alert for open-source vulnerabilities in your software. You can check your application using the Vulert playground at Vulert Scanner without any signup.
You should uninstall the package immediately using 'npm uninstall scrawny_gopher_z3n' and look for alternative packages.
While specific alternatives depend on the functionality you need, it is advisable to search the npm registry for reputable packages that serve similar purposes.
Regularly audit your dependencies using tools like Vulert, keep your packages updated, and be cautious of packages that are part of reward campaigns or have low download counts.
