Malicious Code Detected in @wptv/player Package - Security Risk Identified

@wptv/player Updated 02 Oct 2025

Summary

23/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6269: Malicious code in @wptv/player (npm). Affects @wptv/player versions >= 1.0.0. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The @wptv/player package is an npm library designed for media playback functionalities within web applications. It provides developers with tools to integrate video and audio playback seamlessly. However, this package has been identified to communicate with a domain associated with malicious activities, raising significant security concerns for users and developers relying on it.

Vulnerability Detail

The vulnerability in the @wptv/player package arises from its communication with a domain linked to malicious activities. This could potentially lead to data breaches, unauthorized access, or the execution of harmful scripts within applications that utilize this package. The issue was introduced in version 1.0.0 and poses a serious risk to any application that incorporates this library, as it may compromise user data and application integrity.

How To Fix

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

npm uninstall @wptv/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 workaround, consider removing the @wptv/player package from your project until a secure version is released. You can uninstall it using the following command: npm uninstall @wptv/player.

Conclusion

The @wptv/player package has been identified with a serious vulnerability that allows communication with a malicious domain. It is crucial for developers to take immediate action by updating or removing the package to protect their applications and users from potential threats.

See every vulnerability recorded for @wptv/player →

Share this vulnerability

FAQ

The vulnerability involves the package communicating with a domain associated with malicious activities, posing risks to application security.

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

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

Check the official npm repository for @wptv/player to see if a patched version has been released.

Failure to address this vulnerability may lead to data breaches, unauthorized access, and compromised application integrity.

How To Fix

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

npm uninstall @wptv/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