Critical Malicious Code Vulnerability in @we3js/framework Package
Summary
MAL-2026-17842: Malicious code in @we3js/framework (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 @we3js/framework package is a JavaScript framework designed for building decentralized applications. It provides developers with tools and libraries to streamline the development process. However, this package has been found to contain malicious code, posing significant security risks to any system that has it installed.
Vulnerability Detail
The vulnerability originates from the inclusion of malicious code within the @we3js/framework package. This code can compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The ramifications of this vulnerability are severe, as it can lead to complete control of the affected system by an external entity. Users are advised to treat any system with this package as fully compromised.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @we3js/frameworkIf 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
Currently, there are no effective workarounds other than removing the package and rotating any secrets or keys stored on the affected system. It is essential to perform these actions from a different, secure computer.
Conclusion
The discovery of malicious code in the @we3js/framework package poses a critical security threat to users. Immediate action is required to remove the package and secure any compromised systems. Regular monitoring and vulnerability checks, such as those provided by Vulert, can help prevent future incidents.
See every vulnerability recorded for @we3js/framework →
FAQ
You should remove the package immediately and rotate any sensitive information stored on your system.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
Leaving the package installed can lead to unauthorized access to your system and compromise sensitive data.
The best course of action is to remove the package and rotate all sensitive information. There is no guarantee that removing the package will eliminate all malicious software.
If a patched version is released, updating the package may resolve the issue. However, it is recommended to remove the package entirely until then.
