Critical Malicious Code Vulnerability in modify-setting Package

modify-setting Updated 24 Feb 2026

Summary

24/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1010: Malicious code in modify-setting (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 modify-setting package is an npm module designed to facilitate the modification of configuration settings in various applications. It is commonly used in JavaScript projects to streamline the process of updating application settings dynamically. However, this package has been identified as containing malicious code, which poses a significant security risk to any system that has it installed.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the modify-setting package, identified by the alias GHSA-p88w-8j5m-hjw2. This code can compromise the entire system, allowing unauthorized access to sensitive information such as secrets and keys. The presence of this malicious code means that any computer running this package should be considered fully compromised, and immediate action is required to mitigate potential damage.

How To Fix

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

npm uninstall modify-setting

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 the modify-setting package. The best course of action is to remove the package entirely and rotate any secrets or keys that may have been compromised.

Conclusion

The modify-setting package has been identified as containing malicious code that poses a severe security risk. Immediate removal of the package and rotation of any compromised secrets is essential. Users are encouraged to utilize tools like Vulert for ongoing monitoring of their applications to prevent future vulnerabilities.

See every vulnerability recorded for modify-setting →

Share this vulnerability

FAQ

You should immediately remove the modify-setting package from your system and rotate any sensitive information that may have been compromised.

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.

Failure to address this vulnerability can lead to unauthorized access to sensitive data, complete system compromise, and potential data breaches.

While removing the package is crucial, there is no guarantee that all malicious software will be eliminated. It is advisable to perform a thorough security audit and consider restoring from a clean backup.

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay informed about known vulnerabilities in the packages you use.

How To Fix

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

npm uninstall modify-setting

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