Malicious Code Vulnerability in narrow_mockingbird_requirement Package
Summary
MAL-2025-95582: Malicious code in narrow_mockingbird_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 narrow_mockingbird_requirement package is part of the npm ecosystem, which is widely used for JavaScript package management. This package 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 for token rewards.
Vulnerability Detail
The vulnerability in the narrow_mockingbird_requirement package originates from its association with malicious scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants that pollute the npm registry. This can have serious ramifications, including the potential for developers to unknowingly install compromised packages, leading to security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall narrow_mockingbird_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 remove the narrow_mockingbird_requirement package from your project by executing the following command: npm uninstall narrow_mockingbird_requirement. This will prevent any malicious code from executing until a fix is applied.
Conclusion
The narrow_mockingbird_requirement package contains a serious vulnerability due to its association with malicious scripts that alter package metadata. It is crucial for developers to take immediate action by updating or removing the package to safeguard their applications from potential threats.
See every vulnerability recorded for narrow_mockingbird_requirement →
FAQ
It is an npm package that has been linked to a malicious campaign aimed at manipulating package metadata for token rewards.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By checking your package-lock.json file, you can identify any vulnerabilities without needing to install additional tools.
Using compromised packages can lead to security vulnerabilities in your application, including unauthorized access, data breaches, and potential exploitation of your system.
Regularly updating your dependencies, using tools like Vulert for monitoring vulnerabilities, and auditing your packages can help prevent such issues.
You should uninstall the vulnerable package immediately and check for any updates or patches. Additionally, review your application for any potential security impacts.
