Malicious Code Detected in chakalaka Package - Security Alert

chakalaka Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16764: Malicious code in chakalaka (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 chakalaka package is an npm library designed for various functionalities in JavaScript applications. It is widely used for its ease of integration and versatility. However, recent findings have revealed that this package contains malicious code, posing a significant security risk to applications that rely on it.

Vulnerability Detail

The vulnerability in the chakalaka package originates from the inclusion of malicious code that can compromise the security of applications utilizing this package. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The issue is particularly concerning as it affects all versions of the package starting from its introduction, making it imperative for users to take immediate action.

How To Fix

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

npm uninstall chakalaka

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 removing the chakalaka package from your project until a secure version is released. You can do this by running: npm uninstall chakalaka. This will help mitigate the risk of exposure to the malicious code.

Conclusion

The discovery of malicious code in the chakalaka package poses a serious threat to applications that utilize it. Users are urged to take immediate action by updating or removing the package to safeguard their systems. Continuous monitoring and vigilance are essential to mitigate potential risks.

See every vulnerability recorded for chakalaka →

Share this vulnerability

FAQ

The chakalaka package is an npm library used in JavaScript applications for various functionalities.

The malicious code can lead to unauthorized access and potential data breaches in applications using the package.

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.

As of now, a patched version is not available. Users should monitor the package repository for updates.

If immediate removal is not possible, ensure to implement strict security measures and monitor your application closely for any suspicious activity.

How To Fix

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

npm uninstall chakalaka

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