Malicious Code Injection in sweet_termite_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-96910: Malicious code in sweet_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 'sweet_termite_z3n' is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and sharing of code. However, it has been identified as part of a malicious campaign that aims to exploit the npm registry by generating and publishing numerous derivative packages with altered metadata. This behavior not only affects the integrity of the package but also poses a risk to developers who may unknowingly use it.
Vulnerability Detail
The vulnerability in 'sweet_termite_z3n' originates from its association with the tea.xyz token reward campaign, which has been flooding the npm registry with malicious packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, thereby polluting the npm registry. This can lead to a compromised development environment, where developers may inadvertently install malicious packages, risking their applications and data.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall sweet_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 workaround, you can avoid using the 'sweet_termite_z3n' package altogether. If it is already in use, consider replacing it with a reputable alternative that does not exhibit malicious behavior. Additionally, regularly audit your package dependencies using tools like npm audit to identify and mitigate vulnerabilities.
Conclusion
The 'sweet_termite_z3n' package presents a significant risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to be aware of such vulnerabilities and take proactive measures to secure their applications. Regular audits and the use of monitoring tools like Vulert can help maintain a secure development environment.
See every vulnerability recorded for sweet_termite_z3n →
FAQ
The 'sweet_termite_z3n' package is an npm package that has been identified as part of a malicious campaign targeting the npm registry.
This vulnerability can lead to the installation of malicious code, which may compromise your application's integrity and security.
You should remove the 'sweet_termite_z3n' package from your project and replace it with a secure alternative.
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.