Malicious Code Injection in kitty-teadev: A Threat to npm Ecosystem
Summary
MAL-2025-104834: Malicious code in kitty-teadev (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 'kitty-teadev' is part of the npm ecosystem, which is widely used for JavaScript package management. It is designed to facilitate the development and sharing of JavaScript code. However, this package has been identified as part of a malicious campaign that aims to exploit the npm registry by publishing derivative packages with harmful scripts. The vulnerability stems from its association with the tea.xyz token reward scheme, which has been linked to various malicious activities.
Vulnerability Detail
The vulnerability in 'kitty-teadev' originates from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores within the tea protocol token rewards system. The malicious payload continuously republishes variants of the package, polluting the npm registry and potentially compromising other packages and applications that depend on it. This poses significant risks to developers and users by introducing untrusted code into their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall kitty-teadevIf 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, avoid using the 'kitty-teadev' package and consider using alternative packages that provide similar functionality without the associated risks. Always review the source and reputation of packages before including them in your project.
Conclusion
The 'kitty-teadev' package poses a significant threat due to its malicious code that manipulates package metadata and floods the npm registry with harmful variants. It is crucial for developers to remove this package from their projects and adopt best practices for dependency management to safeguard their applications.
See every vulnerability recorded for kitty-teadev →
FAQ
The main issue is that it contains malicious code that modifies package.json files and publishes harmful variants to the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.
You should uninstall the package immediately using 'npm uninstall kitty-teadev' and review your project for any other potentially harmful dependencies.
Yes, using this package can lead to the introduction of untrusted code into your application, which may compromise its security and integrity.
Regularly audit your dependencies, use tools like Vulert for monitoring vulnerabilities, and only install packages from trusted sources.
