Malicious Code Vulnerability in dgl-cu117 Package - Executable Decryption Risk

dgl-cu117 Updated 15 Mar 2026

Summary

15/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1432: Malicious code in dgl-cu117 (PyPI). Affects dgl-cu117 versions 14.6.0 – 16.0.0. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The dgl-cu117 package is a library available on PyPI, primarily used for deep learning graph neural networks. It provides functionalities that facilitate the development and training of graph-based models. However, this package has been compromised, leading to serious security concerns due to the presence of malicious code that executes upon import.

Vulnerability Detail

The vulnerability originates from a malicious campaign identified as 2026-03-ariadne-federation. During the import process, the dgl-cu117 package decrypts and executes a hidden malicious executable, which is encoded and obfuscated within a JSON resource file. This poses significant risks, including potential data theft and unauthorized access to system resources. The malicious executable is designed to operate stealthily, making detection challenging for users.

How To Fix

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

pip uninstall dgl-cu117

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, avoid using the dgl-cu117 package until a secure version is confirmed. If you must use it, consider isolating it in a controlled environment to minimize potential damage.

Conclusion

The dgl-cu117 package has been identified as a vector for malicious code execution, posing serious security risks to users. It is essential to take immediate action by updating the package and employing monitoring tools like Vulert to safeguard against potential threats.

See every vulnerability recorded for dgl-cu117 →

Share this vulnerability

FAQ

The vulnerability involves the execution of a malicious executable that is decrypted during the import of the package.

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.

Immediately uninstall the package and update to a secure version using 'pip uninstall dgl-cu117' followed by 'pip install --upgrade dgl-cu117'.

Yes, the malicious code can lead to data theft, unauthorized access, and potential system compromise.

Signs may include unusual system behavior, unexpected network activity, or unauthorized access attempts. Regular monitoring is advised.

How To Fix

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

pip uninstall dgl-cu117

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