Malicious Code Injection in Trent-Teadev: A Threat to NPM Users
Summary
MAL-2025-109829: Malicious code in trent-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
Trent-Teadev is an NPM package that is part of the tea.xyz token reward campaign. This package is designed to facilitate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. Its functionality is compromised due to the presence of malicious scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability in Trent-Teadev originates from its association with a malicious campaign that floods the NPM registry with derivative packages. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, which pollutes the NPM registry and can potentially harm developers by inflating reputation scores fraudulently.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall trent-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 Trent-Teadev package from your project by executing: npm uninstall trent-teadev. This will prevent any malicious code from executing until a fix is applied.
Conclusion
The Trent-Teadev package is compromised by malicious code that manipulates package metadata and floods the NPM registry with derivative packages. It is crucial for developers to update or remove this package to safeguard their projects from potential exploitation. Utilizing tools like Vulert can aid in monitoring and addressing such vulnerabilities effectively.
See every vulnerability recorded for trent-teadev →
FAQ
The malicious code modifies package.json to remove private flags and generates random package names, leading to the pollution of the NPM registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By checking your package-lock.json file, you can identify if your application is affected.
If you cannot update the package, consider uninstalling it as a temporary measure to mitigate the risk of exploitation.
Yes, tools like Vulert can help monitor your dependencies for vulnerabilities in real-time without requiring code access or installation.
Leaving this vulnerability unaddressed can lead to reputation damage for developers, as well as potential security risks from malicious packages being published and executed.
