Malicious code in cannotdelete (npm)

cannotdelete Updated 02 Oct 2025

Summary

01/12/2023
CRITICAL
No i
Critical
Not published

MAL-2023-8652: Malicious code in cannotdelete (npm). Affects cannotdelete versions 1.1.0. 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 package 'cannotdelete' is an npm package that is used for a specific functionality. It has been identified as containing malicious code by the OpenSSF Package Analysis project. The package version 1.1.0 is considered malicious because it communicates with a domain associated with malicious activity.

Vulnerability Detail

The vulnerability in 'cannotdelete' package lies in the fact that it contains code that communicates with a domain associated with malicious activity. This can have serious ramifications as it can potentially compromise the security and integrity of the system where the package is used. The malicious code can perform unauthorized actions, steal sensitive information, or introduce other malicious activities into the system.

How To Fix

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

npm uninstall cannotdelete

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

There is no specific workaround mentioned for this vulnerability. The best course of action is to remove the package and ensure the system is secure.

Conclusion

The 'cannotdelete' package version 1.1.0 has been identified as containing malicious code. It is crucial to remove this package from the system and take necessary steps to ensure the security and integrity of the system. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for cannotdelete →

Share this vulnerability

FAQ

The impact of this vulnerability can be severe as it can compromise the security and integrity of the system. It can lead to unauthorized actions, data theft, and other malicious activities.

You can use tools like Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities in software.

Yes, the fix for this vulnerability is to remove the 'cannotdelete' package from the system and ensure the system is secure.

Yes, this vulnerability can be exploited remotely if the system has the 'cannotdelete' package installed and the malicious code is triggered.

There may be instances of this vulnerability being exploited, as the package has been identified as containing malicious code. It is important to take immediate action to remove the package and secure the system.

How To Fix

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

npm uninstall cannotdelete

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

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.