Malicious Code Vulnerability in dstny Package

dstny Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1719: Malicious code in dstny (npm). Affects dstny versions 999.0.0. 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 dstny package is a JavaScript library available through npm, designed to facilitate various functionalities in web applications. It is widely used for its ease of integration and robust features. However, recent findings have revealed that this package is susceptible to a malicious code vulnerability, which poses significant risks to applications utilizing it.

Vulnerability Detail

The vulnerability identified in the dstny package involves the introduction of malicious code that can compromise the integrity of applications relying on this library. This issue originated from a specific version (999.0.0) that was flagged by security researchers. The ramifications of this vulnerability include potential unauthorized access to sensitive data, execution of arbitrary code, and disruption of application functionality. It is crucial for developers to be aware of this risk and take appropriate measures to safeguard their applications.

How To Fix

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

npm uninstall dstny

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, consider removing the dstny package from your project until a secure version is released. You can do this by running the command: npm uninstall dstny. This will help mitigate the risk of exposure to the malicious code until a fix is implemented.

Conclusion

The dstny package has been found to contain a malicious code vulnerability that poses significant risks to applications using it. Developers are urged to update the package to a secure version or remove it until a fix is available. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for dstny →

Share this vulnerability

FAQ

The malicious code can potentially allow unauthorized access to sensitive data and execute harmful operations within the application.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without requiring any signup.

If immediate updates are not feasible, consider removing the package temporarily to avoid exposure to the vulnerability.

It is essential to check the package repository for the latest stable version that addresses the vulnerability. Avoid using version 999.0.0.

The vulnerability was identified by ReversingLabs, a security research organization that specializes in analyzing software for potential threats.

How To Fix

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

npm uninstall dstny

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