Malicious Code Injection in tealove-nanami31: A Threat to npm Ecosystem
Summary
MAL-2025-168461: Malicious code in tealove-nanami31 (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-nanami31 is part of the tea.xyz token reward campaign that has recently infiltrated the npm ecosystem. This package is designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. Its functionality is primarily centered around manipulating package metadata and publishing behavior, making it susceptible to exploitation.
Vulnerability Detail
The vulnerability in tealove-nanami31 stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, effectively polluting the npm registry. The origin of this vulnerability is linked to a broader campaign that aims to exploit npm's publishing mechanisms for malicious purposes, potentially compromising the integrity of the registry and affecting developers relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-nanami31If 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, you can monitor your package-lock.json file for any unauthorized changes and ensure that no untrusted packages are included in your project. Regularly auditing your dependencies with tools like npm audit can help identify potential vulnerabilities.
Conclusion
The vulnerability in tealove-nanami31 poses a significant threat to the npm ecosystem, allowing malicious actors to manipulate package metadata and publish unauthorized variants. It is crucial for developers to take immediate action by removing the affected package and implementing best practices for dependency management to safeguard their projects.
See every vulnerability recorded for tealove-nanami31 →
FAQ
Tealove-nanami31 is an npm package that is part of a token reward campaign, designed to manipulate package publishing in the npm ecosystem.
The vulnerability can lead to unauthorized changes in your package.json file, potentially compromising your project's integrity and security.
You should uninstall the package immediately using 'npm uninstall tealove-nanami31' and review your project's dependencies for any other malicious packages.
Regularly audit your dependencies, use trusted packages, and keep your software updated to minimize the risk of vulnerabilities.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can check if your application is affected by visiting the Vulert playground at Vulert Scanner.
