Malicious Code Detected in easyply Package - MAL-2025-19095

easyply Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19095: Malicious code in easyply (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The easyply package is an npm library designed to facilitate easy playback of audio and video files in web applications. It offers features such as seamless integration with various media formats and user-friendly controls. However, it has been identified to contain malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the easyply package originates from the inclusion of malicious code that can compromise the security of applications using this library. This malicious code can lead to unauthorized access, data breaches, or exploitation of user systems. It is crucial for developers to understand that any version of easyply starting from 0 is affected, and immediate action is required to mitigate potential risks.

How To Fix

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

npm uninstall easyply

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, consider removing the easyply package from your project until a secure version is released. You can do this by executing the command: npm uninstall easyply. This will prevent any potential exploitation while you await a fix.

Conclusion

The easyply package has been identified to contain malicious code, posing significant risks to applications that utilize it. Immediate action is required to update or remove the package to ensure the security of your application. Stay vigilant and use tools like Vulert to monitor for vulnerabilities.

See every vulnerability recorded for easyply →

Share this vulnerability

FAQ

easyply is an npm package used for easy playback of audio and video files in web applications.

The malicious code can lead to unauthorized access and potential exploitation of user systems.

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.

As a workaround, consider uninstalling the easyply package to prevent any potential exploitation until a secure version is available.

Utilizing tools like Vulert can help you monitor your dependencies for vulnerabilities in real-time.

How To Fix

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

npm uninstall easyply

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