Malicious Code Detected in diablokit Package - Security Alert

diablokit Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18428: Malicious code in diablokit (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 diablokit package is an npm library designed for specific functionalities within JavaScript applications. It is utilized by developers for various tasks, including data manipulation and API interactions. However, the package has been identified to contain malicious code, posing a significant security risk to applications that incorporate it.

Vulnerability Detail

The vulnerability in the diablokit package originates from the inclusion of malicious code that can compromise the security of applications using this package. This malicious code can lead to unauthorized access, data breaches, and potential exploitation of the affected systems. The issue is present from version 0 and affects all subsequent versions, making it critical for users to take immediate action.

How To Fix

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

npm uninstall diablokit

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, consider removing the diablokit package from your project until a secure version is released. You can do this by executing the following command: npm uninstall diablokit.

Conclusion

The discovery of malicious code in the diablokit package poses a serious threat to applications utilizing it. Users must take immediate action to mitigate risks by updating or removing the package. Continuous monitoring and vigilance are essential until a secure version is released.

See every vulnerability recorded for diablokit →

Share this vulnerability

FAQ

diablokit is an npm package used in JavaScript applications for various functionalities, but it has been found to contain malicious code.

The malicious code can lead to unauthorized access and data breaches, compromising the security of your application.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.

Currently, there is no patched version available. Users are advised to uninstall the package until a secure version is released.

If immediate removal is not possible, ensure to monitor your application closely for any suspicious activity and prepare to update as soon as a patch is available.

How To Fix

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

npm uninstall diablokit

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