Malicious Code Detected in debu Package: Security Alert

debu Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18142: Malicious code in debu (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The debu package is a popular npm library used for debugging Node.js applications. It provides developers with a simple way to log debug messages to the console, helping to identify issues during development. However, recent findings have revealed that this package contains malicious code, posing a significant security risk to applications that rely on it.

Vulnerability Detail

The vulnerability in the debu package stems from the inclusion of malicious code, which can compromise the security of applications utilizing this library. This code can 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 address this vulnerability promptly.

How To Fix

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

npm uninstall debu

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 remove the debu package from your project if it is not essential. Use the following command to uninstall it: 'npm uninstall debu'. This will prevent any potential exploitation of the malicious code until a secure version is available.

Conclusion

The discovery of malicious code in the debu package poses a serious threat to applications using this library. It is crucial for developers to take immediate action by updating or removing the package to safeguard their applications. Utilizing tools like Vulert can help monitor for vulnerabilities effectively.

See every vulnerability recorded for debu →

Share this vulnerability

FAQ

The debu package is used for logging debug messages in Node.js applications, aiding developers in troubleshooting and debugging their code.

You can check if your application is affected by using Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to test your application without any signup.

Using the compromised debu package can lead to unauthorized access to your application, data breaches, and potential exploitation of your system by malicious actors.

Currently, there is no specific patched version available for the debu package. It is advisable to remove the package or monitor for updates from the maintainers.

If immediate removal is not possible, ensure that your application is secured through other means, such as implementing additional security measures and monitoring for unusual activity.

How To Fix

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

npm uninstall debu

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