Critical Malicious Code Vulnerability in dsidospsodlks Package

dsidospsodlks Updated 19 Nov 2025

Summary

17/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-190505: Malicious code in dsidospsodlks (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 dsidospsodlks package is an npm library that is used for various functionalities in JavaScript applications. However, it has been identified to contain malicious code that poses significant security risks to systems utilizing this package. The presence of such code can lead to unauthorized access and control over affected systems.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the dsidospsodlks package. This code can compromise any computer that has the package installed, allowing attackers to gain full control over the system. The ramifications include potential data breaches, loss of sensitive information, and the ability for attackers to execute arbitrary commands. It is crucial to recognize that simply removing the package may not eliminate all traces of the malicious software, as the attackers may have already established a foothold in the system.

How To Fix

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

npm uninstall dsidospsodlks

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 workaround, if immediate removal of the package is not feasible, consider isolating the affected application from sensitive data and networks until the package can be safely removed. However, this is not a permanent solution and should only be a temporary measure.

Conclusion

The dsidospsodlks package poses a serious security threat due to the presence of malicious code. Immediate action is required to remove the package and secure any compromised systems. Regular monitoring and vulnerability management practices, such as those offered by Vulert, can help prevent similar issues in the future.

See every vulnerability recorded for dsidospsodlks →

Share this vulnerability

FAQ

dsidospsodlks is an npm package used in JavaScript applications, but it has been found to contain malicious code.

If you have the dsidospsodlks package installed, your system is likely compromised. It is recommended to remove the package immediately.

You should rotate all secrets and keys stored on the affected system from a different, secure computer.

While removing the package is necessary, it may not eliminate all malicious software. Full system checks and potential reinstallation may be required.

Vulert monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file, providing real-time insights without requiring code access.

How To Fix

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

npm uninstall dsidospsodlks

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