Malicious Code Injection in unchanged_snail-appteadev: A Threat to npm Packages
Summary
MAL-2025-110047: Malicious code in unchanged_snail-appteadev (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 'unchanged_snail-appteadev' is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign associated with the tea.xyz token reward system. It is designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names, thus compromising the integrity of the npm registry.
Vulnerability Detail
The vulnerability stems from the presence of malicious code within the unchanged_snail-appteadev package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly integrate these compromised packages into their projects, potentially leading to security breaches and loss of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall unchanged_snail-appteadevIf 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 the malicious package by using npm's 'npm audit' command to identify vulnerabilities in your project. Additionally, consider using a package-lock.json file to lock down the versions of your dependencies, which can help mitigate the risk of inadvertently installing compromised packages.
Conclusion
The unchanged_snail-appteadev package poses a significant threat due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to ensure the security of their applications. By taking proactive measures, developers can protect their projects from potential vulnerabilities.
See every vulnerability recorded for unchanged_snail-appteadev →
FAQ
The malicious code modifies package.json files to remove private flags and generates random package names, leading to the pollution of the npm registry.
You can use tools like Vulert to monitor your package-lock.json file for vulnerabilities. Visit Vulert Scanner to check if your application is affected without any signup.
Using this package can lead to security breaches, as it may introduce malicious code into your project, compromising its integrity and security.
Regularly audit your dependencies using npm audit and consider using tools like Vulert to monitor for vulnerabilities in real-time.
Immediately uninstall the package using 'npm uninstall unchanged_snail-appteadev' and check your project for any other compromised dependencies.
