Malicious Code Detected in casper-runner: A Critical Security Alert

casper-runner Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16627: Malicious code in casper-runner (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The casper-runner package is a tool used in web automation and testing, allowing developers to run scripts that interact with web pages. It is widely utilized in the JavaScript ecosystem for its ability to facilitate automated testing of web applications. However, recent findings have revealed that this package contains malicious code, posing significant risks to users and their applications.

Vulnerability Detail

The vulnerability in the casper-runner package stems from the inclusion of malicious code that can compromise the security of applications utilizing this package. This code can potentially lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The malicious code was introduced in all versions starting from 0, making it imperative for users to take immediate action to mitigate risks.

How To Fix

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

npm uninstall casper-runner

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, users can avoid using the casper-runner package until a secure version is released. Alternatively, consider using other testing frameworks that do not have known vulnerabilities.

Conclusion

The discovery of malicious code in the casper-runner package highlights the importance of maintaining vigilance regarding open-source dependencies. Users are urged to update their packages promptly and consider alternative solutions until the issue is resolved.

See every vulnerability recorded for casper-runner →

Share this vulnerability

FAQ

casper-runner is a JavaScript package used for web automation and testing, allowing developers to run scripts that interact with web pages.

The malicious code can compromise the security of applications, potentially leading to unauthorized access or data breaches.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner without any signup.

Immediately update the package to the latest version or consider using alternative testing frameworks until a secure version is released.

Utilize tools like Vulert to monitor your package-lock.json file for real-time alerts on open-source vulnerabilities.

How To Fix

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

npm uninstall casper-runner

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