Malicious Code Vulnerability in @client-web-next/ab-tests Package

@client-web-next/ab-tests Updated 24 Sep 2026

Summary

22/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-16494: Malicious code in @client-web-next/ab-tests (npm). Affects @client-web-next/ab-tests 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/ab-tests package is an npm library designed for A/B testing in web applications. It allows developers to implement experiments to optimize user experience and engagement. However, this package has been identified as containing malicious code, which poses significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the @client-web-next/ab-tests package, specifically in version 0.0.1. This code can potentially compromise the integrity of applications that depend on this package, leading to unauthorized access, data breaches, or other malicious activities. The issue was reported by ReversingLabs and is cataloged under the ID MAL-2026-16494.

How To Fix

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

npm uninstall @client-web-next/ab-tests

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, you can remove the @client-web-next/ab-tests package from your project until a secure version is released. Use the following command to uninstall it: npm uninstall @client-web-next/ab-tests.

Conclusion

The @client-web-next/ab-tests package has been identified as containing malicious code, posing a significant risk to applications that utilize it. It is crucial to update or remove the package to protect your application from potential threats. Utilize tools like Vulert for ongoing monitoring of vulnerabilities in your dependencies.

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

Share this vulnerability

FAQ

The malicious code can compromise application security, leading to unauthorized access or data breaches.

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

If an immediate update is not possible, consider removing the package as a temporary measure to mitigate risks.

The vulnerability was reported by ReversingLabs, a cybersecurity firm specializing in threat detection.

Yes, Vulert can monitor and alert you in real-time for open-source vulnerabilities in your software using just the package-lock.json file.

How To Fix

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

npm uninstall @client-web-next/ab-tests

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