Critical Malicious Code Vulnerability in dise-pkt Package

dise-pkt Updated 02 Feb 2026

Summary

02/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-644: Malicious code in dise-pkt (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 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 dise-pkt package is a Node.js library available through npm, designed for specific data packet manipulation tasks. It is utilized in various applications for its functionality in handling network data. However, this package has been compromised, leading to significant security concerns for any system utilizing it.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the dise-pkt package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The origin of this issue is linked to a malicious actor who has inserted harmful code into the package, making it a severe threat to users and their systems.

How To Fix

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

npm uninstall dise-pkt

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

There are no effective workarounds for this vulnerability other than removing the dise-pkt package entirely. Users should ensure that their systems are secure and monitor for any unusual activity following the removal.

Conclusion

The dise-pkt package has been identified as containing malicious code, posing a serious threat to any system that has it installed. Immediate action is required to remove the package and secure sensitive information. Users are encouraged to utilize tools like Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for dise-pkt →

Share this vulnerability

FAQ

You should immediately uninstall the dise-pkt package and rotate any sensitive information stored on the affected system.

You can use Vulert's playground at Vulert Scanner to check if your application is affected without any signup.

No, there is currently no patched version available for the dise-pkt package. The only solution is to remove it.

Failing to remove the dise-pkt package can lead to unauthorized access to your system, compromising sensitive data and potentially allowing further malicious activities.

While many npm packages are safe, it is essential to monitor and verify the integrity of packages you use. Tools like Vulert can help you stay informed about vulnerabilities.

How To Fix

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

npm uninstall dise-pkt

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