Malicious Code Vulnerability in @client-web-next/ui-business Package

@client-web-next/ui-business Updated 24 Sep 2026

Summary

22/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-16513: Malicious code in @client-web-next/ui-business (npm). Affects @client-web-next/ui-business versions 0.0.1. 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 @client-web-next/ui-business package is a component of the npm ecosystem, designed to provide UI business functionalities for web applications. It is utilized by developers to streamline the integration of user interface elements. However, this package has been identified with a serious vulnerability that allows for the execution of malicious code, potentially compromising applications that rely on it.

Vulnerability Detail

The vulnerability stems from malicious code embedded within version 0.0.1 of the @client-web-next/ui-business package. This code can lead to unauthorized access, data breaches, or other harmful actions within applications that utilize this package. The origin of this vulnerability is linked to the package's distribution through npm, where it was identified by security researchers from ReversingLabs.

How To Fix

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

npm uninstall @client-web-next/ui-business

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

If immediate updating is not feasible, consider removing the package from your project until a secure version is released. You can do this by executing: npm uninstall @client-web-next/ui-business. This will prevent any potential exploitation of the vulnerability in your application.

Conclusion

The @client-web-next/ui-business package has a serious vulnerability due to malicious code that can compromise applications. It is essential to update the package to a secure version or uninstall it until a fix is available. Utilizing tools like Vulert can help monitor and manage vulnerabilities effectively.

See every vulnerability recorded for @client-web-next/ui-business →

Share this vulnerability

FAQ

The vulnerability involves malicious code that can execute harmful actions within applications using the package.

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

As a temporary measure, you can uninstall the package to mitigate the risk until a secure version is available.

The vulnerability was identified by security researchers at ReversingLabs.

You should check the npm repository for any patched versions of the @client-web-next/ui-business package.

How To Fix

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

npm uninstall @client-web-next/ui-business

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