Critical Malicious Code Vulnerability in debug-logger-utils Package

debug-logger-utils Updated 05 Feb 2026

Summary

05/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-768: Malicious code in debug-logger-utils (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-logger-utils package is an npm utility designed to facilitate logging and debugging in JavaScript applications. It provides developers with tools to manage log outputs effectively, enhancing the debugging process. However, this package has been identified to contain malicious code, posing significant security risks to any system utilizing it.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the debug-logger-utils package. This code can compromise any computer that has the package installed, potentially allowing unauthorized access to sensitive information such as secrets and keys. The origin of this vulnerability is linked to a malicious actor who has injected harmful code into the package, making it imperative 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 debug-logger-utils

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, ensure that any sensitive information stored on the affected system is rotated immediately. This includes changing passwords and API keys that may have been compromised. Additionally, consider using alternative logging packages that do not have known vulnerabilities.

Conclusion

The debug-logger-utils package has been compromised with malicious code, posing a serious threat to any systems using it. Immediate action is required to remove the package and secure sensitive information. Users are encouraged to monitor their applications for vulnerabilities using tools like Vulert.

See every vulnerability recorded for debug-logger-utils →

Share this vulnerability

FAQ

debug-logger-utils is an npm package used for logging and debugging in JavaScript applications.

The malicious code can compromise your system, allowing unauthorized access to sensitive information stored on it.

You should immediately uninstall the package and rotate any sensitive information stored on your system.

Currently, there is no patched version available. The best course of action is to remove the package entirely.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can check if your application is affected by this vulnerability using the Vulert playground without any signup.

How To Fix

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

npm uninstall debug-logger-utils

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