Malicious Code Injection in weston-teadev: A Threat to npm Users
Summary
MAL-2025-110818: Malicious code in weston-teadev (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
weston-teadev is an npm package that is part of the tea.xyz token reward campaign. It is designed to facilitate the development and deployment of applications within the npm ecosystem. However, this package has been identified as malicious, containing scripts that manipulate package metadata and publish unauthorized variants, potentially harming developers and users alike.
Vulnerability Detail
The vulnerability in weston-teadev arises from its inclusion in a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts that modify the package.json file, removing private flags, altering version numbers, and generating random package names. This behavior not only pollutes the npm registry but also compromises the integrity of the developer's reputation and can lead to the distribution of malicious software.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall weston-teadevIf 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 remove the weston-teadev package from your project by executing the command: 'npm uninstall weston-teadev'. This will prevent any malicious scripts from executing while you assess the situation.
Conclusion
The weston-teadev package has been identified as malicious, posing significant risks to developers and users within the npm ecosystem. It is essential to take immediate action by updating or removing the package and utilizing tools like Vulert to monitor for vulnerabilities in your applications.
See every vulnerability recorded for weston-teadev →
FAQ
The malicious code modifies package.json to remove private flags and changes version numbers, allowing unauthorized republishing of the package.
You can use Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
Using the compromised package can lead to the distribution of malicious software, loss of developer reputation, and potential security breaches in applications relying on it.
Regularly updating packages, using tools like Vulert for monitoring vulnerabilities, and auditing dependencies can help prevent such issues.
It is crucial to uninstall the package immediately and review your project's dependencies for any other potential vulnerabilities.
