Malicious Code Injection in smoggy_coyote_requirement Package
Summary
MAL-2025-96641: Malicious code in smoggy_coyote_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 smoggy_coyote_requirement package is part of the npm ecosystem, typically used for managing dependencies in JavaScript applications. However, this package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. This vulnerability poses a significant risk to developers and users relying on npm packages, as it can lead to the proliferation of harmful code within the ecosystem.
Vulnerability Detail
The vulnerability originates from the smoggy_coyote_requirement package, which is linked to the tea.xyz token reward campaign. This package contains scripts designed to automatically modify package.json files by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants, polluting the npm registry and potentially compromising the integrity of applications that depend on these packages. The ramifications include exposure to malicious code and the risk of unintentional usage of compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall smoggy_coyote_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 smoggy_coyote_requirement package and any packages that depend on it. Additionally, consider using a tool like Vulert to monitor your package-lock.json for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The smoggy_coyote_requirement package poses a significant risk due to its malicious code injection capabilities. Developers should take immediate action to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for smoggy_coyote_requirement →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores by automatically generating and publishing derivative packages.
The vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and integrity.
You should uninstall the smoggy_coyote_requirement package immediately and check your package-lock.json for any references to it.
Yes, Vulert allows you to monitor your package-lock.json for open-source vulnerabilities in real-time without requiring access to your code or installation.
There is no patch for the smoggy_coyote_requirement package as it is a malicious package. The best course of action is to remove it from your project.
