Malicious Code Injection in Solarwatcher Package
Summary
MAL-2025-171890: Malicious code in solarwatcher (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
Solarwatcher is an npm package designed for monitoring solar energy systems. It provides functionalities for data collection, analysis, and visualization of solar energy metrics. However, it has been compromised by malicious actors who have embedded harmful scripts that manipulate package metadata and publish unauthorized variants.
Vulnerability Detail
The vulnerability originates from the solarwatcher package being part of a larger malicious campaign associated with the tea.xyz token reward initiative. This campaign has led to the creation of packages that include scripts designed to automatically publish derivative packages with altered metadata. The malicious payload modifies the package.json file to remove private flags, changes version numbers, and generates random package names, leading to pollution of the npm registry and potential security risks for developers using these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall solarwatcherIf 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 solarwatcher package from your project until a secure version is released. Use the following command to uninstall the package: npm uninstall solarwatcher.
Conclusion
The solarwatcher package has been compromised by malicious code that alters its metadata and publishes unauthorized variants. It is crucial for developers to update their packages and monitor for vulnerabilities to maintain the integrity of their applications.
See every vulnerability recorded for solarwatcher →
FAQ
The malicious code modifies the package.json file to remove private flags and generates random package names, which can lead to unauthorized package publication.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.
If an immediate update is not possible, consider removing the package from your project as a temporary measure to avoid potential risks.
The impacts include potential exposure to malicious code, unauthorized package publication, and pollution of the npm registry, which can affect the reputation of developers.
The vulnerability was identified by Amazon Inspector, which specializes in detecting malicious packages in open-source ecosystems.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
