Malicious Code Detected in gameworks: A Critical npm Vulnerability
Summary
MAL-2025-21177: Malicious code in gameworks (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 'gameworks' package is an npm library designed for game development, providing various tools and functionalities to streamline the creation of games. However, it has been identified to contain malicious code, posing a significant risk to developers and users who integrate this package into their projects.
Vulnerability Detail
The vulnerability in the 'gameworks' package stems from the inclusion of malicious code that can compromise the security of applications utilizing this library. This code can lead to unauthorized access, data breaches, or other harmful actions that can affect both the developers and end-users. The malicious code was introduced in version 0 and has not been addressed in subsequent releases, making it imperative for users to take immediate action.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall gameworks
If 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 measure, you can avoid using the 'gameworks' package altogether and look for alternative libraries that provide similar functionalities without the associated risks. Additionally, you can monitor your dependencies using tools like Vulert, which can help identify vulnerabilities in your package-lock.json file.
Conclusion
The discovery of malicious code in the 'gameworks' npm package highlights the importance of vigilance in managing open-source dependencies. Developers should take immediate action to remove this package and consider alternatives while utilizing tools like Vulert to monitor their projects for vulnerabilities.
See every vulnerability recorded for gameworks →
FAQ
The malicious code can lead to unauthorized access and potential data breaches, affecting both developers and end-users.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without any signup.
Currently, there is no patched version available. It is recommended to remove the package until a secure version is released.
You should immediately remove the 'gameworks' package from your project and look for alternative libraries.
Vulert uses your package-lock.json to monitor and alert you in real-time for open-source vulnerabilities in your software.