Critical Malicious Code Vulnerability in devstart-cli Package

devstart-cli Updated 24 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-190768: Malicious code in devstart-cli (npm). Affects devstart-cli versions 1.0.6. 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 devstart-cli package is a command-line interface tool designed for developers to streamline their project setup and management processes. It is part of the npm ecosystem, which is widely used for JavaScript package management. However, this package has been identified to contain malicious code that compromises the security of any system it is installed on, making it a significant threat to users and their data.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the devstart-cli package, specifically version 1.0.6. This code can grant unauthorized access to the user's system, potentially leading to data theft, loss of sensitive information, and full system compromise. Users are advised to treat any system running this package as fully compromised, as the malicious code may persist even after the package is removed.

How To Fix

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

npm uninstall devstart-cli

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 effective workarounds to mitigate the risks posed by this vulnerability other than removing the package and securing the system. Users should also monitor their systems for any unusual activity following the removal.

Conclusion

The devstart-cli package has been identified as containing malicious code that poses a serious security threat. Users must take immediate action to remove the package and secure their systems. Regular monitoring for vulnerabilities is essential to maintain the security of your applications.

See every vulnerability recorded for devstart-cli →

Share this vulnerability

FAQ

You should uninstall the devstart-cli package immediately and rotate any sensitive information stored on your system.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

Keeping devstart-cli installed poses significant risks, including unauthorized access to your system, data theft, and potential loss of sensitive information.

No, there is currently no patched version available for the devstart-cli package. It is recommended to uninstall it immediately.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.

How To Fix

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

npm uninstall devstart-cli

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

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.