Critical Malicious Code Vulnerability in wenk Package
Summary
MAL-2025-191155: Malicious code in wenk (npm). Affects wenk versions 1.0.10 – 1.0.9. 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 wenk package is a Node.js library available through npm, designed to facilitate various web development tasks. It is widely used for its simplicity and efficiency in managing web-related functionalities. However, recent findings have revealed that certain versions of wenk contain malicious code that compromises the security of any system where it is installed.
Vulnerability Detail
The vulnerability stems from embedded malicious code within the wenk package, specifically in versions 1.0.9 and 1.0.10. This code can grant unauthorized access to the system, allowing attackers to control the affected machine fully. As a result, any secrets or keys stored on the compromised computer should be considered at risk. The malicious nature of this code is classified under CWE-506, indicating that it appears to be intentionally harmful.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall wenkIf 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 prevent the execution of the wenk package by uninstalling it using the command: npm uninstall wenk. Ensure that you monitor your system for any unusual activities that may indicate further compromise.
Conclusion
The wenk package has been identified to contain malicious code that poses a significant security risk. Users are advised to uninstall the affected versions immediately and take necessary precautions to secure their systems. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.
See every vulnerability recorded for wenk →
FAQ
Immediately uninstall the wenk package and rotate any sensitive credentials stored on the affected machine.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.
The affected versions are 1.0.9 and 1.0.10.
Yes, Vulert can monitor your package-lock.json file to alert you in real-time for any open-source vulnerabilities.
Failing to address this vulnerability could lead to unauthorized access to your system, data breaches, and potential loss of sensitive information.
