Critical Malicious Code Vulnerability in cms_comp_static Package

cms_comp_static Updated 12 Dec 2025

Summary

12/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192556: Malicious code in cms_comp_static (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 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_static package is an npm library designed for managing static content in content management systems. It provides functionalities that allow developers to easily integrate and serve static files. However, this package has been identified as containing malicious code, which poses significant security risks to any system utilizing it.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the cms_comp_static package. This code can compromise any computer that has the package installed, allowing unauthorized access to sensitive information, including secrets and keys. The malicious nature of this code means that simply removing the package may not eliminate all traces of the compromise, as full control of the affected system may have been granted to an external entity.

How To Fix

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

npm uninstall cms_comp_static

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, the only effective workaround is to uninstall the cms_comp_static package. You can do this by running the following command in your terminal: npm uninstall cms_comp_static. After uninstallation, verify that no malicious remnants remain on your system.

Conclusion

The cms_comp_static package has been identified as containing malicious code that poses a serious security risk. Immediate action is required to remove the package and secure any sensitive information. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for cms_comp_static →

Share this vulnerability

FAQ

cms_comp_static is an npm package used for managing static content in content management systems.

The malicious code can compromise your system, allowing unauthorized access to sensitive information and potentially granting full control to an external entity.

You should immediately uninstall the cms_comp_static package and rotate any secrets or keys stored on the affected system.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.

Not necessarily. While removing the package is essential, there may still be remnants of the malicious code on your system. It's crucial to assess and secure your system thoroughly.

How To Fix

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

npm uninstall cms_comp_static

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