Malicious Code Detected in splide Package - MAL-2025-6313

splide Updated 02 Oct 2025

Summary

23/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6313: Malicious code in splide (npm). Affects splide versions >= 2.4.21. 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 splide package is a lightweight, flexible slider and carousel library for web applications, enabling developers to create responsive and customizable sliders with ease. It is widely used in various web projects for its simplicity and versatility. However, a recent vulnerability has been identified that allows the package to communicate with a domain associated with malicious activities, posing a significant risk to users and their applications.

Vulnerability Detail

The vulnerability identified in the splide package (MAL-2025-6313) originates from version 2.4.21 and later. It allows the package to establish communication with a domain linked to malicious activities, which could lead to data breaches, unauthorized access, or other security threats. This vulnerability highlights the importance of scrutinizing third-party packages for potential risks, as they can introduce unforeseen security issues into otherwise secure applications.

How To Fix

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

npm uninstall splide

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, you can remove the splide package from your project if it is not essential. Alternatively, consider using a different slider library that does not have known vulnerabilities.

Conclusion

The splide package has a critical vulnerability that allows it to communicate with a malicious domain, posing risks to applications that utilize it. Users are urged to update to the latest version or consider alternative solutions to mitigate potential threats. Regular monitoring of dependencies using tools like Vulert can help maintain application security.

See every vulnerability recorded for splide →

Share this vulnerability

FAQ

The splide package is a JavaScript library used for creating responsive sliders and carousels in web applications.

The vulnerability allows the splide package to communicate with a malicious domain, potentially compromising user data and application security.

You can use Vulert, which monitors open-source vulnerabilities in your software. By analyzing your package-lock.json file, it provides real-time alerts for vulnerabilities. Visit Vulert Scanner to check your application without any signup.

Yes, updating the splide package to the latest version will address the vulnerability. Use the command npm update splide to apply the patch.

If an immediate update is not possible, consider removing the splide package or using an alternative library until a fix can be applied.

How To Fix

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

npm uninstall splide

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