Malicious Code Injection in double_pig_requirement Package
Summary
MAL-2025-94102: Malicious code in double_pig_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 double_pig_requirement package is part of the npm ecosystem, often utilized in JavaScript projects for dependency management. This package has been identified as part of a malicious campaign that floods the npm registry with derivative packages. Its primary functionality is to facilitate the automatic generation and publication of packages, which can inflate developer reputation scores for token rewards. However, this package has been compromised, leading to significant security concerns.
Vulnerability Detail
The vulnerability originates from the package being associated 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 can lead to unauthorized access, reputation damage for developers, and potential exploitation of applications relying on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall double_pig_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, consider removing the double_pig_requirement package from your project until a secure version is available. You can do this using the following command: npm uninstall double_pig_requirement. Additionally, monitor your package-lock.json file for any unauthorized changes.
Conclusion
The double_pig_requirement package poses a significant security risk due to its malicious code injection. It is essential for developers to take immediate action by updating or removing the package to protect their applications. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.
See every vulnerability recorded for double_pig_requirement →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to unauthorized modifications in your package.json file, potentially compromising your application's integrity and security.
You should immediately update or uninstall the double_pig_requirement package to mitigate the risks associated with this vulnerability.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can check your application’s status using the Vulert playground without any signup.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated with the latest security patches for all packages.
