Malicious Code Injection in changing_termite_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-98639: Malicious code in changing_termite_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 'changing_termite_z3n' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing a significant risk to developers and users alike.
Vulnerability Detail
The vulnerability in 'changing_termite_z3n' originates from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to continuously republish variants of the package, polluting the npm registry and potentially leading to the distribution of compromised software. The malicious payload can undermine the integrity of the npm ecosystem and affect developers who unknowingly use these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall changing_termite_z3n
If 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 'changing_termite_z3n' and any other packages that are part of the tea.xyz token reward campaign. Regularly audit your dependencies using tools like npm audit to identify and mitigate risks associated with malicious packages.
Conclusion
The 'changing_termite_z3n' package poses a significant risk due to its malicious code that manipulates package metadata. It is essential for developers to be vigilant about the packages they use and to regularly audit their dependencies to maintain the security of their projects.
See every vulnerability recorded for changing_termite_z3n →
FAQ
'changing_termite_z3n' is an npm package that has been identified as malicious, associated with a campaign to inflate developer reputation scores.
The vulnerability can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.
You should immediately remove the 'changing_termite_z3n' package from your project and audit your dependencies for any other malicious packages.
You can use tools like npm audit or services like Vulert, which monitors your package-lock.json for vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.