Malicious Code Detected in dctk Package - Security Alert

dctk Updated 02 Oct 2025

Summary

24/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6280: Malicious code in dctk (npm). Affects dctk versions >= 99.99.1. 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 dctk package is an npm library designed for data communication and transformation tasks. It is widely used in various applications for its efficient handling of data. However, recent findings have revealed that this package communicates with a domain associated with malicious activities, posing a significant security risk to applications that utilize it.

Vulnerability Detail

The vulnerability in the dctk package arises from its communication with a domain linked to malicious activities. This could lead to unauthorized data access, data breaches, or the execution of harmful code within applications that depend on this package. The issue was introduced in version 99.99.1, and it is critical for developers to be aware of the potential ramifications of using this compromised package.

How To Fix

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

npm uninstall dctk

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 remove the dctk package from your project until a secure version is available. This can be done using the command: npm uninstall dctk. Alternatively, consider using an alternative package that provides similar functionality without the security risks.

Conclusion

The dctk package has been identified as having a serious vulnerability due to its communication with a malicious domain. Developers are urged to take immediate action by updating or removing the package to safeguard their applications. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for dctk →

Share this vulnerability

FAQ

The dctk package is used for data communication and transformation tasks in various applications.

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.

If an immediate update is not possible, consider uninstalling the package or using an alternative until a secure version is released.

Currently, there is no specific patch version mentioned, but it is advisable to check the official repository for updates.

Using the compromised dctk package can lead to unauthorized data access, data breaches, and the execution of harmful code in your application.

How To Fix

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

npm uninstall dctk

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