Malicious code in ux-website (npm)

ux-website Updated 02 Oct 2025

Summary

21/10/2023
CRITICAL
No i
Critical
Not published

MAL-2023-8392: Malicious code in ux-website (npm). Affects ux-website versions 1.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 'ux-website' package is an npm package that provides functionality for building user experience websites. It is commonly used in web development projects to create interactive and visually appealing user interfaces. The package is vulnerable to a malicious code injection attack, which can lead to unauthorized access, data breaches, and other security risks.

Vulnerability Detail

The 'ux-website' package has been identified as malicious due to its communication with a domain associated with malicious activity. This indicates that the package may contain code that performs unauthorized actions or collects sensitive information from users. The presence of this malicious code poses a significant risk to the security and integrity of any application that includes the 'ux-website' package.

How To Fix

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

npm uninstall ux-website

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, you can manually inspect the code of the 'ux-website' package to identify and remove any malicious code. However, this approach is time-consuming and may not guarantee complete removal of all malicious components. Therefore, it is highly recommended to follow the fix mentioned above and replace the package with a trusted alternative.

Conclusion

The 'ux-website' package has been identified as malicious due to its communication with a domain associated with malicious activity. This vulnerability poses a significant risk to the security and integrity of any application that includes the package. To mitigate this risk, it is recommended to remove the package from your project and replace it with a trusted alternative. Regularly updating packages and conducting security audits are also essential practices to ensure the overall security of your application.

See every vulnerability recorded for ux-website →

Share this vulnerability

FAQ

This vulnerability can lead to unauthorized access, data breaches, and other security risks. Attackers may exploit the malicious code in the 'ux-website' package to perform actions such as stealing sensitive information, injecting additional malicious code, or compromising the overall security of the application.

You can use the Vulert Playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Simply provide the package-lock.json file of your application, and Vulert will analyze it in real-time to identify any open-source vulnerabilities, including this one.

The most effective mitigation for this vulnerability is to remove the 'ux-website' package from your project and replace it with a trusted alternative. Regularly updating all packages in your project and conducting security audits can also help identify and address any other potential vulnerabilities.

While it is technically possible to use the 'ux-website' package if you take precautions such as manually inspecting the code and implementing additional security measures, it is highly recommended to replace the package with a trusted alternative. The presence of malicious code in the package poses a significant risk, and it is difficult to guarantee complete security even with precautions.

For further support on vulnerability remediation and securing your application, you can contact info@devnack.com. They can provide guidance, resources, and assistance in addressing the vulnerability and ensuring the overall security of your application.

How To Fix

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

npm uninstall ux-website

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