Critical Malicious Code Vulnerability in oneapi-gdb-debug Package

oneapi-gdb-debug Updated 02 Oct 2025

Summary

09/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-5714: Malicious code in oneapi-gdb-debug (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 oneapi-gdb-debug package is a Node.js library designed for debugging applications built with Intel's oneAPI toolkit. It provides developers with tools to analyze and troubleshoot their code effectively. However, this package has been identified as containing malicious code, posing significant security risks to any system where it is installed.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the oneapi-gdb-debug package. This code can compromise the security of any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of this code means that even after removal of the package, there is no guarantee that all traces of the malware will be eliminated, potentially leaving systems vulnerable to further attacks.

How To Fix

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

npm uninstall oneapi-gdb-debug

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

Currently, there are no effective workarounds to mitigate the risks posed by this vulnerability other than removing the package entirely. Ensure that all secrets and keys stored on the affected computer are rotated from a different, secure machine.

Conclusion

The oneapi-gdb-debug package has been identified as containing malicious code that poses significant security risks. Immediate removal of the package is necessary to protect your system. Regular monitoring and auditing of your software dependencies are crucial to maintaining security.

See every vulnerability recorded for oneapi-gdb-debug →

Share this vulnerability

FAQ

You should remove the oneapi-gdb-debug package immediately and rotate any sensitive information stored on the affected machine.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

While removing the package is essential, there is no guarantee that all malicious software will be removed. It is advisable to perform a thorough security audit of your system.

Currently, there is no patched version available for the oneapi-gdb-debug package, so updating will not resolve the issue.

Leaving the oneapi-gdb-debug package installed can lead to unauthorized access to sensitive data and further compromise your system's security.

How To Fix

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

npm uninstall oneapi-gdb-debug

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