Malicious Code Detected in dslash-parser: A Critical Security Concern

dslash-parser Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18940: Malicious code in dslash-parser (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 dslash-parser package is an npm library designed for parsing and manipulating mathematical expressions. It is widely used in applications that require complex calculations and data processing. However, the package has been found to contain malicious code, posing significant security risks to users and their applications.

Vulnerability Detail

The vulnerability in the dslash-parser package originates from the inclusion of malicious code that can compromise the security of applications utilizing this library. This code may lead to unauthorized access, data breaches, or other harmful actions, potentially affecting the integrity and confidentiality of user data. The malicious nature of the code makes it imperative for developers to address this issue promptly to safeguard their applications.

How To Fix

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

npm uninstall dslash-parser

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 dslash-parser package from your project until a secure version is confirmed. You can do this by executing the command: npm uninstall dslash-parser.

Conclusion

The discovery of malicious code in the dslash-parser package highlights the importance of maintaining secure dependencies in software development. Developers must act swiftly to update or remove affected packages to protect their applications and user data.

See every vulnerability recorded for dslash-parser →

Share this vulnerability

FAQ

The malicious code can compromise application security, potentially leading to unauthorized access and data breaches.

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.

Yes, users are advised to update to the latest version of dslash-parser to mitigate the risk associated with the malicious code.

As a temporary measure, consider uninstalling the dslash-parser package until a secure version is available.

Vulert uses just package-lock.json to monitor and alert for open-source vulnerabilities without requiring access to the code or installation.

How To Fix

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

npm uninstall dslash-parser

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