Critical Malicious Code Vulnerability in @workleap-ai/shared Package
Summary
MAL-2026-210: Malicious code in @workleap-ai/shared (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 @workleap-ai/shared package is a JavaScript library used in Node.js applications, primarily for shared functionalities across various modules. It is part of the npm ecosystem, which allows developers to easily integrate and manage dependencies in their projects. However, this package has been identified to contain malicious code that compromises the security of any system it is installed on.
Vulnerability Detail
The vulnerability originates from the presence of embedded malicious code within the @workleap-ai/shared package. This code can fully compromise any computer where the package is installed, allowing unauthorized access to sensitive information such as secrets and keys. The ramifications of this vulnerability are severe, as it may lead to data breaches and loss of control over the affected systems. Users are advised to treat any system with this package as compromised and take immediate action.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @workleap-ai/sharedIf 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 to mitigate the risks associated with this vulnerability other than removing the package entirely. Ensure that you monitor your systems for any signs of compromise.
Conclusion
The discovery of malicious code in the @workleap-ai/shared package poses a significant threat to users and their systems. Immediate action is required to mitigate risks, including uninstalling the package and rotating sensitive information. Continuous monitoring and auditing of dependencies are crucial to maintaining security.
See every vulnerability recorded for @workleap-ai/shared →
FAQ
You should immediately uninstall the package using npm uninstall @workleap-ai/shared and rotate any sensitive information stored on the affected system.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.
Failure to address this vulnerability can lead to unauthorized access to sensitive data, data breaches, and loss of control over your systems.
Regularly monitor your dependencies for vulnerabilities using tools like Vulert, and ensure to keep your packages updated.
While the npm ecosystem is generally reliable, it is essential to remain vigilant and regularly audit your dependencies for any potential vulnerabilities.
