Malicious Code Injection in dramatic_narwhal-tool: npm Package Vulnerability

dramatic_narwhal-tool Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101761: Malicious code in dramatic_narwhal-tool (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The dramatic_narwhal-tool is an npm package that has been implicated in a malicious campaign associated with the tea.xyz token reward system. This package is designed to assist developers in various tasks, but it has been compromised to include harmful scripts that manipulate its functionality. The vulnerability arises from the package's ability to modify its own metadata, leading to potential security risks for users who integrate it into their projects.

Vulnerability Detail

The vulnerability in dramatic_narwhal-tool originates from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious payload within this package alters the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior not only compromises the integrity of the package but also pollutes the npm registry, potentially affecting other developers and projects that rely on it. The ramifications include unauthorized access to sensitive data, reputation damage for developers, and increased difficulty in managing dependencies.

How To Fix

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

npm uninstall dramatic_narwhal-tool

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

If you cannot update the package immediately, consider removing it from your project and replacing it with a secure alternative. Additionally, you can monitor your package-lock.json file for any unauthorized changes using tools like Vulert, which provides real-time alerts for open-source vulnerabilities.

Conclusion

The dramatic_narwhal-tool package has been identified as containing malicious code that compromises its integrity and poses security risks to users. It is essential to update or remove this package to protect your projects from potential vulnerabilities. Utilizing tools like Vulert can help you monitor your dependencies effectively.

See every vulnerability recorded for dramatic_narwhal-tool →

Share this vulnerability

FAQ

The dramatic_narwhal-tool is an npm package that was initially designed for various development tasks but has been compromised to include malicious scripts.

The vulnerability can lead to unauthorized modifications of your package.json file, potentially exposing your project to security risks and dependency issues.

You should immediately update the package to the latest version or remove it from your project to prevent any potential security breaches.

Yes, you can use Vulert, which allows you to monitor your package-lock.json for vulnerabilities in real-time without requiring installation.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall dramatic_narwhal-tool

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