Malicious Code Injection in regular_skunk_z3n: npm Package Vulnerability
Summary
MAL-2025-96250: Malicious code in regular_skunk_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 'regular_skunk_z3n' is part of the npm ecosystem and appears to be associated with the tea.xyz token reward campaign. This package is designed to manipulate the npm registry by creating and publishing numerous derivative packages with randomized names, which can inflate developer reputation scores for token rewards. Its functionality is compromised due to the presence of malicious scripts that alter package metadata.
Vulnerability Detail
The vulnerability originates from malicious code embedded within the 'regular_skunk_z3n' package. This code modifies the package.json file to remove private flags, changes version numbers, and generates random package names, leading to the continuous republishing of these variants. The ramifications include potential pollution of the npm registry, unauthorized access to sensitive data, and a negative impact on the reputation of developers using this package. The malicious payload is designed to exploit the npm ecosystem, making it a significant threat.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall regular_skunk_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 'regular_skunk_z3n' package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use the following command to uninstall the package: npm uninstall regular_skunk_z3n.
Conclusion
The 'regular_skunk_z3n' package poses a significant threat due to its malicious code that alters package metadata and pollutes the npm registry. It is essential to remove this package from your projects and monitor your dependencies for vulnerabilities to maintain the security and integrity of your applications.
See every vulnerability recorded for regular_skunk_z3n →
FAQ
It is an npm package that has been identified as malicious, designed to manipulate the npm registry by publishing numerous derivative packages.
The vulnerability can lead to unauthorized modifications in your package.json file, potentially compromising your application's integrity and security.
You should uninstall the 'regular_skunk_z3n' package immediately and monitor your application for any unusual behavior.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check your application for vulnerabilities using the Vulert playground without any signup.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated with the latest security patches for all packages.
