Malicious Code Injection in firm_duck_requirement Package
Summary
MAL-2025-94523: Malicious code in firm_duck_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 firm_duck_requirement 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 of applications by providing reusable code. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages designed to manipulate developer reputation scores through automated publishing scripts.
Vulnerability Detail
The vulnerability in the firm_duck_requirement package stems from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores for token rewards in the tea.xyz protocol. The malicious payload continuously republishes these variants, leading to pollution of the npm registry and potential security risks for developers who unknowingly use these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall firm_duck_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 firm_duck_requirement package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider implementing strict package management practices to monitor and vet dependencies before including them in your projects.
Conclusion
The firm_duck_requirement package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is essential to remove this package from your projects and adopt best practices for dependency management to safeguard your applications.
See every vulnerability recorded for firm_duck_requirement →
FAQ
The firm_duck_requirement package is an npm package used in JavaScript development, but it has been identified as part of a malicious campaign.
This vulnerability can lead to the pollution of your project's dependencies, potentially introducing security risks and affecting the integrity of your application.
You should remove the firm_duck_requirement package from your project immediately and monitor for any updates or patches.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.
Implement strict package management practices, regularly audit your dependencies, and utilize tools like Vulert to monitor for vulnerabilities.
