Critical Malicious Code Vulnerability in docksy Package

docksy Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18570: Malicious code in docksy (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The docksy package is an npm module designed for managing and deploying Docker containers efficiently. It provides developers with tools to streamline their container workflows, enhancing productivity and deployment speed. However, recent findings have revealed that docksy contains malicious code, posing significant risks to users and their applications.

Vulnerability Detail

The docksy package has been identified to contain malicious code that can compromise the security of applications utilizing it. This vulnerability originated from the introduction of harmful scripts within the package, which could lead to unauthorized access, data breaches, or system manipulation. Users of docksy are at risk of having their environments exploited, making it crucial to address this issue promptly.

How To Fix

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

npm uninstall docksy

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, users are advised to remove the docksy package from their projects until a secure version is confirmed. This can be done using the command: 'npm uninstall docksy'. Consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the docksy package highlights the importance of maintaining secure dependencies in software development. Users are urged to update or remove the affected package to safeguard their applications from potential threats.

See every vulnerability recorded for docksy →

Share this vulnerability

FAQ

docksy is an npm package used for managing Docker containers, providing tools to enhance deployment and workflow efficiency.

The malicious code found in docksy can lead to unauthorized access and potential data breaches within applications that utilize the package.

You can use Vulert, a tool that monitors open-source vulnerabilities in your software. By simply analyzing your package-lock.json file, Vulert can alert you to any vulnerabilities, including those in docksy.

Yes, Vulert offers real-time monitoring for open-source vulnerabilities without requiring code access or installation. You can check your application using the Vulert playground.

If you cannot update docksy right away, it is recommended to uninstall the package and look for alternative solutions until a secure version is available.

How To Fix

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

npm uninstall docksy

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