Malicious Code Detected in kalitest11 Package - Critical Security Risk

kalitest11 Updated 02 Oct 2025

Summary

24/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6290: Malicious code in kalitest11 (npm). Affects kalitest11 versions >= 9.1.1. 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 kalitest11 package is an npm library that is used for various functionalities in JavaScript applications. However, it has been identified as containing malicious code that communicates with a domain associated with harmful activities. This vulnerability poses a significant risk to any system utilizing this package, potentially compromising sensitive data and system integrity.

Vulnerability Detail

The vulnerability in the kalitest11 package stems from its embedded malicious code, which was introduced in version 9.1.1. This code can lead to unauthorized access and control over the affected systems. The malicious nature of the code means that any computer running this package should be considered fully compromised, with all secrets and keys stored on that computer needing immediate rotation. The package's association with a malicious domain further exacerbates the risk, as it may facilitate data exfiltration or other harmful activities.

How To Fix

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

npm uninstall kalitest11

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, you can prevent the execution of the kalitest11 package by removing it from your dependencies and ensuring that your application does not call any functions from this package. However, this does not guarantee that all malicious effects are mitigated, so complete removal is recommended.

Conclusion

The kalitest11 package presents a significant security risk due to its embedded malicious code. Immediate action is required to remove the package and secure any compromised systems. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for kalitest11 →

Share this vulnerability

FAQ

kalitest11 is an npm package used in JavaScript applications, but it has been identified as containing malicious code.

You can use Vulert, which monitors vulnerabilities in open-source packages. Check your application against the vulnerability using the Vulert playground at Vulert Scanner.

Immediately uninstall the kalitest11 package and rotate any sensitive information stored on the affected system.

Currently, there is no patched version available. The best course of action is to remove the package entirely.

Failing to address this vulnerability can lead to unauthorized access, data breaches, and potential control over your system by malicious actors.

How To Fix

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

npm uninstall kalitest11

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