Malicious Code Vulnerability in underlying_constrictor_dumbs Package

underlying_constrictor_dumbs Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-110063: Malicious code in underlying_constrictor_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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The underlying_constrictor_dumbs package is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names, aiming to inflate developer reputation scores for token rewards. This behavior poses a significant risk to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in the underlying_constrictor_dumbs package originates from its malicious design, which includes autopublish scripts that modify the package.json file. These modifications remove private flags, alter version numbers, and create random package names, leading to the continuous republishing of variants. This not only pollutes the npm registry but also compromises the security of applications relying on this package, potentially allowing for further exploitation.

How To Fix

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

npm uninstall underlying_constrictor_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 temporarily avoid using the underlying_constrictor_dumbs package by removing it from your dependencies. You can do this by executing the following command in your project directory: npm uninstall underlying_constrictor_dumbs.

Conclusion

The underlying_constrictor_dumbs package contains a significant vulnerability that can compromise the security of applications relying on it. Immediate action is required to remove the package and monitor for updates. Utilizing tools like Vulert can help in identifying and managing such vulnerabilities effectively.

See every vulnerability recorded for underlying_constrictor_dumbs →

Share this vulnerability

FAQ

It is an npm package involved in a malicious campaign that generates and publishes numerous derivative packages to inflate developer reputation scores.

The vulnerability can lead to the pollution of the npm registry and may compromise the security of applications that depend on the affected package.

You should uninstall the underlying_constrictor_dumbs package immediately and monitor for any updates or patches that may be released.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can check your application for vulnerabilities using the Vulert playground without any signup.

Detailed information can be found in the vulnerability report and by monitoring updates from the npm registry and security advisories.

How To Fix

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

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