Malicious Code Vulnerability in confused_mouse_requirement Package
Summary
MAL-2025-93719: Malicious code in confused_mouse_requirement (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 confused_mouse_requirement package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to provide specific functionalities to developers. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to potential security risks for users who integrate it into their projects.
Vulnerability Detail
The vulnerability originates from the confused_mouse_requirement package being associated with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts designed to modify the package.json file, removing private flags, altering version numbers, and generating random package names. This behavior can lead to the pollution of the npm registry and compromise the integrity of applications relying on these packages. The malicious payload can inflate developer reputation scores fraudulently, posing risks to the broader developer community.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall confused_mouse_requirementIf 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 avoid using the confused_mouse_requirement package and look for alternative packages that provide similar functionalities without the associated risks. Additionally, you can use the following command to uninstall the package: npm uninstall confused_mouse_requirement.
Conclusion
The confused_mouse_requirement package poses a significant security risk due to its association with malicious activities in the npm ecosystem. It is crucial for developers to be vigilant and remove any instances of this package from their projects. Utilizing tools like Vulert can help in monitoring and identifying vulnerabilities in real-time.
See every vulnerability recorded for confused_mouse_requirement →
FAQ
It is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.
The vulnerability can lead to the pollution of the npm registry and may compromise the security and integrity of applications that depend on this package.
You should uninstall the confused_mouse_requirement package immediately and monitor for any updates or patches.
You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just package-lock.json. You can also check if your application is affected by this vulnerability using the Vulert playground.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without requiring any signup.
