Critical Malicious Code Vulnerability in clerk-js Package

clerk-js Updated 23 Jan 2026

Summary

21/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-410: Malicious code in clerk-js (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The clerk-js package is a JavaScript library used in web applications for managing user authentication and authorization. It provides features such as user sign-up, login, and session management, making it a popular choice among developers. However, recent findings have revealed that this package contains malicious code, posing significant security risks to any application utilizing it.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the clerk-js package. This code can compromise any computer that has the package installed, allowing unauthorized access to sensitive data such as secrets and keys. The ramifications of this vulnerability are severe, as it can lead to complete control of the affected system by an external entity. Users are advised to treat any system running this package as fully compromised.

How To Fix

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

npm uninstall clerk-js

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, consider isolating the affected application from sensitive data and networks until the package can be removed and the system secured. Additionally, rotate all secrets and keys stored on the compromised system from a different, secure machine.

Conclusion

The discovery of malicious code within the clerk-js package presents a critical security threat to applications using it. Immediate action is required to remove the package and secure any compromised systems. Users should remain vigilant and utilize tools like Vulert to monitor for vulnerabilities in their software.

See every vulnerability recorded for clerk-js →

Share this vulnerability

FAQ

Clerk-js is a JavaScript library used for user authentication and authorization in web applications.

The malicious code can compromise your system, allowing unauthorized access to sensitive data and potentially giving control to external entities.

Immediately remove the clerk-js package from your application and rotate any sensitive keys or secrets stored on the affected system.

Yes, you can use Vulert to monitor and alert for open-source vulnerabilities. You can check if your application is affected by visiting the Vulert playground at Vulert Scanner.

Not necessarily. While removing the package is essential, there is no guarantee that all malicious software will be removed. It is advisable to assess the system for further compromises.

How To Fix

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

npm uninstall clerk-js

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