Malicious Code Detected in chakert Package - Security Alert

chakert Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16765: Malicious code in chakert (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 chakert package is an npm library designed for various functionalities within JavaScript applications. It is utilized by developers for its ease of integration and utility features. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that depend on it.

Vulnerability Detail

The vulnerability in the chakert package stems from the inclusion of malicious code that can compromise the security of applications using it. This code can lead to unauthorized access, data breaches, and potential exploitation of the affected systems. The malicious nature of this vulnerability was identified in version 0 and has been documented by security researchers.

How To Fix

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

npm uninstall chakert

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 replacing the chakert package with an alternative library that offers similar functionalities without the associated risks. Ensure to review the security posture of any new package before integration.

Conclusion

The discovery of malicious code in the chakert package highlights the importance of regularly auditing dependencies in software projects. Developers should take immediate action to remove the affected package and consider alternatives to ensure the security of their applications.

See every vulnerability recorded for chakert →

Share this vulnerability

FAQ

The chakert package is an npm library used in JavaScript applications for various functionalities, but it has been found to contain malicious code.

The malicious code was identified by security researchers and reported through the Open Source Vulnerability database.

Using the chakert package can lead to unauthorized access, data breaches, and exploitation of your application.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without any signup.

You should uninstall the chakert package immediately and consider using an alternative library that does not pose security risks.

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 chakert

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