Malicious Code Vulnerability in tealoveness17: npm Package Exploitation
Summary
MAL-2025-168742: Malicious code in tealoveness17 (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 tealoveness17 package is part of a broader campaign associated with the tea.xyz token reward system, which has been known to flood the npm ecosystem with malicious packages. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The functionality of tealoveness17 is compromised, making it a conduit for malicious activities.
Vulnerability Detail
The vulnerability in the tealoveness17 package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of other packages. The malicious payload can inflate developer reputation scores fraudulently, posing risks to the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealoveness17If 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 workaround, you can avoid using the tealoveness17 package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your npm packages to ensure no malicious packages are included.
Conclusion
The tealoveness17 package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial to remove this package from your projects and monitor for similar vulnerabilities to maintain the integrity of your software.
See every vulnerability recorded for tealoveness17 →
FAQ
Tealoveness17 is an npm package that is part of a malicious campaign aimed at manipulating developer reputation scores through the automatic generation and publication of derivative packages.
The vulnerability can lead to the pollution of the npm registry and compromise the integrity of your project's dependencies, potentially introducing security risks.
You should uninstall the tealoveness17 package immediately using 'npm uninstall tealoveness17' and check for any other potentially malicious packages in your project.
You can use tools like Vulert, which monitors and alerts you in real-time for open-source vulnerabilities in your software using just the package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
