Malicious Code Vulnerability in cms_comp_popup Package

cms_comp_popup Updated 23 Dec 2025

Summary

23/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192726: Malicious code in cms_comp_popup (npm). Affects cms_comp_popup versions 999.0.0. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The cms_comp_popup package is a JavaScript library available through npm, designed to facilitate the creation and management of pop-up components in web applications. It is widely used due to its ease of integration and customizable features. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the cms_comp_popup package, specifically in version 999.0.0. This code can potentially compromise the security of applications by executing unauthorized actions, leading to data breaches or system manipulation. The malicious nature of the code was identified by ReversingLabs, indicating a serious threat to users who have integrated this package into their projects.

How To Fix

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

npm uninstall cms_comp_popup

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, users are advised to avoid using the cms_comp_popup package until a secure version is released. Consider implementing alternative libraries for pop-up management that are known to be secure and actively maintained.

Conclusion

The cms_comp_popup package has been identified as containing malicious code, posing a significant security risk to applications that utilize it. Users are advised to remove the package and seek alternatives to ensure their applications remain secure. Regular monitoring for vulnerabilities using tools like Vulert can help maintain application integrity.

See every vulnerability recorded for cms_comp_popup →

Share this vulnerability

FAQ

cms_comp_popup is a JavaScript library used for creating pop-up components in web applications.

The vulnerability involves malicious code embedded in the cms_comp_popup package, which can compromise application security.

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

Currently, there is no patched version of the cms_comp_popup package available.

It is recommended to uninstall the cms_comp_popup package and consider using a secure alternative until a fix is provided.

How To Fix

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

npm uninstall cms_comp_popup

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