Malicious Code Vulnerability in increasing_marsupial_requirement Package
Summary
MAL-2025-94983: Malicious code in increasing_marsupial_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 'increasing_marsupial_requirement' package is part of the npm ecosystem, primarily used for managing dependencies in JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing a significant risk to users and the integrity of the npm registry.
Vulnerability Detail
This vulnerability originates from the malicious intent behind the 'increasing_marsupial_requirement' package, which includes scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. The scripts continuously republish these variants, polluting the npm registry and potentially compromising the security of applications that depend on these packages. The ramifications include unauthorized access to sensitive information and the degradation of the npm ecosystem's reliability.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall increasing_marsupial_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 measure, you can avoid using the 'increasing_marsupial_requirement' package and replace it with a trusted alternative. Additionally, you can lock your package versions in your package-lock.json file to prevent automatic updates to potentially malicious packages.
Conclusion
The 'increasing_marsupial_requirement' package poses a significant threat due to its malicious code designed to manipulate npm package metadata. It is essential to remove this package and monitor your dependencies for vulnerabilities to maintain the security of your applications.
See every vulnerability recorded for increasing_marsupial_requirement →
FAQ
It is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry and developer reputation scores.
The vulnerability can lead to unauthorized modifications in your project's dependencies, potentially exposing sensitive information and compromising application security.
You should immediately remove the 'increasing_marsupial_requirement' package and check for any other potentially malicious packages in your project.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
