Malicious Code Injection in tealove-nameka28: A Threat to npm Ecosystem
Summary
MAL-2025-168410: Malicious code in tealove-nameka28 (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 tealove-nameka28 is part of a broader campaign associated with the tea.xyz token reward initiative, which has been known to flood the npm registry with numerous packages. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to alter key files and continuously pollute the npm registry.
Vulnerability Detail
The vulnerability in tealove-nameka28 originates from its design to include autopublish scripts that modify the package.json file by removing private flags and changing version numbers. This allows the package to generate random names, often themed around Indonesian culture, and republish variants, leading to a polluted npm registry. The ramifications include compromised developer reputations and potential security risks for applications relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-nameka28
If 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, avoid using the tealove-nameka28 package and monitor your project for any dependencies that may indirectly rely on it. You can also use the following command to check for vulnerabilities in your project: 'npm audit'.
Conclusion
The tealove-nameka28 package poses a significant threat due to its malicious code designed to manipulate the npm registry. It is crucial for developers to be vigilant, remove affected packages, and utilize tools like Vulert to monitor for vulnerabilities in their projects.
See every vulnerability recorded for tealove-nameka28 →
FAQ
tealove-nameka28 is an npm package that is part of a malicious campaign to inflate developer reputation scores through automated publishing of derivative packages.
The vulnerability can lead to the pollution of the npm registry, which may compromise the integrity of your application's dependencies and affect its security.
You should uninstall the package immediately using 'npm uninstall tealove-nameka28' and check your project for any other affected dependencies.
Yes, you can use tools like Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software. You can check your application for vulnerabilities without any signup using the Vulert playground.
Regularly audit your dependencies using 'npm audit', keep your packages updated, and consider using tools like Vulert to monitor for vulnerabilities.