Malicious Code Detected in dk2o Package - Security Alert

dk2o Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18518: Malicious code in dk2o (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 dk2o package is an npm library designed for specific functionalities within JavaScript applications. It is utilized by developers for various tasks, but its recent identification as containing malicious code poses a significant risk. The package's attributes include ease of integration and a lightweight footprint, making it appealing for developers. However, the presence of malicious code undermines its reliability and security.

Vulnerability Detail

The dk2o package has been found to contain malicious code that could compromise the security of applications utilizing it. This vulnerability originated from the package's codebase, which was intentionally altered to include harmful scripts. The ramifications of this vulnerability include unauthorized access to sensitive data, potential data breaches, and exploitation of the affected systems. Developers using this package are at risk of having their applications hijacked or manipulated.

How To Fix

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

npm uninstall dk2o

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, you can prevent the use of the dk2o package by removing it from your dependencies. You can do this by executing the following command in your terminal: npm uninstall dk2o. Additionally, consider using alternative packages that provide similar functionalities without the security risks.

Conclusion

The discovery of malicious code within the dk2o package highlights the importance of vigilance in managing software dependencies. Developers are urged to take immediate action to remove the affected package and explore secure alternatives. Utilizing tools like Vulert can aid in monitoring for vulnerabilities in real-time.

See every vulnerability recorded for dk2o →

Share this vulnerability

FAQ

The dk2o package is an npm library used in JavaScript applications for various functionalities.

The malicious code found in dk2o could lead to unauthorized access and exploitation of applications using 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.

You should uninstall the dk2o package immediately and consider using a secure alternative.

Regularly monitor your dependencies using tools like Vulert and keep your packages updated to mitigate potential vulnerabilities.

How To Fix

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

npm uninstall dk2o

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