Malicious Code Vulnerability in discovery-player Package

discovery-player Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18495: Malicious code in discovery-player (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 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 discovery-player package is an npm library designed for building interactive media experiences. It allows developers to create engaging applications that utilize various media formats. However, this package has been identified to contain malicious code, posing a significant risk to applications that rely on it.

Vulnerability Detail

The vulnerability in the discovery-player package stems from the inclusion of malicious code that can compromise the security of applications using this library. This code can potentially lead to unauthorized access, data breaches, or other malicious activities. The issue was introduced in version 0 and affects all subsequent versions.

How To Fix

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

npm uninstall discovery-player

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 avoid using the discovery-player package and seek alternative libraries that provide similar functionality without the associated risks. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which analyzes your package-lock.json file for real-time alerts on open-source vulnerabilities.

Conclusion

The discovery-player package has been identified to contain malicious code, posing a serious risk to applications that utilize it. It is crucial to remove this package and seek alternatives to ensure the security of your application. Utilizing tools like Vulert can help keep your project safe from vulnerabilities.

See every vulnerability recorded for discovery-player →

Share this vulnerability

FAQ

The discovery-player package is an npm library used for creating interactive media applications.

The malicious code can lead to unauthorized access and potential data breaches in applications that utilize the package.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

Currently, there is no patched version available. It is recommended to remove the package and look for alternatives.

Vulert uses your package-lock.json file to monitor and alert you in real-time for open-source vulnerabilities in your software.

How To Fix

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

npm uninstall discovery-player

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