Malicious Code Injection in sensitive_cod_dumbs Package

sensitive_cod_dumbs Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-108541: Malicious code in sensitive_cod_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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The sensitive_cod_dumbs package is part of a broader campaign that exploits the npm ecosystem, primarily targeting developers involved in token reward systems. This package is designed to automate the generation and publication of derivative packages, which can mislead developers and inflate reputation scores. Its functionality revolves around creating random package names and modifying existing package metadata, making it a significant threat to the integrity of the npm registry.

Vulnerability Detail

The vulnerability in the sensitive_cod_dumbs package originates from its malicious intent to manipulate the npm registry. It includes scripts that automatically publish variants of the package with altered metadata, such as removing private flags and changing version numbers. This behavior not only pollutes the npm registry but also poses risks to developers who may unknowingly use these compromised packages, potentially leading to security breaches in their applications.

How To Fix

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

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

Currently, there are no specific workarounds to mitigate the effects of this vulnerability other than removing the package entirely from your project.

Conclusion

The sensitive_cod_dumbs package poses a significant threat due to its malicious behavior of manipulating npm registry data. It is crucial for developers to be vigilant and remove any instances of this package from their projects. Regular monitoring and updating of dependencies can help mitigate such risks in the future.

See every vulnerability recorded for sensitive_cod_dumbs →

Share this vulnerability

FAQ

The sensitive_cod_dumbs package is a malicious npm package that automates the creation and publication of derivative packages to inflate developer reputation scores.

Using the sensitive_cod_dumbs package can lead to the inclusion of malicious code in your project, potentially compromising its security and integrity.

If you have installed the sensitive_cod_dumbs package, you should uninstall it immediately using the command npm uninstall sensitive_cod_dumbs.

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 also check your application against known vulnerabilities using the Vulert playground.

To prevent vulnerabilities, always use trusted packages, regularly update your dependencies, and consider using automated tools to monitor your projects for security issues.

How To Fix

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

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