Malicious Code Injection in tealoveness32: A Threat to npm Users
Summary
MAL-2025-168759: Malicious code in tealoveness32 (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 tealoveness32 is part of a broader campaign associated with the tea.xyz token reward initiative. It is designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This package, like others in the campaign, is intended to manipulate the npm registry and exploit the system for token rewards.
Vulnerability Detail
The vulnerability in tealoveness32 originates from its malicious code that modifies the package.json file to remove private flags and alter version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to clutter the npm registry. This not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these tainted packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealoveness32If 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 tealoveness32 package and monitor your dependencies for any malicious activity. Additionally, consider using tools like Vulert to scan your package-lock.json for vulnerabilities.
Conclusion
The tealoveness32 package poses a significant threat due to its malicious code designed to manipulate the npm registry. It is crucial for developers to be vigilant and remove any affected packages while utilizing tools like Vulert to ensure their projects remain secure.
See every vulnerability recorded for tealoveness32 →
FAQ
Tealoveness32 is an npm package that is part of a malicious campaign aimed at manipulating the npm registry for token rewards.
The vulnerability can lead to the injection of malicious code into your project, potentially compromising its security and integrity.
You should remove the package immediately and monitor your project for any unusual behavior.
You can use the Vulert playground to check your application for vulnerabilities without needing to sign up.
Vulert is a tool that monitors and alerts you in real-time for open-source vulnerabilities in your software by analyzing your package-lock.json.
