Malicious Code Vulnerability in @client-web-next/adaptive Package

@client-web-next/adaptive Updated 24 Sep 2026

Summary

22/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-16495: Malicious code in @client-web-next/adaptive (npm). Affects @client-web-next/adaptive 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 Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The @client-web-next/adaptive package is a component of the npm ecosystem, designed to facilitate adaptive web client functionalities. It is utilized in various web applications to enhance user experience through dynamic content adjustments. However, this package has been identified as containing malicious code, posing significant security risks to applications that depend on it.

Vulnerability Detail

The vulnerability originates from a malicious code injection within version 0.0.1 of the @client-web-next/adaptive package. This code can potentially lead to unauthorized access, data breaches, or exploitation of the application, compromising user data and application integrity. The malicious nature of this code makes it imperative for users to take immediate action to secure their applications.

How To Fix

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

npm uninstall @client-web-next/adaptive

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 workaround, consider removing the @client-web-next/adaptive package from your project until a secure version is released. You can do this by executing the following command: npm uninstall @client-web-next/adaptive.

Conclusion

The discovery of malicious code in the @client-web-next/adaptive package highlights the importance of maintaining vigilance in open-source software management. Users are urged to take immediate action by updating or removing the affected package to safeguard their applications.

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

Share this vulnerability

FAQ

The malicious code can lead to unauthorized access and data breaches, putting user information and application security at risk.

You can use Vulert's playground at Vulert Scanner to check if your application is affected without needing to sign up.

Currently, there is no patched version available. Users should keep an eye on the package repository for future updates.

If immediate removal is not possible, ensure that your application has additional security measures in place to mitigate risks until the package can be updated or removed.

The vulnerability was identified by ReversingLabs, a security research organization.

How To Fix

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

npm uninstall @client-web-next/adaptive

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