Malicious Code Injection in damaged_cricket-appteadev Package
Summary
MAL-2025-101192: Malicious code in damaged_cricket-appteadev (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 damaged_cricket-appteadev package is part of the npm ecosystem, which is widely used for JavaScript development. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary functionality of this package is to serve as a tool for developers, but it has been compromised to include harmful scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability in the damaged_cricket-appteadev package originates from its association with a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to pollution of the npm registry. This can result in security risks for developers who unknowingly use these compromised packages, potentially exposing their applications to further vulnerabilities.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall damaged_cricket-appteadevIf 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 damaged_cricket-appteadev package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file using tools like Vulert to receive real-time alerts for any open-source vulnerabilities.
Conclusion
The damaged_cricket-appteadev package poses a significant security risk due to its malicious code designed to manipulate package metadata. It is essential for developers to remove this package from their projects and monitor for vulnerabilities using tools like Vulert to ensure the security of their applications.
See every vulnerability recorded for damaged_cricket-appteadev →
FAQ
It is an npm package that has been compromised to include malicious code aimed at manipulating package metadata and inflating developer reputation scores.
The malicious code can lead to the pollution of the npm registry and may expose your application to further vulnerabilities if you use these compromised packages.
You should uninstall the damaged_cricket-appteadev package immediately and monitor for any updates or patches that may be released.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
Vulert is a monitoring tool that uses your package-lock.json file to alert you in real-time about open-source vulnerabilities in your software, helping you maintain secure applications.
