Malicious Code Vulnerability in flores-tea-archive Package
Summary
MAL-2025-102824: Malicious code in flores-tea-archive (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 flores-tea-archive package is part of the tea.xyz token reward campaign that has infiltrated the npm ecosystem. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, its malicious nature poses significant risks to developers and users alike.
Vulnerability Detail
The vulnerability in the flores-tea-archive package stems from its inclusion in a campaign that utilizes autopublish scripts to create and publish numerous derivative packages with randomized names. This malicious payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names, ultimately leading to pollution of the npm registry. The origin of this vulnerability is linked to the broader tea.xyz token reward scheme, which incentivizes such behavior, potentially compromising 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 flores-tea-archiveIf 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 flores-tea-archive package and instead utilize alternative packages that do not exhibit malicious behavior. Additionally, consider implementing strict package management practices to monitor and control the packages used in your project.
Conclusion
The flores-tea-archive package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to be aware of this vulnerability, take immediate action to remove the package, and implement best practices for package management to safeguard their projects.
See every vulnerability recorded for flores-tea-archive →
FAQ
The flores-tea-archive package is part of a token reward campaign that automates the generation and publication of npm packages, but it contains malicious code.
This vulnerability can lead to the pollution of the npm registry, potentially compromising the security and integrity of your project by introducing unwanted or malicious packages.
You can use Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
If you have installed the flores-tea-archive package, you should remove it immediately and monitor your project for any unusual behavior or additional vulnerabilities.
Yes, consider using other reputable packages that provide similar functionality without the associated risks of malicious behavior.
