Malicious Code Detected in libdebugrouter.so - npm Package Vulnerability

libdebugrouter.so Updated 01 Dec 2025

Summary

01/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191499: Malicious code in libdebugrouter.so (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

libdebugrouter.so is a package available in the npm ecosystem, primarily used for debugging purposes in various applications. It is designed to facilitate the routing of debug information, making it easier for developers to troubleshoot issues in their code. However, this package has been found to contain malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability originates from the discovery of malicious code embedded within the libdebugrouter.so package. This malicious code can potentially compromise the integrity of applications that depend on this package, leading to unauthorized access, data breaches, or other harmful actions. The specific technical details of the malicious code have not been disclosed, but its presence indicates a severe threat to application security.

How To Fix

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

npm uninstall libdebugrouter.so

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 libdebugrouter.so package from your project until a secure version is released. You can do this by executing the following command: npm uninstall libdebugrouter.so. This will help mitigate the risk associated with the malicious code until a fix is available.

Conclusion

The discovery of malicious code in the libdebugrouter.so npm package highlights the importance of regularly monitoring and updating open-source dependencies. Developers should take immediate action to mitigate risks by removing the package or updating it as soon as a secure version is available.

See every vulnerability recorded for libdebugrouter.so →

Share this vulnerability

FAQ

libdebugrouter.so is an npm package used for routing debug information in applications, aiding developers in troubleshooting.

The malicious code was identified by Amazon Inspector, which conducts security assessments on open-source packages.

Using this package can lead to unauthorized access, data breaches, and other security vulnerabilities in your application.

Currently, there is no specific patch version mentioned. It is advisable to monitor the npm repository for updates.

You can use Vulert, which monitors open-source vulnerabilities in your software using just package-lock.json. Visit Vulert Scanner to check your application without any signup.

How To Fix

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

npm uninstall libdebugrouter.so

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