Malicious Code Injection in jeromy-tea-archive: npm Package Vulnerability
Summary
MAL-2025-104545: Malicious code in jeromy-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 jeromy-tea-archive package is part of a broader campaign associated with the tea.xyz token reward system, which has been known to flood the npm registry with numerous packages. This package is designed to facilitate token rewards through automated publishing scripts that create derivative packages. However, it has been identified as containing malicious code that compromises the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability originates from the package's malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to manipulate developer reputation scores and pollute the npm registry. This can lead to significant security risks, including the potential for dependency confusion and the introduction of further vulnerabilities into applications that rely on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall jeromy-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 measure, you can avoid using the jeromy-tea-archive package and replace its functionality with a trusted alternative. Additionally, regularly audit your npm packages using tools like npm audit to identify and mitigate vulnerabilities.
Conclusion
The jeromy-tea-archive package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their applications.
See every vulnerability recorded for jeromy-tea-archive →
FAQ
jeromy-tea-archive is an npm package associated with the tea.xyz token reward campaign, which automates the generation and publishing of derivative packages.
The vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and integrity.
You should uninstall the jeromy-tea-archive package immediately and review your dependencies for any other vulnerabilities.
Yes, tools like Vulert can monitor your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
