Malicious Code Injection in spare_narwhal_0xrequest Package

spare_narwhal_0xrequest Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-108963: Malicious code in spare_narwhal_0xrequest (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The spare_narwhal_0xrequest package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate token rewards by generating and publishing derivative packages. However, it has been identified as containing malicious code that compromises its integrity and the integrity of the npm registry.

Vulnerability Detail

The vulnerability originates from the malicious payload embedded within the spare_narwhal_0xrequest package. It modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which leads to the continuous republishing of these variants. This behavior not only inflates developer reputation scores but also pollutes the npm registry, potentially affecting other developers and their projects.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall spare_narwhal_0xrequest

If 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 workaround, consider using alternative packages that provide similar functionality without the risk of malicious code. Additionally, regularly audit your npm packages using tools like npm audit to identify and address vulnerabilities.

Conclusion

The spare_narwhal_0xrequest package contains malicious code that poses a significant risk to developers and the npm ecosystem. Immediate action is required to remove the package and mitigate potential impacts. Regular monitoring and auditing of packages are essential to maintain security.

See every vulnerability recorded for spare_narwhal_0xrequest →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.

The malicious code modifies your package.json file, which can lead to security vulnerabilities and pollution of the npm registry.

You should uninstall the package immediately and consider using alternative packages.

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 for vulnerabilities in your application without requiring an account.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall spare_narwhal_0xrequest

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback