Malicious Code Vulnerability in tealove-boy30: Exploitation of npm Registry
Summary
MAL-2025-168137: Malicious code in tealove-boy30 (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 package tealove-boy30 is part of the tea.xyz token reward campaign, which has been associated with a series of malicious npm packages. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior not only clutters the npm registry but also poses a significant risk to developers who may unknowingly install these compromised packages.
Vulnerability Detail
The vulnerability in tealove-boy30 originates from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This allows the package to continuously republish variants, polluting the npm registry and potentially leading to security risks for developers who rely on the integrity of npm packages. The autopublish scripts included in the package facilitate this malicious behavior.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-boy30If 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 prevent the installation of tealove-boy30 by using npm's package-lock.json to monitor dependencies. Ensure that your project does not include this package by checking your package.json and removing any references to it.
Conclusion
The tealove-boy30 package presents a significant security risk due to its malicious code designed to manipulate npm registry entries. Developers should take immediate action to remove this package and monitor their projects for vulnerabilities using tools like Vulert.
See every vulnerability recorded for tealove-boy30 →
FAQ
tealove-boy30 is an npm package associated with the tea.xyz token reward campaign, which has been identified as containing malicious code.
The vulnerability can lead to the installation of compromised packages that may alter your project's dependencies and introduce security risks.
Immediately remove the package from your project and check for any other affected packages. Update your dependencies to secure versions.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without requiring 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.
