Critical Malicious Code Vulnerability in internal-plugin-telemetry-backend Package

Summary

22/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6166: Malicious code in internal-plugin-telemetry-backend (npm). Affected versions are not published. 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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The internal-plugin-telemetry-backend package is an npm library designed for telemetry data collection and processing. It is utilized in various applications to gather performance metrics and user interactions. However, this package has been identified to contain embedded malicious code, posing significant security risks to any system utilizing it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code embedded within the internal-plugin-telemetry-backend package. This code can compromise the entire system where the package is installed, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of this code is classified under CWE-506, indicating that it appears to be intentionally harmful. The ramifications of this vulnerability are severe, as it can lead to complete system compromise and data breaches.

How To Fix

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

npm uninstall internal-plugin-telemetry-backend

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 measure, you can isolate the affected application from the network to prevent unauthorized access while you work on removing the package. Additionally, consider rotating all secrets and keys stored on the compromised system immediately.

Conclusion

The internal-plugin-telemetry-backend package contains a critical vulnerability due to embedded malicious code. Immediate action is required to remove the package and secure any compromised systems. Regular monitoring and updates are essential to maintain application security.

See every vulnerability recorded for internal-plugin-telemetry-backend →

Share this vulnerability

FAQ

It is an npm package used for collecting and processing telemetry data in applications.

The vulnerability involves embedded malicious code that can compromise the entire system where the package is installed.

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

You should remove the internal-plugin-telemetry-backend package immediately and rotate any sensitive information stored on the affected system.

Currently, there is no specific patch mentioned, but it is advisable to keep an eye on the package repository for any updates.

How To Fix

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

npm uninstall internal-plugin-telemetry-backend

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