Critical Malicious Code Vulnerability in transform-remove-debugger Package

transform-remove-debugger Updated 18 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1509: Malicious code in transform-remove-debugger (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 transform-remove-debugger package is an npm utility designed to remove debugger statements from JavaScript code. It is commonly used in production environments to clean up code before deployment. However, this package has been compromised, embedding malicious code that poses significant security risks to any system using it.

Vulnerability Detail

The vulnerability originates from a malicious code injection within the transform-remove-debugger package. Any system with this package installed is considered fully compromised, potentially allowing unauthorized access to sensitive data, including secrets and keys. The malicious code can persist even after the package is removed, making it crucial for users to take immediate action to secure their systems.

How To Fix

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

npm uninstall transform-remove-debugger

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 are no effective workarounds for this vulnerability. The only safe course of action is to uninstall the compromised package and secure your system.

Conclusion

The transform-remove-debugger package has been compromised, embedding malicious code that can severely impact system security. Immediate uninstallation and key rotation are critical to mitigate risks. Regular monitoring of dependencies is essential to prevent future vulnerabilities.

See every vulnerability recorded for transform-remove-debugger →

Share this vulnerability

FAQ

Immediately uninstall the package using 'npm uninstall transform-remove-debugger' and rotate any sensitive keys or secrets.

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

Keeping this package installed can lead to unauthorized access to your system, data breaches, and potential control by malicious actors.

No, there is no patched version available. The recommended action is to uninstall the package entirely.

You can use tools like Vulert, which monitors and alerts you in real-time for open-source vulnerabilities using just your package-lock.json file.

How To Fix

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

npm uninstall transform-remove-debugger

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