Malicious Code Detected in debug-common Package - Security Alert

debug-common Updated 01 Dec 2025

Summary

01/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191509: Malicious code in debug-common (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 debug-common package is a Node.js library commonly used for debugging purposes in JavaScript applications. It provides a simple way to log messages to the console, making it easier for developers to troubleshoot issues in their code. However, recent findings have revealed that this package has been compromised, containing malicious code that could potentially harm applications relying on it.

Vulnerability Detail

The vulnerability originates from a malicious code injection in the debug-common package, identified by the Amazon Inspector. This code can lead to unauthorized access, data breaches, or even complete system compromise. The malicious code was introduced in all versions starting from 0, making it critical for users of this package to take immediate action to safeguard their applications.

How To Fix

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

npm uninstall debug-common

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 workaround, consider removing the debug-common package from your project if it is not essential. Alternatively, you can replace it with a different debugging library that does not have known vulnerabilities.

Conclusion

The discovery of malicious code in the debug-common package poses a significant risk to applications that utilize it. Users are urged to take immediate action to update or replace the package to mitigate potential threats. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for debug-common →

Share this vulnerability

FAQ

debug-common is a Node.js library used for logging and debugging JavaScript applications.

The malicious code was identified by Amazon Inspector during a routine security assessment.

The risks include unauthorized access to sensitive data, potential data breaches, and system compromise.

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

If immediate updates are not possible, consider removing the package or using an alternative debugging library until a secure version is available.

How To Fix

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

npm uninstall debug-common

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