Malicious Code Injection in local_narwhal_requirement Package
Summary
MAL-2025-95300: Malicious code in local_narwhal_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 local_narwhal_requirement package is part of the npm ecosystem, primarily used for managing dependencies in JavaScript applications. It is designed to facilitate the integration of various libraries and tools within a project. However, this package has been identified as part of a malicious campaign that exploits npm's package publishing system, leading to significant security concerns.
Vulnerability Detail
The vulnerability stems from the package being associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages contain scripts that automatically modify the package.json file, removing private flags, altering version numbers, and generating random package names. This behavior not only compromises the integrity of the affected applications but also pollutes the npm registry, making it difficult for developers to trust the packages they use.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall local_narwhal_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 local_narwhal_requirement package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your dependencies using tools like npm audit to identify and mitigate vulnerabilities.
Conclusion
The local_narwhal_requirement package poses a significant security risk due to its association with malicious activities in the npm ecosystem. It is essential for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to ensure their applications remain secure.
See every vulnerability recorded for local_narwhal_requirement →
FAQ
It is an npm package used for managing dependencies in JavaScript applications, but it has been identified as part of a malicious campaign.
The vulnerability can lead to unauthorized modifications of your package.json file, potentially compromising your application's integrity and security.
You should uninstall the local_narwhal_requirement package immediately and review your project for any related changes.
You can use tools like npm audit or services like Vulert, which monitors your package-lock.json for 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.
