Malicious Code Detected in debuggers Package - MAL-2025-18146

debuggers Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18146: Malicious code in debuggers (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 'debuggers' package is an npm library designed to facilitate debugging in JavaScript applications. It provides developers with tools to inspect and troubleshoot their code effectively. However, this package has been identified to contain malicious code, posing a significant risk to users who integrate it into their projects.

Vulnerability Detail

The vulnerability in the 'debuggers' package stems from the inclusion of malicious code that can compromise the security of applications utilizing this library. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to take immediate action.

How To Fix

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

npm uninstall debuggers

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 measure, you can avoid using the 'debuggers' package in your application until a secure alternative is identified. Consider using other debugging libraries that are well-maintained and have a good security track record.

Conclusion

The 'debuggers' package has been identified as containing malicious code, which poses a serious risk to applications that utilize it. Users are urged to remove the package and explore secure alternatives to safeguard their projects. Regular monitoring for vulnerabilities using tools like Vulert is advisable to maintain application security.

See every vulnerability recorded for debuggers →

Share this vulnerability

FAQ

The 'debuggers' package is an npm library used for debugging JavaScript applications, providing tools for inspecting and troubleshooting code.

The malicious code found in the 'debuggers' package can lead to unauthorized access and potential data breaches in applications using this library.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.

If you have used the 'debuggers' package, it is crucial to remove it from your project immediately and replace it with a secure alternative.

Currently, there is no patched version available for the 'debuggers' package. It is recommended to remove the package and look for alternatives.

How To Fix

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

npm uninstall debuggers

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