Critical Malicious Code Vulnerability in clip_settings Package

clip_settings Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17137: Malicious code in clip_settings (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 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 clip_settings package is an npm library designed for managing and configuring user settings in applications. It provides developers with a straightforward way to handle user preferences and application configurations. However, this package has been identified to contain malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the clip_settings package. This code can potentially compromise the integrity of applications using this package, leading to unauthorized access, data breaches, or other malicious activities. The issue is particularly concerning as it affects all versions starting from 0, making any application relying on this package vulnerable to exploitation.

How To Fix

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

npm uninstall clip_settings

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, you can avoid using the clip_settings package altogether and implement your own settings management solution or use a different, trusted package that offers similar functionality.

Conclusion

The clip_settings package has been identified as containing malicious code, posing a significant risk to applications that utilize it. It is crucial for developers to take immediate action by removing the package and considering alternatives to safeguard their applications.

See every vulnerability recorded for clip_settings →

Share this vulnerability

FAQ

The clip_settings package is an npm library used for managing user settings and configurations in applications.

The vulnerability involves malicious code embedded within the package, which can lead to security breaches.

You can use Vulert, which monitors open-source vulnerabilities in real-time. By analyzing your package-lock.json file, it can alert you to any vulnerabilities, including those in clip_settings.

You should remove the clip_settings package and consider using a secure alternative. If a patched version is released, update it immediately.

You can visit Vulert's playground at Vulert Scanner to check for vulnerabilities in your application without needing to sign up.

How To Fix

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

npm uninstall clip_settings

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