Malicious Code Injection in neighbouring_cicada_dumbs Package

neighbouring_cicada_dumbs Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106252: Malicious code in neighbouring_cicada_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 neighbouring_cicada_dumbs package is part of a series of npm packages that have been associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by creating and publishing numerous derivative packages with altered names and metadata. This behavior is primarily aimed at inflating developer reputation scores for token rewards, posing a significant risk to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in the neighbouring_cicada_dumbs package originates from its inclusion in a malicious campaign that utilizes autopublish scripts to modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The ramifications include pollution of the npm registry, potential security risks for users who unknowingly install these packages, and damage to the reputation of legitimate developers.

How To Fix

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

npm uninstall neighbouring_cicada_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 workaround, you can avoid using the neighbouring_cicada_dumbs package altogether. If it is a dependency of another package, consider removing that package or replacing it with a safer alternative. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which can alert you to open-source vulnerabilities in real-time.

Conclusion

The neighbouring_cicada_dumbs package poses a significant risk due to its malicious intent to manipulate the npm registry. It is crucial for developers to be vigilant about their dependencies and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive steps to remove affected packages and audit your project, you can safeguard your applications from potential threats.

See every vulnerability recorded for neighbouring_cicada_dumbs →

Share this vulnerability

FAQ

It is an npm package associated with a malicious campaign that manipulates the npm registry.

It can lead to the installation of malicious code, compromising the security and integrity of your project.

You should remove the package and monitor your project for any further vulnerabilities.

Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without needing to sign up.

How To Fix

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

npm uninstall neighbouring_cicada_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