Malicious Code Detected in @client-web-next/analytics Package - Critical Vulnerability Alert

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

Summary

22/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-16496: Malicious code in @client-web-next/analytics (npm). Affects @client-web-next/analytics 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/analytics package is a JavaScript library used in web applications for analytics tracking and data collection. It is designed to help developers integrate analytics features seamlessly into their applications. 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 in version 0.0.1 of the @client-web-next/analytics package. This code can potentially compromise the security of applications by allowing unauthorized access, data exfiltration, or other malicious activities. The origin of this vulnerability has been traced back to a malicious actor who injected harmful code into the package, making it imperative for users to take immediate action to mitigate risks.

How To Fix

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

npm uninstall @client-web-next/analytics

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, developers can avoid using the @client-web-next/analytics package until a secure version is released. Additionally, consider using alternative analytics libraries that are known to be secure and widely used in the community.

Conclusion

The @client-web-next/analytics package has been identified as containing malicious code, posing significant risks to applications that utilize it. Immediate action is required to uninstall the affected version and seek alternatives. Utilizing tools like Vulert can help in monitoring and preventing future vulnerabilities.

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

Share this vulnerability

FAQ

The malicious code can lead to unauthorized access and data breaches, potentially compromising user data and application integrity.

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

Currently, there is no patched version available for the compromised version 0.0.1. Users should uninstall it and look for alternative packages.

Immediately uninstall the package and assess your application for any potential security breaches. Consider using alternative analytics solutions.

Regularly monitor your dependencies using tools like Vulert, and keep your packages updated to the latest secure versions.

How To Fix

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

npm uninstall @client-web-next/analytics

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