Malicious Code Injection in win693 Package: A Threat to npm Ecosystem
Summary
MAL-2025-172005: Malicious code in win693 (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 win693 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and distribution of JavaScript applications. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities to inflate developer reputation scores through the creation of numerous derivative packages.
Vulnerability Detail
The vulnerability in the win693 package stems from its involvement in a malicious campaign that modifies the package.json file to remove private flags, changes version numbers, and generates random package names. This behavior is designed to pollute the npm registry by continuously republishing variants, which can lead to a compromised development environment and potential security risks for developers relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall win693If 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, avoid using the win693 package and monitor your dependencies for any malicious activity. You can also use tools like Vulert to check your package-lock.json for vulnerabilities.
Conclusion
The win693 package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to be aware of this vulnerability and take immediate action to remove the package and monitor their dependencies. Utilizing tools like Vulert can aid in maintaining the security of your projects.
See every vulnerability recorded for win693 →
FAQ
The win693 package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.
The vulnerability can lead to the pollution of the npm registry and compromise the integrity of your project's dependencies.
You should uninstall the win693 package immediately using the command: npm uninstall win693.
Yes, you can use Vulert to monitor your package-lock.json file for vulnerabilities in real-time without needing to access the code.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
