Malicious Code Detected in cljsrt Package - Security Alert

cljsrt Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17144: Malicious code in cljsrt (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 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 cljsrt package is a JavaScript library commonly used in web development for various functionalities. It is designed to enhance the performance and capabilities of applications built with the ClojureScript language. However, recent findings have revealed that this package contains malicious code, posing a significant security risk to users and their applications.

Vulnerability Detail

The vulnerability in the cljsrt package stems from the inclusion of malicious code that can compromise the security of applications utilizing this library. This code may allow unauthorized access to sensitive data, facilitate data breaches, or enable other malicious activities. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to address this vulnerability promptly.

How To Fix

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

npm uninstall cljsrt

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 can remove the cljsrt package from their project until a secure version is released. This can be done by executing the command: npm uninstall cljsrt. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the cljsrt package poses a serious threat to users and their applications. It is imperative to take immediate action by updating or removing the package to mitigate potential risks. Utilizing tools like Vulert can help monitor and alert for vulnerabilities in real-time, ensuring the security of your software.

See every vulnerability recorded for cljsrt →

Share this vulnerability

FAQ

The malicious code can potentially allow unauthorized access to sensitive data and may lead to data breaches or other harmful activities.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without needing to sign up.

If an immediate update is not possible, consider uninstalling the package and using alternative libraries until a secure version is available.

While specific exploits have not been detailed, the presence of malicious code indicates a high risk of exploitation, making it crucial to address the vulnerability as soon as possible.

Detailed information about the vulnerability can be found in the official GitHub repository for the malicious packages at https://github.com/ossf/malicious-packages.

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 cljsrt

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