Malicious Code Injection in annual_jay_yellow-85: A Threat to npm Packages
Summary
MAL-2025-99478: Malicious code in annual_jay_yellow-85 (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 'annual_jay_yellow-85' is part of a series of npm packages that have been associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to modify critical files and republish variants, thereby polluting the npm registry.
Vulnerability Detail
The vulnerability in 'annual_jay_yellow-85' originates from its inclusion in a malicious campaign that utilizes autopublish scripts to manipulate package.json files. This manipulation removes private flags, alters version numbers, and generates random package names, which can lead to a significant increase in spam within the npm registry. The ramifications include potential security risks for developers who may unknowingly use these compromised packages, as well as damage to the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall annual_jay_yellow-85
If 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 'annual_jay_yellow-85' package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity of packages before installation.
Conclusion
The 'annual_jay_yellow-85' package poses a significant risk due to its malicious code designed to manipulate npm packages. Developers are advised to remove this package and monitor their dependencies closely to maintain the integrity of their projects.
See every vulnerability recorded for annual_jay_yellow-85 →
FAQ
The package contains malicious code that modifies package.json files and republish variants to inflate developer reputation scores.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
You should uninstall the package immediately using 'npm uninstall annual_jay_yellow-85' and review your project's dependencies for any other potentially malicious packages.
Yes, using this package can lead to security vulnerabilities, spam in the npm registry, and potential reputation damage for developers.
Regularly audit your dependencies, use tools like Vulert for monitoring, and only install packages from trusted sources.