Malicious Code Detected in public-site-cms-ui Package - Critical Vulnerability

public-site-cms-ui Updated 23 Jan 2026

Summary

23/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-483: Malicious code in public-site-cms-ui (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The public-site-cms-ui package is a component of the npm ecosystem, commonly used for building user interfaces in content management systems. It provides essential functionalities for developers to create and manage public-facing websites. However, this package has been identified to contain malicious code, posing significant security risks to applications that depend on it.

Vulnerability Detail

The vulnerability originates from the discovery of malicious code within the public-site-cms-ui package, as reported by Amazon Inspector. This malicious code can lead to unauthorized access, data breaches, or other harmful actions within affected applications. The vulnerability affects all versions of the package starting from its introduction, making it imperative for users to take immediate action.

How To Fix

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

npm uninstall public-site-cms-ui

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 measure, you can remove the public-site-cms-ui package from your project until a secure version is released. Use the following command to uninstall the package: npm uninstall public-site-cms-ui.

Conclusion

The public-site-cms-ui package has been identified to contain malicious code, posing serious security risks. Users are urged to update or uninstall the package to mitigate potential threats. Continuous monitoring and prompt action are essential to maintain application security.

See every vulnerability recorded for public-site-cms-ui →

Share this vulnerability

FAQ

The malicious code can perform unauthorized actions within applications, potentially leading to data breaches or other security incidents.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

Currently, there is no specific patched version mentioned. It is advisable to monitor the package repository for updates.

As a workaround, consider uninstalling the public-site-cms-ui package until a secure version is available.

The vulnerability was reported by Amazon Inspector, a security assessment service.

How To Fix

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

npm uninstall public-site-cms-ui

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