Malicious Code Injection in fine_constrictor_requirement Package
Summary
MAL-2025-94516: Malicious code in fine_constrictor_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 fine_constrictor_requirement package is a component of the npm ecosystem, primarily used for managing dependencies in JavaScript applications. It is part of a broader set of packages that have been implicated in a token reward campaign, which aims to manipulate npm's registry by flooding it with derivative packages. This package, like others in the campaign, is designed to inflate developer reputation scores through automated publishing scripts.
Vulnerability Detail
The vulnerability in the fine_constrictor_requirement package stems from its association with a malicious campaign that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly depend on these malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall fine_constrictor_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 measure, you can avoid using the fine_constrictor_requirement package and replace it with a trusted alternative. Always verify the integrity of packages before including them in your project.
Conclusion
The fine_constrictor_requirement package poses a significant risk due to its malicious behavior, which can compromise the security of applications relying on it. It is essential to remove this package and monitor your dependencies regularly to maintain a secure development environment.
See every vulnerability recorded for fine_constrictor_requirement →
FAQ
It is an npm package that has been linked to a malicious campaign aimed at manipulating the npm registry.
The vulnerability can lead to the inclusion of malicious code in your application, potentially compromising its security and integrity.
You should uninstall the fine_constrictor_requirement package immediately and review your project's dependencies for any other potentially harmful packages.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time about open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without requiring any signup.
