Malicious Code Detected in Clashbot Package - Security Alert

clashbot Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17092: Malicious code in clashbot (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

Clashbot is an npm package designed for various functionalities, including automation and bot creation. It is widely used in the JavaScript ecosystem for its ease of use and integration capabilities. However, recent findings have revealed that this package contains malicious code, posing significant security risks to users and their applications.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the clashbot package. This code can potentially compromise user data, lead to unauthorized access, and disrupt application functionality. The malicious nature of this code makes it imperative for users to take immediate action to safeguard their systems.

How To Fix

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

npm uninstall clashbot

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, users may consider removing the clashbot package from their projects until a secure version is confirmed. This can be done using the command: 'npm uninstall clashbot'.

Conclusion

The clashbot package has been identified to contain malicious code, necessitating immediate action from users to protect their applications. Updating to the latest version or uninstalling the package are critical steps to mitigate risks.

See every vulnerability recorded for clashbot →

Share this vulnerability

FAQ

Clashbot is an npm package used for automation and bot creation in JavaScript applications.

The malicious code can compromise user data and lead to unauthorized access, posing significant security risks.

You can use Vulert's playground at Vulert Scanner to check if your application is affected without any signup.

As a temporary measure, consider uninstalling the clashbot package until a secure version is available.

Vulert uses package-lock.json to monitor and alert in real-time for open-source vulnerabilities in your software, providing an easy way to stay informed.

How To Fix

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

npm uninstall clashbot

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