Malicious Code Injection in external_nightingale_dumbs Package

external_nightingale_dumbs Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102421: Malicious code in external_nightingale_dumbs (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 external_nightingale_dumbs package is part of a larger ecosystem that has been exploited for malicious purposes, specifically linked to the tea.xyz token reward campaign. This package is designed to interact with the npm registry, allowing developers to publish and manage JavaScript packages. However, its recent exploitation has raised significant concerns regarding its integrity and security.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the external_nightingale_dumbs package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which are often themed around Indonesian culture. The primary risk is that it allows for the automatic generation and republishing of derivative packages, leading to pollution of the npm registry and potential misuse of developer reputation scores. This can result in developers inadvertently using compromised packages, exposing their applications to further vulnerabilities.

How To Fix

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

npm uninstall external_nightingale_dumbs

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 temporary workaround, you can prevent the installation of the external_nightingale_dumbs package by using the following command:

npm uninstall external_nightingale_dumbs

Additionally, ensure that your package-lock.json file is monitored for any unauthorized changes.

Conclusion

The external_nightingale_dumbs package has been identified as containing malicious code that poses significant risks to developers and their applications. It is crucial to take immediate action by updating or removing the package and utilizing tools like Vulert for ongoing monitoring of vulnerabilities.

See every vulnerability recorded for external_nightingale_dumbs →

Share this vulnerability

FAQ

It is a package associated with the npm ecosystem, which has been exploited for malicious activities related to the tea.xyz token reward campaign.

If your application uses the external_nightingale_dumbs package, it may be at risk of using compromised code that can lead to security breaches and reputation damage.

You should immediately update or uninstall the package to mitigate any potential risks associated with the vulnerability.

Yes, you can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.

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

How To Fix

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

npm uninstall external_nightingale_dumbs

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