Malicious Code Detected in player-button Package - Critical Vulnerability Alert

player-button Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1818: Malicious code in player-button (npm). Affects player-button 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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The player-button package is an npm library designed to provide customizable button components for media players. It is widely used in web applications to enhance user interaction with audio and video content. However, recent findings have revealed that this package has been compromised, introducing malicious code that could jeopardize the security of applications relying on it.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the player-button package, specifically in version 100.0.0. This code can potentially allow attackers to execute unauthorized actions, compromise user data, or gain control over the affected systems. The malicious nature of this code poses significant risks to any application utilizing this package, making it imperative for developers to address this issue promptly.

How To Fix

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

npm uninstall player-button

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 remove the player-button package from your project until a secure version is released. Use the following command to uninstall it: 'npm uninstall player-button'. Consider using alternative libraries that provide similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the player-button package highlights the importance of maintaining vigilance in open-source software. Developers should take immediate action to update or remove the affected package to safeguard their applications. Utilizing tools like Vulert can aid in monitoring vulnerabilities effectively.

See every vulnerability recorded for player-button →

Share this vulnerability

FAQ

The player-button package is an npm library that provides customizable button components for media players, enhancing user interaction with audio and video content.

The malicious code found in the player-button package can execute unauthorized actions, potentially compromising user data and system security.

You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in real-time. By simply uploading your package-lock.json file, you can check if your application is affected by this vulnerability.

Yes, you can temporarily uninstall the player-button package and consider using alternative libraries until a secure version is released.

Detailed information about this vulnerability can be found on the official GitHub repository and the Open Source Vulnerability database.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall player-button

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