Malicious Code Detected in @client-web-next/api-metrics Package

@client-web-next/api-metrics Updated 24 Sep 2026

Summary

22/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-16497: Malicious code in @client-web-next/api-metrics (npm). Affects @client-web-next/api-metrics 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/api-metrics package is a Node.js library used for tracking and reporting API metrics in web applications. It is designed to help developers monitor performance and usage statistics effectively. However, this package has been identified as containing malicious code, which poses a significant risk to applications that rely on it.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code in version 0.0.1 of the @client-web-next/api-metrics package. This code can potentially compromise the security of applications using this package, leading to unauthorized access, data breaches, or other malicious activities. The origin of this vulnerability is linked to the package being flagged by security researchers at ReversingLabs, highlighting the importance of scrutinizing third-party dependencies.

How To Fix

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

npm uninstall @client-web-next/api-metrics

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 using alternative packages that provide similar functionality without the associated risks. Additionally, you can implement security measures such as code reviews and dependency scanning to mitigate potential threats.

Conclusion

The @client-web-next/api-metrics package has been identified as containing malicious code, posing significant risks to applications that utilize it. It is crucial for developers to remove the affected version and monitor for any updates or patches. Utilizing tools like Vulert can help in identifying vulnerabilities in real-time.

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

Share this vulnerability

FAQ

The malicious code can lead to unauthorized access to sensitive data, potential data breaches, and other security vulnerabilities in applications using the affected package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By analyzing your package-lock.json file, Vulert can provide real-time alerts. You can also check your application using the Vulert playground at Vulert Scanner without any signup.

Currently, there is no patched version available for the @client-web-next/api-metrics package. It is advisable to monitor the package repository for any updates.

If no alternative package is available, consider implementing additional security measures such as thorough code reviews and dependency audits to minimize risks.

The vulnerability was discovered by security researchers at ReversingLabs, who flagged the package for containing malicious code.

How To Fix

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

npm uninstall @client-web-next/api-metrics

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