Malicious Code Injection in cold_pigeon_dumbs Package - npm Vulnerability

cold_pigeon_dumbs Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-100652: Malicious code in cold_pigeon_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 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 cold_pigeon_dumbs package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate automatic publishing of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that alters package metadata and floods the npm registry with variants.

Vulnerability Detail

The vulnerability in the cold_pigeon_dumbs package stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of these variants, polluting the npm registry and potentially compromising the integrity of other packages. The origin of this issue is linked to the tea.xyz token reward campaign, which employs autopublish scripts to automate the creation of these malicious packages.

How To Fix

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

npm uninstall cold_pigeon_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 this package by using npm's package-lock.json to monitor dependencies. Ensure that your project does not include cold_pigeon_dumbs by regularly auditing your dependencies with 'npm audit'.

Conclusion

The cold_pigeon_dumbs package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial to remove this package from your projects and monitor your dependencies to maintain the integrity of your applications.

See every vulnerability recorded for cold_pigeon_dumbs →

Share this vulnerability

FAQ

cold_pigeon_dumbs is an npm package that is part of a token reward campaign and is known for containing malicious code that modifies package metadata.

The malicious code can alter your package.json file, remove private flags, and flood the npm registry with variants, potentially compromising your project's integrity.

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

If you have installed cold_pigeon_dumbs, you should uninstall it immediately using 'npm uninstall cold_pigeon_dumbs' and audit your dependencies.

Currently, there is no patched version of cold_pigeon_dumbs available. The best course of action is to remove the package from your project.

How To Fix

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

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