Malicious Code Injection in disappointed_jay-appteadev Package
Summary
MAL-2025-101614: Malicious code in disappointed_jay-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 disappointed_jay-appteadev package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores in exchange for tea protocol token rewards. However, it has been identified as containing malicious code that compromises its integrity and the security of the npm registry.
Vulnerability Detail
The vulnerability originates from the package's malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names, primarily themed around Indonesian culture. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially affecting other developers by inflating reputation scores fraudulently. The malicious scripts (auto.js, autopublish.js, etc.) are designed to automate this process, making it difficult for developers to identify and mitigate the issue.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall disappointed_jay-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 disappointed_jay-appteadev package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes.
Conclusion
The disappointed_jay-appteadev package poses a significant security risk due to its malicious code that alters package files and floods the npm registry. It is crucial for developers to remove this package from their projects and monitor for any similar vulnerabilities using tools like Vulert. Staying informed and proactive is essential in maintaining the security of your applications.
See every vulnerability recorded for disappointed_jay-appteadev →
FAQ
The package contains malicious code that modifies package.json files and republishes variants to pollute the npm registry.
You can use Vulert, which monitors your package-lock.json file for vulnerabilities. You can check your application using the Vulert playground without any signup.
You should uninstall the package immediately and look for alternatives that do not pose security risks.
Currently, there is no patched version available. The best course of action is to remove the package.
Vulert uses your package-lock.json file to monitor and alert you in real-time for open-source vulnerabilities in your software.
