Malicious Code Detected in chakl Package - Security Alert

chakl Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16766: Malicious code in chakl (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The chakl package is an npm library designed for developers to streamline certain functionalities in their applications. It is widely used for its ease of integration and robust features. However, recent findings have revealed that this package contains malicious code, posing significant security risks to users and their applications.

Vulnerability Detail

The vulnerability in the chakl package stems from the inclusion of malicious code that can compromise the security of applications utilizing this library. This code may allow unauthorized access, data breaches, or other harmful actions that can affect both developers and end-users. The issue was identified in all versions starting from 0, indicating that any application using this package is potentially at risk.

How To Fix

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

npm uninstall chakl

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, consider removing the chakl package from your project until a secure version is released. You can do this by running the command: 'npm uninstall chakl'. This will help mitigate any immediate risks associated with the malicious code.

Conclusion

The discovery of malicious code in the chakl package highlights the importance of regularly monitoring and updating open-source libraries. Users of this package should take immediate action to mitigate risks by updating or removing the package. Utilizing tools like Vulert can further enhance security by providing real-time alerts for vulnerabilities.

See every vulnerability recorded for chakl →

Share this vulnerability

FAQ

The chakl package is an npm library that provides various functionalities to developers, enhancing their application development process.

You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities. By analyzing your package-lock.json file, Vulert can inform you if your application is at risk.

If an immediate update is not possible, consider removing the package from your project as a temporary workaround to prevent potential security issues.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

Using the compromised chakl package may lead to unauthorized access to sensitive data, data breaches, and other security incidents that could harm both developers and users.

How To Fix

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

npm uninstall chakl

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