Malicious Code Injection in tealoveness1 Package: A Threat to npm Users
Summary
MAL-2025-168734: Malicious code in tealoveness1 (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The tealoveness1 package is part of the tea.xyz token reward campaign, which has been known to flood the npm ecosystem. This package is designed to facilitate token rewards through the generation and publication of derivative packages. However, it has been identified as containing malicious scripts that can compromise the integrity of the npm registry and the applications relying on it.
Vulnerability Detail
The vulnerability in the tealoveness1 package stems from its inclusion of autopublish scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants. This behavior can inflate developer reputation scores fraudulently and pollute the npm registry, posing risks to developers and users who may unknowingly install compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealoveness1If 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, it is advisable to audit your npm packages regularly and remove any packages that are not actively maintained or that you do not recognize. You can use the command npm audit to identify vulnerabilities in your dependencies.
Conclusion
The tealoveness1 package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the security of their applications.
See every vulnerability recorded for tealoveness1 →
FAQ
Tealoveness1 is an npm package that is part of a token reward campaign, which has been found to contain malicious code.
The malicious code modifies your package.json file, potentially leading to the installation of compromised packages and pollution of the npm registry.
You should uninstall the tealoveness1 package immediately using npm uninstall tealoveness1.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
