Malicious Code Injection in tealoveness67: A Threat to npm Ecosystem
Summary
MAL-2025-168797: Malicious code in tealoveness67 (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 tealoveness67 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 through the automatic generation and publication of derivative packages. The functionality of tealoveness67 is compromised due to its malicious payload, which modifies essential files and repurposes the package for harmful activities.
Vulnerability Detail
The vulnerability in tealoveness67 originates from its inclusion in a campaign that floods the npm registry with malicious packages. The payload alters the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior not only compromises the integrity of the affected package but also pollutes the npm registry, potentially affecting other developers and users relying on npm for secure package management.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealoveness67If 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 the tealoveness67 package by using the following command to uninstall it: npm uninstall tealoveness67. Additionally, consider using npm audit to identify and address other vulnerabilities in your project.
Conclusion
The tealoveness67 package poses a significant threat to the npm ecosystem due to its malicious code and the potential for widespread impact on developers and users. It is crucial to take immediate action to remove this package and monitor your projects for vulnerabilities to maintain a secure development environment.
See every vulnerability recorded for tealoveness67 →
FAQ
Tealoveness67 is an npm package associated with a malicious campaign that aims to inflate developer reputation scores through the automatic generation of derivative packages.
The vulnerability can compromise your project's integrity by modifying essential files and potentially introducing harmful code that affects the functionality and security of your application.
You should immediately uninstall the package using npm uninstall tealoveness67 and check for any other vulnerabilities in your project.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can also check your application against known vulnerabilities using the Vulert playground.
Regularly audit your dependencies using npm audit, keep your packages updated, and consider using tools like Vulert for continuous monitoring of your project's dependencies.
