Malicious Code Detected in player-common-controls: A Critical npm Vulnerability

player-common-controls Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1820: Malicious code in player-common-controls (npm). Affects player-common-controls versions 100.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 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 player-common-controls package is a widely used npm library designed to provide common control functionalities for media players. It is utilized in various applications to streamline the development of media-related features. However, this package has been found to contain malicious code, posing significant security risks to applications that depend on it.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the player-common-controls package, specifically in version 100.0.0. This code can potentially compromise the integrity of applications using the package, leading to unauthorized access, data breaches, or other malicious activities. The origin of this vulnerability is linked to the package's distribution through npm, where it was identified by security researchers from ReversingLabs.

How To Fix

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

npm uninstall player-common-controls

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

If immediate updating is not feasible, consider removing the player-common-controls package from your project and replacing it with an alternative library that offers similar functionalities without the associated risks. Additionally, you can monitor your package dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time.

Conclusion

The discovery of malicious code in the player-common-controls npm package highlights the importance of regularly monitoring and updating dependencies in software projects. By following the recommended steps to fix the vulnerability and utilizing tools like Vulert for ongoing monitoring, developers can protect their applications from potential threats.

See every vulnerability recorded for player-common-controls →

Share this vulnerability

FAQ

player-common-controls is an npm library that provides common functionalities for media player controls, making it easier for developers to implement media features in their applications.

The malicious code found in the player-common-controls package can lead to unauthorized access and potential data breaches in applications that utilize it.

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

If you cannot update the package right away, consider removing it and using an alternative library. Additionally, monitor your dependencies for vulnerabilities using tools like Vulert.

The vulnerability was discovered by security researchers from ReversingLabs, who identified the malicious code in the player-common-controls package.

How To Fix

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

npm uninstall player-common-controls

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