Malicious Code Injection in @user-services/web-components: Telemetry Probe Vulnerability

Summary

22/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-16379: Malicious code in @user-services/web-components (npm). Affects @user-services/web-components versions 9.9.10. 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 @user-services/web-components package is an npm library designed for web component development within user services. It provides reusable components that can be integrated into various applications. However, version 9.9.10 of this package has been found to contain malicious code that compromises user data security.

Vulnerability Detail

The vulnerability originates from a hidden telemetry probe embedded in the @user-services/web-components package. This probe activates during the npm install lifecycle and on every require() of the module. It collects sensitive information such as the username, hostname, and current working directory, which it sends to an attacker-controlled server. The malicious code is obfuscated to evade detection by static analysis tools, making it particularly dangerous as it can exfiltrate user identity data without consent.

How To Fix

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

npm uninstall @user-services/web-components

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 @user-services/web-components package from your project until a patched version is available. Use the following command to uninstall the package: npm uninstall @user-services/web-components.

Conclusion

The @user-services/web-components package version 9.9.10 contains a serious vulnerability due to embedded malicious code that exfiltrates user data. It is crucial to update to a patched version or remove the package to protect against potential data breaches.

See every vulnerability recorded for @user-services/web-components →

Share this vulnerability

FAQ

The malicious code is a telemetry probe that collects sensitive user information and sends it to an external server.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By analyzing your package-lock.json file, Vulert can help you identify if your application is affected.

If an immediate update is not possible, consider removing the package from your project as a temporary measure to mitigate risk.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without requiring any signup.

The consequences include unauthorized access to sensitive user information, which could lead to identity theft or other malicious activities.

How To Fix

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

npm uninstall @user-services/web-components

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