Malicious Code Injection in tealove-nanami33: A Threat to npm Packages
Summary
MAL-2025-168463: Malicious code in tealove-nanami33 (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-nanami33 is part of a broader campaign that exploits the npm ecosystem, specifically targeting developers involved in the tea.xyz token reward initiative. This package is designed to automate the generation and publication of derivative packages, which can mislead users and inflate developer reputation scores. Its functionality is compromised by malicious scripts that alter package metadata and continuously republish variants, thereby polluting the npm registry.
Vulnerability Detail
The vulnerability in tealove-nanami33 stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these tainted packages. The malicious payload is designed to create a flood of derivative packages, making it difficult for legitimate packages to stand out and potentially leading to 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-nanami33If 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 tealove-nanami33 package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.
Conclusion
The tealove-nanami33 package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry with derivative packages. It is essential for developers to be vigilant, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, you can protect your projects from potential threats.
See every vulnerability recorded for tealove-nanami33 →
FAQ
Tealove-nanami33 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the inclusion of malicious code in your project, which may compromise security and integrity, potentially affecting your application's functionality.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
If you have installed tealove-nanami33, you should uninstall it immediately using the command npm uninstall tealove-nanami33 and review your project for any other potentially vulnerable packages.
Yes, Vulert provides a service that monitors your package-lock.json for open-source vulnerabilities in real-time, helping you stay informed about potential risks.
