Malicious Code Injection in feminist_stork-strongdev Package
Summary
MAL-2025-102679: Malicious code in feminist_stork-strongdev (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 feminist_stork-strongdev package is part of the npm ecosystem, often used in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages. This package is designed to manipulate its own metadata and publish derivative versions to inflate developer reputation scores, posing significant risks to users.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded within the feminist_stork-strongdev package. This payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also compromises the integrity of projects that depend on this package, potentially leading to security breaches and loss of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall feminist_stork-strongdevIf 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 feminist_stork-strongdev package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner.
Conclusion
The feminist_stork-strongdev package poses a significant security risk due to its malicious code that alters package metadata and republishing behavior. It is essential for developers to remove this package from their projects and monitor for vulnerabilities using tools like Vulert to ensure the integrity of their applications.
See every vulnerability recorded for feminist_stork-strongdev →
FAQ
It is an npm package that has been identified as part of a malicious campaign to manipulate package metadata and inflate developer reputation scores.
The vulnerability can lead to the introduction of malicious code into your project, compromising its security and integrity.
You should uninstall the feminist_stork-strongdev package immediately and look for alternative packages.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
