Malicious Code Vulnerability in player-common-composites Package

player-common-composites Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1819: Malicious code in player-common-composites (npm). Affects player-common-composites 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 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 player-common-composites package is a component used in npm for building composite player applications. It provides essential functionalities for managing and rendering multimedia content. However, this package has been identified to contain malicious code, posing significant risks to applications that depend on it.

Vulnerability Detail

The vulnerability in the player-common-composites package stems from the inclusion of malicious code that can compromise the security of applications using this package. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The malicious nature of this code was identified through a detailed analysis by security researchers, highlighting the importance of scrutinizing third-party packages before integration.

How To Fix

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

npm uninstall player-common-composites

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-composites package from your project until a secure version is available. You can do this by executing: npm uninstall player-common-composites. Additionally, review your application for any dependencies that may also rely on this package.

Conclusion

The player-common-composites package has been identified to contain malicious code, posing a significant security risk. It is essential to update to a patched version or remove the package until a secure version is available. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for player-common-composites →

Share this vulnerability

FAQ

The player-common-composites package is an npm library used for building multimedia applications, providing functionalities for managing and rendering content.

You can use Vulert, a tool that monitors open-source vulnerabilities in your software. By analyzing your package-lock.json file, Vulert can alert you in real-time about vulnerabilities, including this one.

The malicious code can lead to unauthorized access, data breaches, and potentially allow attackers to execute harmful actions within your application.

Yes, it is recommended to check for a patched version of the player-common-composites package and update to that version as soon as possible.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

npm uninstall player-common-composites

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