Malicious Code Injection in eclipseobserver: A Threat to npm Packages
Summary
MAL-2025-171129: Malicious code in eclipseobserver (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
eclipseobserver is an npm package that is part of the tea.xyz token reward campaign. It is designed to facilitate certain functionalities within the npm ecosystem. However, it has been identified as vulnerable due to the presence of malicious code that alters its package.json file, potentially leading to severe security risks.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded within the eclipseobserver package. This payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names. The intent is to inflate developer reputation scores for token rewards by continuously republishing these variants, which can pollute the npm registry and compromise the integrity of the ecosystem. The ramifications include unauthorized access to sensitive information and the potential for further exploitation of affected systems.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall eclipseobserverIf 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 remove the eclipseobserver package from your project by executing: npm uninstall eclipseobserver. This will prevent the malicious code from executing until a fix is applied.
Conclusion
The eclipseobserver package has been identified as containing malicious code that poses significant security risks. It is crucial for developers to take immediate action by updating or removing the package to safeguard their projects. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.
See every vulnerability recorded for eclipseobserver →
FAQ
eclipseobserver is an npm package associated with the tea.xyz token reward campaign, which has been compromised by malicious code.
The malicious code modifies your package.json file, potentially exposing your project to security vulnerabilities and affecting the integrity of your npm dependencies.
You should immediately update the package to the latest version or uninstall it to prevent any malicious activity.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can check your application for vulnerabilities using the Vulert playground without any signup.
Regularly update your packages, monitor for vulnerabilities using tools like Vulert, and review your dependencies for any known issues.
