Critical Malicious Code Vulnerability in daytonjs Package

daytonjs Updated 02 Mar 2026

Summary

02/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1105: Malicious code in daytonjs (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

daytonjs is a JavaScript library available through npm that is designed for various web development tasks. It is utilized by developers to streamline their coding processes and enhance functionality in web applications. However, this package has been identified as containing malicious code, posing significant security risks to any system where it is installed.

Vulnerability Detail

The vulnerability in the daytonjs package stems from the presence of embedded malicious code, which can compromise the security of any computer running this package. This malicious code can lead to unauthorized access, data breaches, and the potential for further exploitation of the system. The vulnerability is classified under CWE-506, indicating that the product contains code that appears to be malicious in nature. Users are advised to treat any system with this package installed as fully compromised.

How To Fix

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

npm uninstall daytonjs

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

Currently, there are no workarounds available that can mitigate the risks associated with the daytonjs package. The best course of action is to uninstall the package and secure your system.

Conclusion

The daytonjs package has been identified as containing malicious code that poses serious security risks. Users are strongly advised to uninstall the package immediately and take necessary precautions to secure their systems. Utilizing tools like Vulert can help in monitoring and managing open-source vulnerabilities effectively.

See every vulnerability recorded for daytonjs →

Share this vulnerability

FAQ

You should immediately uninstall the daytonjs package and rotate any secrets or keys stored on the affected machine.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.

No, there is currently no patched version available for the daytonjs package. The only solution is to uninstall it.

Leaving daytonjs installed can lead to unauthorized access to your system, data breaches, and further exploitation by malicious actors.

Regularly monitor your dependencies using tools like Vulert, and ensure that you keep your packages updated to the latest secure versions.

How To Fix

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

npm uninstall daytonjs

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