Malicious Code Injection in repulsive_tick_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-89933: Malicious code in repulsive_tick_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 'repulsive_tick_z3n' is part of a series of malicious npm packages associated with 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. The malicious nature of this package lies in its ability to modify critical files and republish variants, thereby polluting the npm registry.
Vulnerability Detail
The vulnerability stems from the presence of malicious code within the 'repulsive_tick_z3n' package. This code is designed to alter the package.json file by removing private flags, changing version numbers, and generating random package names. The result is a continuous cycle of republishing variants that can lead to significant pollution of the npm registry, affecting the integrity and reliability of the ecosystem. This vulnerability was identified by Amazon Inspector and is part of a broader trend of malicious packages targeting npm.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall repulsive_tick_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 prevent the installation of this malicious package by using npm's package-lock.json file to monitor dependencies. Ensure that your project does not include 'repulsive_tick_z3n' in its dependencies. You can also use tools like Vulert to monitor for vulnerabilities in real-time.
Conclusion
The 'repulsive_tick_z3n' package poses a serious threat to the npm ecosystem due to its malicious code that alters package files and republishes variants. It is crucial for developers to be vigilant and remove such packages from their projects. Utilizing tools like Vulert can help in monitoring and identifying vulnerabilities effectively.
See every vulnerability recorded for repulsive_tick_z3n →
FAQ
The vulnerability involves malicious code that modifies package.json files and republishes variants to pollute the npm registry.
You can use Vulert to check if your application is affected by this vulnerability without requiring code access or installation.
You should uninstall the package immediately using 'npm uninstall repulsive_tick_z3n' and check your project for any other malicious dependencies.
Yes, Vulert provides real-time monitoring for open-source vulnerabilities using just the package-lock.json file.
The impact includes the potential for significant pollution of the npm registry, which can compromise the integrity and reliability of packages within the ecosystem.
