Critical Malicious Code Vulnerability in weavejs-backend Package
Summary
MAL-2025-6781: Malicious code in weavejs-backend (npm). Affects weavejs-backend versions >= 10.4.5. 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 weavejs-backend package is an npm library designed to facilitate backend functionalities for applications using the WeaveJS framework. It provides essential features such as data handling, API integration, and user authentication. However, this package has been identified to communicate with a domain linked to malicious activities, posing a significant security risk to applications utilizing it.
Vulnerability Detail
The vulnerability stems from the package's communication with a domain associated with malicious activity. This can lead to unauthorized data access, potential data breaches, and exploitation of the application by attackers. The issue was introduced in version 10.4.5, and it is crucial for developers to be aware of the risks involved with using this version or any subsequent versions that do not address this vulnerability.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall weavejs-backendIf 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 may consider removing the weavejs-backend package from your project until a secure version is available. Alternatively, you can implement network security measures to block communications with the malicious domain.
Conclusion
The weavejs-backend package has a critical vulnerability that allows communication with a malicious domain, posing significant risks to applications. It is essential to update the package to a secure version and consider workarounds until a fix is implemented. Regular monitoring using tools like Vulert can help maintain application security.
See every vulnerability recorded for weavejs-backend →
FAQ
The vulnerability involves the package communicating with a domain linked to malicious activities, which can compromise application security.
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.
Consider removing the weavejs-backend package or implementing network security measures to prevent communication with the malicious domain.
Yes, a patched version of the weavejs-backend package is expected to be released. Always check the package repository for updates.
Failure to address this vulnerability can lead to unauthorized access to sensitive data, data breaches, and exploitation of your application by malicious actors.
