Malicious Code Injection in Scary Gull Requirement Package
Summary
MAL-2025-96452: Malicious code in scary_gull_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 'scary_gull_requirement' package is part of the npm ecosystem, often utilized for various JavaScript functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant security risks.
Vulnerability Detail
The vulnerability stems from the malicious code embedded within the 'scary_gull_requirement' package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The result is a continuous republishing of these variants, which pollutes the npm registry and can compromise the integrity of other packages. The origin of this issue is linked to the tea.xyz token reward campaign, which exploits npm for malicious purposes.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall scary_gull_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 prevent the installation of this package by using npm's package-lock.json file to monitor dependencies. Additionally, consider using tools like Vulert to scan your project 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 'scary_gull_requirement' package poses a significant security risk due to its malicious code designed to manipulate npm's registry. It is crucial to remove this package from your project and monitor your dependencies for any vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for scary_gull_requirement →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.
The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of other packages and affecting your application's security.
You should uninstall the 'scary_gull_requirement' package immediately and check for any dependencies that may also need to be addressed.
Yes, you can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
