Malicious Code Detected in customer-account-ui-extensions Package

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17839: Malicious code in customer-account-ui-extensions (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 customer-account-ui-extensions package is an npm library designed to enhance customer account functionalities in web applications. It provides various extensions that allow developers to customize user experiences. 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 customer-account-ui-extensions package. This code can potentially compromise the security of applications, leading to unauthorized access, data breaches, or other malicious activities. The issue affects all versions of the package starting from its introduction, making it critical for users to address this vulnerability promptly.

How To Fix

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

npm uninstall customer-account-ui-extensions

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, consider using alternative packages that provide similar functionalities without the associated risks. Always ensure to review the security of any third-party libraries before integrating them into your application.

Conclusion

The customer-account-ui-extensions package has been identified to contain malicious code, posing a serious threat to applications that utilize it. It is crucial for developers to uninstall the package and monitor for updates or alternatives to ensure the security of their applications.

See every vulnerability recorded for customer-account-ui-extensions →

Share this vulnerability

FAQ

It is an npm library that enhances customer account functionalities in web applications.

The specific nature of the malicious code has not been disclosed, but it poses significant security risks.

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 patched version available, and it is recommended to uninstall the package until a secure version is released.

Consider using alternative packages that offer similar functionalities and ensure to review their security before integration.

How To Fix

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

npm uninstall customer-account-ui-extensions

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