Malicious Code Injection in tealoveness16: A Threat to npm Users
Summary
MAL-2025-168741: Malicious code in tealoveness16 (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 tealoveness16 is part of a broader campaign associated with the tea.xyz token reward system. It is designed to manipulate the npm registry by creating and publishing numerous derivative packages with randomized names. This behavior aims to inflate developer reputation scores for rewards, making it a significant concern for developers relying on npm for package management.
Vulnerability Detail
The vulnerability in tealoveness16 stems from its malicious code that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly integrate these malicious packages into their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealoveness16If 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 measure, you can avoid using tealoveness16 and any packages that may have been derived from it. Regularly audit your package-lock.json file to identify and remove any suspicious packages.
Conclusion
The tealoveness16 package poses a significant threat to the npm ecosystem due to its malicious behavior. Developers should take immediate action to remove this package and monitor their dependencies for similar vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your applications.
See every vulnerability recorded for tealoveness16 →
FAQ
Tealoveness16 is an npm package that is part of a malicious campaign aimed at manipulating the npm registry.
The vulnerability can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.
You should uninstall the package immediately using 'npm uninstall tealoveness16' and check for any other affected packages.
You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
